The compatibility shows just the latest version the plugin was tested on. If WordPress didn’t change the API the plugin will continue working and you don’t have to worry. Test it. There is no other way to be sure.
Short answer is no — there is no way to completely and reliably prevent your public plugin/theme coming up as duplicate if WP org thinks that it is. There are limited things you can do while it’s active (intercept update requests, unfortunately there isn’t even canonical up–to–date tutorial on that), but that goes out of … Read more
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.
Typically any plugin changes take 15minutes to be reflected on the plugin’s pages in the repo. Did you upload the screenshots and header image to the /assets/ folder of the repo?
As long as everything was made according to WP best practices all your manually installed versions will update the same as the ones installed from wordpress.org. The updater looks at many things to identify your plugin. However, the most important is the plugin URI (you can change the directory of many plugins and they will … Read more
You can try out the api.wordpress.org. Take for example the secret MP6 plugin: http://api.wordpress.org/plugins/info/1.0/mp6.xml The current version is given by: <version type=”string”> <![CDATA[ 0.8 ]]> </version> and it looks like the previous versions are listed in the compatibility tag: <compatibility type=”array”> <array key=”3.4.1″> <array key=”1.0.0″> <integer>100</integer> <integer>1</integer> <integer>1</integer> </array> <array key=”1.0.1″> <integer>100</integer> <integer>1</integer> <integer>1</integer> </array> … Read more
This is because you directly call a PHP file from within your plugin folder. This is bad for two reasons, the first being that some people block direct access to PHP files inside the wp-content folder. The second is you need to include wp-load.php to access the WordPress API. Instead of linking to… site_url().””.”/wp-content/plugins/Printer-Friendly-WP/print.php?id=page_id=”.””. get_the_ID()` … Read more
The currently required minimal PHP version is still 5.2.4+. The recommended version is 7. According to archive.org since December 2, 2016. Note that many plugins and themes need at least PHP 5.4 or newer nowadays, and that PHP versions below 5.6 do not get security updates anymore and are therefore probably not safe for production. … Read more
WordPress.com is web service. WordPress.org is software product. Think bus vs car. You can ride both, but bus is owned by someone else and what you can do with it is limited.
Disclaimer: I am not a lawyer. The issue here is the Apache license. You are free to distribute your own work under as many license varients as you want. After all you retain copyright. But if you include other peoples work in the distribution, every license varient you distribute under needs to be compatible. However, … Read more