WordPress.org

Make WordPress Core

Opened 2 weeks ago

Last modified 5 hours ago

#46442 reopened defect (bug)

Visual Editors stopped working with WordPress v5.1

Reported by: burningthumb Owned by:
Milestone: Priority: normal
Severity: major Version: 5.1
Component: Editor Keywords:
Focuses: Cc:

Description

When I upgraded to WordPress v5.1 both the classic and gutenberg visual editors stopped working. In the classic editor I would get no buttons, a tinyMCE not found error in the browser console, and a blank edit area. In Gutenberg I would get a completely blank screen, there was also JS console errors for undefined symbols. In both cases I could click and drag to see the text was there but was white.

I was saved by the WP Downgrade plugin which I used to downgrade from v5.1 back to v5.0.3 where the visual editors are working again.

I worked on this for almost 3 days. Very, very, annoying.

As a test, I reinstalled v5.1 and the editors stop working, then I rolled back to v5.0.3 and they start working again. Its repeatable at will.

Change History (26)

#1 @burningthumb
2 weeks ago

My hosting company is Telus. I mention this because on godaddy.com I have upgraded to v5.1 with no problems so maybe its something specific to hosting companies / resources. I don't know. I raised a ticket with Telus and they were completely useless.

#2 @CarolKn
12 days ago

Same issue with a site on ATT hosting. A nearly exact copy of the site on A2 works fine, as do other WP 5.1 sites with same theme and plugins on A2, Siteground & Hostgator. I disabled all plugins, replaced all WordPress core files - to no avail. I am getting SyntaxError: "" string literal contains an unescaped line break in mce-view.min.js:1:5816, but replacing this file (or tinymce altogether) with a known good copy from 5.1 does not fix the problem. Text editor works fine; visual editor link doesn't work, and Gutenberg displays a white screen (view source has content.) Have installed Classic Editor plugin, but reinstalling, disabling, changing settings doesn't have an effect. I am reluctant to back out to 5.0.3 since this is a live site and the public display is not affected. Both the copy and live site are running php 7.1.

Last edited 11 days ago by CarolKn (previous) (diff)

#3 follow-up: @usmc1
9 days ago

I have been running a website on WordPress(then at v5.1) using the theme Esteem (v1.4.2) by Theme Grill using Firefox v66.0b13. Two weeks ago I started getting a white screen when I try to edit any page. I can’t think of any change that might have led to this (e.g. new plug-ins). Interestingly, the widget that allows a common block to be displayed on all pages was still editable.

I tried the following, none of which have worked:

  1. cleared my browser cache
  2. deactivated all plug-ins
  3. changed the theme to Twenty Nineteen
  4. reverted to Classic Editor
  5. used Internet Explorer and Edge as alternative browsers
  6. logged in via my mobile using Chrome
  7. called the host support but they cound't find any issues at their end

Health Checker didn't show up anything untoward.

I got someone to investigate and it appeared that my host put tracking pixel code in too many files – including one called tinymce.min.js. This meant that that broke, so he turned the tracking pixel off and after some fiddling (not sure what) it worked. It then stopped working again on my laptop that evening but by the next day WordPress had been upgraded to v5.1.1 and it’s back working.

#4 in reply to: ↑ 3 ; follow-up: @burningthumb
9 days ago

I just tried v5.1.1 and the problem is still there on my host. Can you provide more details or a contact at your hosting company as its not clear what you mean by they put tracking pixel code in too many files.

#5 @CarolKn
9 days ago

The problem still exists on my host with 5.1.1.

#6 in reply to: ↑ 4 ; follow-up: @usmc1
9 days ago

Replying to burningthumb:

I just tried v5.1.1 and the problem is still there on my host. Can you provide more details or a contact at your hosting company as its not clear what you mean by they put tracking pixel code in too many files.

There's an option on my host's front end which offers the option to switch off the pixel tracking. It was a friend that fixed the tinymce.min.js file not the host. I can't help beyond that, I'm afraid.

#7 in reply to: ↑ 6 ; follow-up: @burningthumb
9 days ago

Its odd since I replaced the tinymce.min.js file with known good copy from a working site on godaddy.com (and I also ran a diff on the tinymce.min.js on both sites and they are identical) so I know tinymce.min.js is good.

