simonlange

No u r not. many ppl got this problem.

as said. the bug is always the same and it does not matter if u got 3rd party plugins installed or any installed or not.

you may find cases where a plugin may triggered the bug. as you find pretty easy cases where its not plugin related (just by the fact that they dont have any installed), which is destroying the theory that its plugins to blame. ??

same for themes or multisite/single.
the only common factor is the upgrade itself.

just read this thread even here we got (including me) ppl who got this bug with standard theme and no plugins running. i got plenty sites and all sites except one got this bug. funny. they all using the same configuration in the backend. same fpm configuration same php.ini same webserver. so right now i dont have any clue what is triggering this bug.

Simon

Jan wrote

OK. How did you come to that conclusion? I’m not saying you are incorrect but you’ll need more than “it’s broken” to make that determination.

its plain logic.
3.8.x worked
refering the reports just in this forum (or even just in this thread) it does not matter if u:
– have default theme or not
– plugins installed or not
– mutisite or not

the only factor they all have in comon is that they did upgrade frmo 3.8.x to 3.9.

a hotfix for the visual editor (rollback and maybe upgrade at a later stage) would be the best solution rght now.
guess u had reason to upgrade the VE but since its more unstable than stable it should not used in a stable branch.

m2c

Simon

its not plugin related its core related. please release asap a patch with a rollback for the visual editor.

tyvm

twenty 12….

as expected…. no change. ??

which is?