License Compatibility As a recent commenter pointed out on my site, it should be possible to distribute a plug-in that’s not GPL so long as you don’t distribute it with WordPress. However, the guys at WP.org have pointed out time and again that only GPL-compatible plug-ins must be compatible with version 2 of the GPL. … Read more
Do you want to display the plugins and themes for sale or download or just have them accessible to download for updates?
If your plugin is already in the repository, you don’t need to submit the form to ADD a new plugin, you only need to update the trunk folder to make your update via svn. Sure WordPress will send you an email to tell you that the name is already use by another plugin and ask … Read more
Yes absolutely, It would be great to abstract away your queries at a single place. You might also use caching in your repository.
Log queries: You could collect all the queries during core/plugin/theme upgrades to see what happens. Just follow these two steps: 1) You should add: define( ‘SAVEQUERIES’, TRUE ); to your wp-config.php file to collect all queries during a page load into the $wpdb->queries array. Just remember to remove it afterwards. 2) Then you could log … 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/
Okay, looks like this is a problem with windows. I tested this now under linux and it worked like a charm. I have no idea what is causing this, but that specific plugin which is problematic is looking wired in svn anyway. So solution is to use a SVN client on linux. It just works.
you have to commit the changes to the /trunk directory yourself, changing the version number in the /trunk/readme.txt is not going to do this on its own. Update Whenever i update a version say from 1.0.0 to 2.0.0 i first create a directory in /tags and name it just like the last version 1.0.0 the … Read more
Comparing how your plugin is diplayed with your neighbour on the list here https://wordpress.org/plugins/search.php?q=custom+fields+taxonomies+light, they have 2 images on the CSS inline script, and yours only show one, the other background image url being empty. Yours: background-image: url(//ps.w.org/filter-custom-fields-taxonomies-light/assets/icon-256×256.png?rev=1110269 background-image: url() Theirs: background-image: url(//ps.w.org/advanced-custom-fields/assets/icon-128×128.png?rev=1082746 background-image: url(//ps.w.org/advanced-custom-fields/assets/icon-256×256.png?rev=1082746 If you are sure you uploaded that 128px image, in … Read more
The easiest thing I think is to ask wordpress.org if it’s possible that they host your plugin with GPL v3+ compatibility. Probably they say yes. Give it a try, the discussion was very new back in the end of January so points of views might be a bit more settled these days. IMHO there is … Read more