Also since Wordpress v5.0.3 is working, the problem started with the v5.1 update, and both v5.1 and v5.1.1 are not I still think, even if something the hosting company is doing is the cause (which surely it appears to be), something in the Wordpress core can be / should be changed to fix it by reverting to whatever v5.0.3 is doing.

Replying to usmc1:

Replying to burningthumb:

I just tried v5.1.1 and the problem is still there on my host. Can you provide more details or a contact at your hosting company as its not clear what you mean by they put tracking pixel code in too many files.

There's an option on my host's front end which offers the option to switch off the pixel tracking. It was a friend that fixed the tinymce.min.js file not the host. I can't help beyond that, I'm afraid.

#8 in reply to: ↑ 7 @CarolKn
9 days ago

Replying to burningthumb:

Its odd since I replaced the tinymce.min.js file with known good copy from a working site on godaddy.com (and I also ran a diff on the tinymce.min.js on both sites and they are identical) so I know tinymce.min.js is good.

Also since Wordpress v5.0.3 is working, the problem started with the v5.1 update, and both v5.1 and v5.1.1 are not I still think, even if something the hosting company is doing is the cause (which surely it appears to be), something in the Wordpress core can be / should be changed to fix it by reverting to whatever v5.0.3 is doing.

Replying to usmc1: Same experience. Unfortunately our client wants us to wait until 3/25 to try rolling back to 5.0.3, so we wait...

Replying to burningthumb:

I just tried v5.1.1 and the problem is still there on my host. Can you provide more details or a contact at your hosting company as its not clear what you mean by they put tracking pixel code in too many files.

There's an option on my host's front end which offers the option to switch off the pixel tracking. It was a friend that fixed the tinymce.min.js file not the host. I can't help beyond that, I'm afraid.

#9 follow-ups: @azaozz
9 days ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Sounds like the hosting company is inserting/appending a string (tracking pixel) to the JS file? Ugh...

In any case, this doesn't seem to be an issue in core. Manipulating JS files is a big no-no! Please contact your host and open a thread on the support forum to track any progress.

#10 @burningthumb
9 days ago

So assuming this is the case, which seems reasonable, why is Wordpress v5.0.3 working but v5.1 is not? Would v5.0.3 not have the same problem if the hosting company, in this case Telus, was modifying the .js file? I need to be able to explain this to Telus support when I call them.

#11 in reply to: ↑ 9 @burningthumb
9 days ago

So I called Telus and they say they are not modifying the .js files.

azaozz:

Sounds like the hosting company is inserting/appending a string (tracking pixel) to the JS file? Ugh...

In any case, this doesn't seem to be an issue in core. Manipulating JS files is a big no-no! Please contact your host and open a thread on the support forum to track any progress.

#12 @burningthumb
9 days ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

#13 in reply to: ↑ 9 @CarolKn
9 days ago

Replying to azaozz:

Sounds like the hosting company is inserting/appending a string (tracking pixel) to the JS file? Ugh...

In any case, this doesn't seem to be an issue in core. Manipulating JS files is a big no-no! Please contact your host and open a thread on the support forum to track any progress.

@azaozz is correct. I looked more closely inside one of the affected JS files and found "WiredMinds eMetrics tracking with Enterprise Edition V5.4". Google search returns your host Telus as one host that inserts pixel tracking code willy-nilly into files, including the middle of JS files.
http://www.dslreports.com/forum/r28249867-BC-Telus-Hosting-what-is-this-code-on-our-web-pages

Solution that worked for me was logging into ATT hosting, finding Analytics, poking around till I found Web Analytics | Advanced | Manage Pixel Code. Set to off, clear cache, hard refresh on admin / editor and it's fixed.

Several other folks out there having similar issues... Curious why this is a problem all the sudden with WP.

Last edited 9 days ago by CarolKn (previous) (diff)

#14 in reply to: ↑ 9 ; follow-up: @CarolKn
8 days ago

Replying to azaozz:

Sounds like the hosting company is inserting/appending a string (tracking pixel) to the JS file? Ugh...

In any case, this doesn't seem to be an issue in core. Manipulating JS files is a big no-no! Please contact your host and open a thread on the support forum to track any progress.

Thank you @azaozz!

#15 in reply to: ↑ 14 @burningthumb
8 days ago

  • Resolution set to invalid
  • Status changed from reopened to closed

YES! This is it. I looked on Windows using the Edge Browser and indeed this is the case.

