Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I updated to the newest version of WYSIWYG API yesterday. I use TinyMCE 2.1.3 for my edits. After the update was installed I am unable to make edits to posts. I make the changes and click save, but the content in the post stays the same.
Comments
Comment #1
bgregoire commentedWhile trying to fix the issue I added fckeditor 2.6.4 and adjusted my editor settings to use that instead. I am now able to successfully make changes to my pages and stories.
Comment #2
sunGlad you fixed it yourself. Support for TinyMCE 2 was actually implemented for testing reasons only. I have no real interest in fixing TinyMCE 2. Use TinyMCE 3 instead.
Comment #3
sethcohn commentedAfter having a client wonder why they couldn't save things (type text, submit, no change recorded), I discovered that while WYSIWYG API 0.5 did work correctly with TinyMCE v2, neither 1.0 nor 1.1 works correctly...
yet, this isn't listed in big bold letters on the project page, no warnings, and the code continues to recognize and list v2 as supported.
I realize this is a "won't fix", but please fix the supported list of editors on the issue page and REMOVE v2 from that list, and put big bold letters saying it's no longer supported if you aren't planning on fixing this.
Comment #4
sunI'm not able to replicate this issue. Switched to TinyMCE 2 and can flawlessly create and edit content. The only thing I needed to do after switching from TinyMCE 3 to 2 was to recreate the wysiwyg profile.
Comment #5
sethcohn commentedWe had very inconsistent results, including some dev sandboxes able to use the editor, others not, and browser didn't matter (we tried multiple browsers).
I did delete and recreate the profiles, to no avail.
The fact it's inconsistent points to something, I think. For example, we noticed that the class selector dropdown would malfunction ($labels showing), but the editor would work, while in other cases, the class selector would work correctly, and the editor would refuse to save.
Downgrading from 1.1 to 0.5 'fixed' the problem, while going to 1.0 didn't, so that points to something in the current codebase, likely added in v1 but not in v0.5.
Comment #6
sunI can only imagine that you are experiencing #379182: TinyMCE stopped showing in languages other than English on some of those sandboxes then. Thus, marking as duplicate.