Edit line 149 in file.php as described in this thread: https://wordpress.org/support/topic/unable-to-update-plugins-after-upgrade-to-42 fixed it for me (on a linux host). edit: just read you are on windows: someone also posted a fix that applies to windows hosts there (apparently more complicated because backslashes are used in filepaths). so your line 149 in file.php should read: if … Read more
The bad news WP doesn’t track this information persistently. It only keeps the technical representation of active plugins to load them. The rest is only looked up in specific contexts (such as plugin management admin panel), because it’s relatively heavy on resources. The good news is that you can certainly rebuild this functionality in arbitrary … Read more
It is EOL. WordPress will backport security fixes when it can, but makes no promises for updates for anything except the latest version. You should have updated 3 years ago. WordPress will be backported security updates when possible, but there are no guarantee and no timeframe for older releases. There are no fixed period of … Read more
You can always use GitHub. WordPress has an official (view-only) GitHub repository, and GitHub has an excellent comparison feature. Here’s the GitHub comparison of WordPress 3.4.2 vs 3.5.
Release Date: WordPress 4.0 is planned for August 27September 3, 2014 Source WordPress 4.0 Release: […] For those unaware, for WordPress, version 4.0 sounds like a “big” version number but it’s just another major release for us, like 3.9 and 4.1, constructed over the same ~4-month release cycle. […] Source For WordPress 4.0 features follow … Read more
are the updated newer major-versions significantly more secure than updated older ones? This is quite ambiguous. How significant or insignificant security changes might be, it is totally irrelevant. There might or might not be significant security enhancements between minor and major versions or even major versions as such. To really know how significant changes are … Read more
Usually a plugin developed in WordPress version will run fine on several newer versions. What you need to care about is ‘deprecated` features/apis in WordPress. Any API in WordPress is not removed overnight, rather it remains deprecated for several versions. You will get such a list here: http://codex.wordpress.org/Category:Deprecated_Functions When you develop a plugin, you can … Read more
Codex (official WordPress documentation wiki) has a list of WordPress Versions with links to changelogs and release posts for each. Though information in those changelogs can be lacking. Note that WP doesn’t follow semantic versioning or resemblance of. Every version is a minor one and there are no major versions, so 3.9 was simply followed … Read more
I maintain WordPress Bengali project and yesterday I pushed the 3.9 translation update from bn.wordpress.org. You are right, there are no 3.9.x branch there so it’s pretty much not clear to me as well. Here’s how it works: we should always translate from the Dev version. When a new release comes, there is a SVN … Read more
There’s a page in the Codex that shows exactly that: WordPress > About » Statistics But really, it all depends on what features you’re using. A safe bet for a new plugin would be to support WordPress 3.1.X and above (since that’s the current stable release). You’re setting yourself up for a lot of hurt … Read more