So I called Telus back, and this time they knew exactly what the problem was as well. They say the pixel track has always been on and its a problem with wordpress 5.1 and later.

Funny now everyone seems to know it.

I only had to talk to 3 people at Telus and two good folk here.

Rest easy.

Replying to CarolKn:

Replying to azaozz:

Sounds like the hosting company is inserting/appending a string (tracking pixel) to the JS file? Ugh...

In any case, this doesn't seem to be an issue in core. Manipulating JS files is a big no-no! Please contact your host and open a thread on the support forum to track any progress.

Thank you @azaozz!

This ticket was mentioned in Slack in #forums by ipstenu. View the logs.


2 days ago

#17 follow-up: @gcphoto
2 days ago

Does anyone know if this issue going to be addressed and fixed in the next version of WP or is it something that has to be addressed by the Web Host?

Thanks
Garry

#18 in reply to: ↑ 17 ; follow-up: @CarolKn
44 hours ago

Replying to gcphoto:

Does anyone know if this issue going to be addressed and fixed in the next version of WP or is it something that has to be addressed by the Web Host?

Thanks
Garry

Your best bet is getting it fixed by the web host.

#19 in reply to: ↑ 18 @gcphoto
43 hours ago

Replying to CarolKn:

Replying to gcphoto:

Does anyone know if this issue going to be addressed and fixed in the next version of WP or is it something that has to be addressed by the Web Host?

Thanks
Garry

Your best bet is getting it fixed by the web host.

Thank you, I did just that and it solved the problem. It was so easy to Fix but so Hard to Find.
Garry

#20 follow-ups: @smartabhay27
21 hours ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

same here iam also unable to edit on my homepage in version 5.1.1..can anyone plz help and support how to resolve..? iam struglling from last 10 days and i have to release my site urgently...

if its a bug in new version then what is the way to roll back to the older version ?

#21 in reply to: ↑ 20 @CarolKn
20 hours ago

  • Resolution set to invalid
  • Status changed from reopened to closed

Replying to smartabhay27:

same here iam also unable to edit on my homepage in version 5.1.1..can anyone plz help and support how to resolve..? iam struglling from last 10 days and i have to release my site urgently...

if its a bug in new version then what is the way to roll back to the older version ?

Assuming your problem is the same as above, your hosting company is causing this problem by inserting code into various files on the website. Call them and ask them to turn off tracking pixels. Tracking pixels are sometimes used to generate statistics, but in this case they are getting into places they shouldn't be.

#22 in reply to: ↑ 20 @burningthumb
19 hours ago

To my mind, not everyone will agree, its a wordpress v5.1 bug. My hosting company has had tracking pixels turned on for YEARS and previous version of Wordpress worked fine. I backed out to v5.0.3 and it works fine.

Having said that, the Wordpress developers are among those who don't agree with my assessment and as such are not, so far as I can tell by responses here, prepared to accept responsibility and fix the bug. So if you want a solution, as I and other did, get your hosting company to turn off tracking pixels / statistics, you are probably not using the statistics that it gathers anyway - I wasn't.

Replying to smartabhay27:

same here iam also unable to edit on my homepage in version 5.1.1..can anyone plz help and support how to resolve..? iam struglling from last 10 days and i have to release my site urgently...

if its a bug in new version then what is the way to roll back to the older version ?

#23 @smartabhay27
11 hours ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

#24 @smartabhay27
7 hours ago

can someone inform the process of rolling back to older version of wordpress and will that impact my functional site by anyways ?

#25 @knutsp
5 hours ago

  • Resolution set to invalid
  • Status changed from reopened to closed

Hello @smartabhay27

Since this is not a support channel, please search for this on the support sitehttps://wordpress.org/support/ or through a general search engine.

This ticket was, and should be closed because the OP's problem turned out not to be a core bug.

#26 @smartabhay27
5 hours ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

How can you say that its not a core bug..everyone on this forum is saying that they are facing updating issues in 5.1 version of wordpress...and you are just trying to pass on the problem on the hosting team..how was everything working fine on your older version ??

by the way i have already checked with hosting team...it has nothing to do with their pixels... its a core word press new version issue...either kindly rectify it or arrange to roll us back to the older version..atleast there should be a provision for us to use either a new verss=ion or a old version which ever suits our website..or else guide us with steps how to roll back to older version without impacting the site.

Note: See TracTickets for help on using tickets.