The RC2 version of WordPress 4.0 is now available and the machines are being prepared so that tomorrow the final version, ready to install publicly, of WordPress 4.0 is ready , so stay tuned to your WordPress desktop 🙂
The first RC version of WordPress 3.8 has just come to light, that is, the first version already with all the new features incorporated, ready to start making compatibility tests of each to release of the final public version, scheduled for this month .
That said do not expect more news in WordPress 3.8 than those already announced with the first beta, but if it's a good time to load it on a test site and check if it will get along with your current theme and plugins, then do not scare .
As you already know WordPress from the version 3.7 is updated only to the minor versions (from 3.7.x to 3.7.y), not so to the major ones (from 3.7 to 3.8), so you will have to make the decision at the time of whether to update or not, although you already know that my advice is that if you do it.
Although we almost gave it up for lost, it seems that the version WordPress 3.6 follows its course and at a good pace, despite having to change the plans for the withdrawal of the formats interface of entry .
In a statement a few hours ago has been made a review of the pending tasks, confirming that there are less than 40 open tickets and, most importantly, that this very Friday the first RC version ( release candidate or candidate for publication ) may already be available.
This only means that, if nothing is broken, we will have the final version of WordPress 3.6 before the end of July so we can enjoy it all summer.
Just released a few hours ago the RC2 version of WordPress 3.5 which is fine-tuning more details for the planned release of the final version of WordPress 3.5 scheduled for December 5 .
Ea, which is already the last previous version, RC3 the next one will be the final version of WordPress 3.4 (I bet something). If you want to give it a try you already have it for download and try and if not, wait until the definitive one comes out this week and you will be able to enjoy the news from WordPress 3.4 . In the meantime you can try it here .
If you are one of the impatient ones you already have available the ready version to publish 3 (or RC3) in direct download in this link . But, you know, you wait very little and the final version of WordPress 3.1
will come out. This is an original content of WordPress Help – Resources, themes, plugins and tutorials in Spanish and published it Fernando Tellado first here: WordPress 3.1 RC3
As always, when the final version of WordPress is available, whatever version it is, is when we start to update our sites, without testing betas or RCs without checking the compatibility of plugins, and it happens what happens, that the first failures begin to appear, previously undetected because the user base testing the version was not enough … until the final version does not come out. It always happens.
Well, if you have not yet updated to WordPress 3.0 you should know that there are several plugins that are causingblank pages . So far we have seen errors in plugins as common as Event Calendar, HeadSpace2, DBcache or Podcasting plugin.
Regarding the translation has also been a failure, this time mainly due to the change of publication system of the translations that, due to general ignorance and some other detail, has caused some other sustillo, fortunately nothing important, as it appears as version 3.1 Alpha, although we have updated "correctly" to 3.0.
The issue of memory failure It has an easy solution, which we have already commented on at some other occasion. If you get the ugly message of " Fatal error: Allowed memory size of xxxxxxx bytes exhausted (tried to allocate xxxxx bytes) in /home/loquesea/public_html/fulanito/wp-admin/includes/ficheroquesea.php on line xxxx "you can do a couple of things to solve it:
In the file
wp-settings.php modify the default value to increase the memory to something like this:
if ( ! defined ( 'WP_MEMORY_LIMIT' ) )  define ( 'WP_MEMORY_LIMIT' '64M' ) ;
If what has surprised you is a blank page, follow this checklist .
And, of course, report the failures to the development team .
These failures will be resolved in no time, as always, something that is the greatness of the WordPress community, that while we complain there are people who, altruistically, are taking hours to solve these failures as soon as possible.
Of course, again, remember that you should NEVER update without having done tests before and without making a backup, and even less compromising a site in active, much less if it is of a client. This is valid for WordPress and for any software, offline or online.