Should warn People !!!!
-
from looking around I see that many , many people are having issues with 3.9 update… not having used wp all that long and having no issues with previous updates I just updated all websites, now I’m in real trouble because none of them are working (visual editor issues) I certainly would have appreciated some warning that this update is obviously a beta version and not stable.
Is there any way I can go back to 3.83 if I didn’t back up the files?
Thanks;
-
In future, don’t update the development versions of your sites until majority of the bugs have been fixed. Check the forums for any existing known issues before updating your own site.
There’s no need to rush into a new update.
Then it should be said this is a “ddevelopment version” and I was afraid this would update automatically and I would be in trouble on all sites, something else they should have explained before updating to version 3.7
Obviously I’m not the only person having this issue… http://goo.gl/UTnl0f What’s wrong woth leaving in Beta until known bugs are worked out?
If you’re not using the dev version, please don’t post in ALPHA/BETA 🙂
That’s why Evan, rightly, assumed you were on a dev version 😀
Sadly, a handful of people have had issues with 3.9 and the post editor.
The tl;dr is that a plugin (or theme) you’re using is breaking the visual editor. The best way to diagnose would be via your browser and the console. We have some directions here:
https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors
Doing that will help you narrow down WHAT plugin it might be, as well as what it’s missing.
If that doesn’t help, make sure you’ve worked your way through the master list:
https://wordpress.org/support/topic/wordpress-39-master-list
Hate to break it to you, but the admin page is urging us (as of April 19) to update to 3.9 and says NOTHING about this version being in dev. If it’s a dev version, we should not be getting the “please update now!” message.
I updated, which could explain why I’m having problems with a new theme (posted elsewhere) that I just happened to install right around the time the update occurred. It’s one thing to bug fix from one direction, but now I have to wonder how much of this is because of the update. And yes, I’ve checked my plug-ins…
cc
3.9 IS NOT a dev version, ccpetersen
doug2523 originally posted this topic in the Alpha/Beta thread. I moved it because people like Evan assumed he’d accidentally installed the alpha/beta.
3.9 is out and solid and released and just dandy 🙂 If you’re having your own issues, please make a topic for it for yourself, unless it’s this one: https://wordpress.org/support/topic/confounded-site-title-font-size?replies=2&view=all
If it’s that one, please stick with it. People get spread too thin to answer the same questions in a dozen places (I just deleted one of those…)
OK… you can move it where ever you want to Ipstenu, I really don’t care!
I am having “my own issues” with it and have made “a topic” unfortunately, people such as yourself are only able to offer the same ineffectual advice as you are.
I have ZERO and I repeat ZERO plugins running on a site that is using Customizer (I think over 500,000 installations +/-) and I have changed themes in addition to re-installing wordpress 3.9 and the visual editor is still not working.
Given the number of people having similar issues, I would suggest that a very clear warning about this update should have been posted and in this persons opinion wordpress should not be encouraging people to up date to 3.9 as it is.
The fact that you think this release is “just dandy” is subjective at best. At this point I would definately use other words to describe it because it has cost me many hours of frustration.
If you have anything constructive to offer as opposed to moving conversations around and deleting others I would like to hear a legitimate solution to what appears to be a widespread problem.
Regards;
Every time WordPress makes any sort of changes to the visual editor, it is going to “break” for some number of people. This isn’t actually WordPress’s fault, it’s because your browser or some other system is very likely caching the old javascript and not getting the new code from the site.
Most often this is because the site is using some kind of “optimization” or “speed” or “SEO” plugin that isn’t handling things correctly. Sometimes disabling these plugins for a while will do the trick, other times you will need to find .htaccess files they wrote on your server and delete or edit them to remove the excessive caching rules, and often you will need to clear your browser cache as well.
The thing is, WordPress can’t control what plugins do, and many plugins do silly things above and beyond what is really necessary.
Standard debug rules apply: Disable plugins, switch to the default theme, clear your browser cache (twice), and check for any extra files (.htaccess) added by other systems that may be screwing things up. If you have any sort of “caching” service like CloudFlare or anything else, flush that cache.
Once you’ve got it working properly, then turn everything back on one at a time, until it breaks, and then you know what is the cause of the problem.
Also, in this particular case, the TinyMCE editor got a major overhaul. Any plugins you might have had before that changed the Visual Editor in any way will likely not work anymore. So, deactivate those. I know you said you have no plugins, check anyway.
And the bottom line is simple, really: This is a forum for providing support and solving problems. Just coming in here and complaining and saying “it’s broke, fix it” at the top of your lungs is not actually going to solve your problem. See, it is not broke for the vast majority of people. You, along with everybody else having a problem, is a special case. You may see a lot of people having problems in this forum, but again, this is a support forum. People only come here when they have problems. WordPress 3.9 has been downloaded almost 2.5 million times already, if it was a problem for everybody, then it would never have made it out the door.
Realistically, this has been a reasonably smooth update, all things considered. I expected much more in the way of issues. As is, it’s mostly been incompatible plugins and old theme code causing the major problems.
Thanks for your thought Samuel. I tried all of the above mentioned to no avail so I deleted the entire site and reloaded an older version of wordpress. This has a least solved the problem on that particular site. One down 4 to go. Fortunately I only installed 3.9 on two of them.
Problem is I am not a programer and am just learning how to use wordpress, had I known this was a “major” update and possibly not compatible with plugins and or themes I would not have installed it… it’s that simply.
Your response to suggesting I’m “yelling it’s broke just fix it” is to me really quite immature and a dumb thing to suggest. I simply wish that whoever is responsible for making a new release of this magnitude had mentioned that there may be problems and to possibly wait and or try it out on a test site or something.
Enough said, so far I, personally, am not a fan of wp 3.9 because it just caused me 3 days of work that I could have spent doing other things and to realize that had a simple caution warning been put forth before upgrading would have helped the situation to the point where I wouldn’t have wasted three days of my life needlessly.
Doug,
It is always best to first make sure plugins are up to date with the latest version of WordPress. Some plugins that are not up to date with the latest version of WordPress may work when WordPress is updated while others will not.
Also, you need to learn about how the software version works. If 3.8 is upgraded to 3.8.x then it is a minor upgrade/update. However, if 3.8.x is upgraded to 3.9 then it is a major upgrade/update.
I wouldn’t fret over this because this is a good experience for all WordPress beginners.
Yer right… good experience, now I know all that 🙁 I think the part that caused me the most grief though was this automatic update… I felt I had to upgrade at least one site before the “automatic update” updated all four sites.
I know that it’s good experience however I would like to be the one that decides when I need to learn something. I don’t like this auto update and I still think there should be a warning when and if an update potentially effects the functionality as is the case with the issue many are currently having with the visual editor.
One of the themes I am using is itself beta and the use of some plugins is necessary for the theme to work. The theme author is already up to his ears fixing a wide range of bugs.
I realize now that the wp update won’t update major updates and that it is possible to turn the update feature off however I think that the update feature should have been optional and at the very least explained with the release of 3.7 or whenever it came out.
I mean to say, I can’t be the only person learning wordpress and I can see throughout this forum that I am not the only one having problems.
I sincerely do appreciate everybody on this forum and the help they provide live and learn I guess 🙂
It is possible to turn off the automatic update feature, but then you’ll be responsible to ensure that all plugins and WordPress versions are updated.
If the theme you are using is in beta, then I hope you are not using it to produce a website that you want to be live.
Every time there’s a notification of a new release in the Admin backend, there’s a link/button to learn more about the new release. Most people do not click on this link/button and go straight for the Update button. It is beneficial to take at least five minutes to read information on the new release.
Oh, by the way, beta versions of WordPress are NEVER given as an automatic update as the user has to download them.
The topic ‘Should warn People !!!!’ is closed to new replies.