How can I edit commit messages in my wp-hosted plugin repo?
what’s the best way to go about editing commit messages? Don’t worry about it, don’t make such mistake in future “ask the administrator to create a pre-revprop-change hook”
what’s the best way to go about editing commit messages? Don’t worry about it, don’t make such mistake in future “ask the administrator to create a pre-revprop-change hook”
This will not be a problem. WordPress doesn’t provide plugins with an explicit update hook for this reason: If a plugin is manually updated then this upgrade hook won’t fire. The best way to manage database upgrades is to do it the same way as WordPress does it. Store an option containing your plugin’s database … Read more
Use this URL format for checkout (if using TortoiseSVN, just right click and do checkout from Explorer): http://plugins.svn.wordpress.org/your-plugin-name You will need to use your username/password for WordPress (the account used to publish the plugin) to do any commits. Command line instructions are available direct from WordPress here: https://wordpress.org/plugins/about/svn/
I found the answer myself. I wasn’t creating the patch correctly. You have to use the “Create patch…” option in TortoiseSVN on the root folder, not the patched file itself.
For the current version, make sure you include the Version attribute in your plugin header file. Like this: /* Plugin Name: WordPress.org Plugin Plugin URI: https://developer.wordpress.org/plugins/the-basics/ Description: Basic WordPress Plugin Header Comment Version: 2.3.0 Author: WordPress.org Author URI: https://developer.wordpress.org/ License: GPL2 License URI: https://www.gnu.org/licenses/gpl-2.0.html Text Domain: wporg Domain Path: /languages */ For more detail check … Read more
Needed to use svn delete command to delete files, and then commit the changes. Screenshot: https://prnt.sc/v0lzb2
A readme update may take a week or more. Sometimes it helps to update just the readme file again. The Last Updated field is … dead. One of my plugins still shows the date 2010-12-24, but I had three updates in the mean time, the last one a week ago. The whole system feels like … Read more
If you know Subversion basics and can work with it (and write at least some bash-code), it will be feasible task All plugins placed in common repo http://plugins.svn.wordpress.org, each plugin is subdir of the root plugins.svn.wordpress.org/PLUGINNAME, published versions (all, not only releases) stored as directories in tags: plugins.svn.wordpress.org/PLUGINNAME/tags/ In order to check new versions of … Read more
This is an instruction I wrote for myself: Increment version nummber in plugin php file. Increment the “Stable tag” in readme.txt file to to the same number. Copy over all files from local plugin folder to the the D:\My_SVN_Folder\Plugin_Name\trunk Right click trunk folder and select SVN Commit Enter “Version X.X.X” and Save files to /trunk … Read more
The command you need is patch which is not specific to SVN. It’s really easy to do. See this article: http://jungels.net/articles/diff-patch-ten-minutes.html