[wp-trac] [WordPress Trac] #46442: Visual Editors stopped working with WordPress v5.1

[WordPress Trac]

#46442: Visual Editors stopped working with WordPress v5.1
--------------------------+----------------------
 Reporter:  burningthumb  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:  5.1
 Severity:  major         |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------

Comment (by CarolKn):

 Replying to [comment:28 smartabhay27]:
 > so what do you suggest i should do ?
 >
 > my hosting team has clearly denied any error from their side and any
 insertion of pixels etc and none of the error logs state any
 error...except that iam hitting max 1GB RAM limit which is strange since
 my site is very very basic.
 >
 > Also note my issue is that iam unable to update my homepage where all
 other pages are getting updated easily.
 >
 > i have deactivated all plugins but still error is there...as per hosting
 team i need to upgrade to a higher RAM plan but thats not a solution since
 my site is very very basic so why is it eating so much RAM with hardly any
 plugins and images on my site ?
 >
 >
 > Replying to [comment:27 azaozz]:
 > > @CarolKn and @knutsp are right. This is not an issue in WordPress.
 It's not even an issue exactly with the web hosting companies, it's some
 software they are using turns out to be buggy.
 > >
 > > @smartabhay27 imagine the post office opening your letters, cutting
 them in half and sticking a paragraph written in... Latin in the middle.
 Would you blame the sender of the letters then? :)
 > >
 > > I have no idea why somebody would append a HTML string in the middle
 of a JavaScript file. This is bound to fail in almost all cases. Perhaps
 they had a good reason for doing it, but... It breaks sites.
 > >
 > > I also don't know why this started happening now. The file being
 affected is not from WordPress itself. It comes from the TinyMCE open
 source project and WP doesn't modify it in any way. My guess is that it
 started matching some sort of pattern so the pixel inserting software
 decided it's OK to add HTML tags there. I'd like to repeat that inserting
 HTML strings in JS files seems like a really bad idea in the first place,
 and that software should be fixed.

 @smartabhay27 it sounds like you may have a different issue. I could not
 edit ANY page or post of the problem website with the visual editors.

 TinyMCE had significant changes that were put out about the same time as
 WP 5, and as @azaozz writes, it's likely the new code triggered the
 insertion by the stat software. When I used web developer console to look
 at the errors, it pointed me to the file that was corrupted. When I
 finally actually looked at it (who looks at minified files!?) it was
 obvious why it wasn't working: massive code insertion that didn't belong
 in a JS file. I couldn't see it via FTP because it happens between the
 server and client as the page is rendered. I'm sending these details
 because at the point where I saw the bad code, I could have sent that to
 my hosting company and proven that it was their software that caused the
 problem. Fortunately I didn't have to do that and fixed it myself in about
 5 minutes. You should be able to follow those steps to debug your problem
 to confirm whether this is indeed the issue or ascertain whether there is
 a different problem on your site.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46442#comment:30>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform