Stephen Edgar

If that site has now reverted back to 3.9 you should have two options available:
1: Re-Install 3.9.1 en_GB
2: Re-Install 3.9.1 en_US

Try installing the en_US version and once complete you should still have the en_GB option available.

@hlanggo My previous comment was based on the codex article you linked to before editing your post 😉

Thank you so much for helping. I have just done one site and it seems to be OK.

Cool and your welcome 🙂

I changed the the wp_version in /wp-includes/version.php from 4.0-alpha to 3.9 as instructed. It immediately told me there was a new version vailable and prompted me to upgade to 3.9.1 which I did. Does it work if you change the version to 3.9.1 in version,php? Would it be a bit quicker.

Not really, not entirely sure, I haven’t tested this, in theory I may be slightly quicker though I’m not sure you would notice.

As stated I haven’t tested this method and I’d suggest staying with the method we have tested, compounding any issues here is not what we want right now 😉

Also how long before the others get auto updated to some beta? as it’s the middle of the night and I want to go to bed!

I haven’t tested this for a while but I think it will deliver the latest ‘nightly’, thus this is a once per day update.

If you need to scoot off for the night, that shouldn’t be an issue, the same process to fix it will work tomorrow. 🙂

Hi Lepussaliens,

I have just downloaded the updated 3.9.1 en_GB package to confirm it is the correct 3.9.1 version and it is.

Once you have followed the steps outlined in the post I linked to above your site will be restored and working as you expect it should work and you will not automatically be upgraded to future beta versions etc

I agree with your statement that you should be able to upgrade effectively without any code editing. I haven’t spoken to the en_GB team directly but passing on my apologies on behalf of them anyway, I know they are sorry for the mishap and it indeed it is not what most people want or expect from WordPress.

We are changing the way these updates are packaged and deployed for WordPress 4.0 so the fixes to prevent this from reoccurring.

To reinstall follow the steps I have in this post:
https://ww.wp.xz.cn/support/topic/updat-wp-39-installed-40-alpha?replies=21#post-5470519

I’ve done an immense amount of testing of the new TinyMCE with bbPress and the link I listed above combined with WordPress 3.9 and bbPress 2.5.3 works perfectly as is.

I haven’t tested it with BuddyPress, yet, I will get to that eventually.

That said all the errors you list above relate to either ‘cubepoints-buddypress-integration’ or ‘cubepoints’ plugins.

As you rightly point out most likely that is an issue for sure, try disabling the cubepoints plugins, also I would suggest posting what you have above to the cubepoints plugin support forum.

This isn’t a bbPress issue, bbPress works fine with TinyMCE 4.0 included with WordPress 3.9 with the method outlined above.

I’ve done quite a bit of testing with the new TinyMCE and bbPress, the previous version of TinyMCE gave us quite a few compat issues and that is why it was removed in bbPress 2.3.1. I am hoping with the improvements we can once again enable it as an option in an upcoming bbPress release.

I haven’t tested this plugin or compat with any other plugins in this regard, just bbPress core and WordPress core.

http://codex.bbpress.org/enable-visual-editor/

@reinasc That has nothing to do with this topic, this topic is only to do with incorrect translations delivered from a couple of custom localized WP 3.9 builds.