Thread Starter
rwilki
(@rwilki)
forgot to mention, I’m using chrome…
Thread Starter
rwilki
(@rwilki)
just tried this line in wp-config file
define(‘CONCATENATE_SCRIPTS’, false );
but did not work…
The bug is recorded here http://core.trac.wordpress.org/ticket/23337
but I don’t understand what to do with the code from github. Any help would be great…
Thanks,
Bob
Thread Starter
rwilki
(@rwilki)
tested in my browser on tinyMCE site and works fine…
Thread Starter
rwilki
(@rwilki)
can I download tinyMCE manually and apply to wordpress somehow?
Thread Starter
rwilki
(@rwilki)
Thanks but tinyMCE isn’t really a plugin. It’s built into the core. Are you suggesting I download it and install as a plugin?
I’d like to chime in here on this issue. I’ve noticed this on a number of sites I’ve built now. I find myself using the plain text editor as opposed to WYSIWYG. @rwilki, have you figured anything out on this?
Thread Starter
rwilki
(@rwilki)
thanks for your email inhouse. Nope. sadly, the annoying tinyMCE editor is still a piece of garbage in chrome. I can use the text editor no problem, for that matter I could just do all my coding in dreamweaver but the idea that as a CMS it’s supposed to be a reliable Wysiwyg editing tool – it is not.
my customers come to me for a CMS solution and for the most part, wordpress is second to none. but I’ve had many complaints about how the editor behaves and all its associated quirky behavior.
supposedly, the new release will have the fix for chrome backspacing + delete but I never hold my breath.
my dream for wordpress is to have a reliable, stable, cross-platform, cross-browser editor before they keep putting new bells and whistles into the application. it’s strange that on tinyMCE’s website, the editor works quickly and flawlessly.
thanks again,
Bob
I noticed that as well on the TinyMCE website. It also looks a lot nicer too! I’ve had a few complaints about TinyMCE from clients as well. I noticed CKEditor that replaces MCE with a completely separate editor in case that’s of any interest to you.
Thread Starter
rwilki
(@rwilki)
thanks. i’ve used it in the past. how’s it working? are your customers happy with it?
thanks,
Bob
I don’t use it myself. I just came across it today as I was researching the <em id=”__mceDel”> issue. I really don’t want to have to start using an entirely new editor as it would mean I have 2 systems to answer support questions for. I’ll stick it out with TinyMCE and hope it’s fixed for the next core update. Generally, I’m ok with it as the bugs are pretty small aside from this <em id=”__mceDel”> issue.
Thread Starter
rwilki
(@rwilki)
exactly the same thing with me. it seemed fairly stable but it wasn’t perfect and it meant I needed to stay on top of two editors. I don’t know why more time isn’t devoted to improving the editor (and I’m not talking about the html, plain text editor)
guess it’s what we live with… : /
@rwilki: Have you tried:
– deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).
– switching to the default theme to rule out any theme-specific problems.
– resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.
– re-uploading all files & folders – except the wp-content folder – from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones.
Thread Starter
rwilki
(@rwilki)
thanks Esmi for your reply. I’ve done all of the above. I’m not telling you I’ve done it on every site but I know for a fact that it’s buggy for me. The chrome bug is a recorded problem so unfortunately, not just my own situation.
in the past, i’ve spent countless hours trouble shooting this and I’ve come across the same problem.
here’s the bug tracker link.
http://core.trac.wordpress.org/ticket/23337
Looks like you’ll need to wait until 3.6 or 3.5.2 – whichever is released first.