Item8094: Pickaxe editing doesn't work on trunk
Current State: Closed
Since the upgrade to the latest TinyMCE
, pickaxe editing no longer works.
When you edit using the Wysiwyg, then click the pickaxe, and then make changes, when you click save, the page will be saved as it looked when you clicked the pickaxe, and all the changes you did in raw TML view are lost.
I tried that on FF on windows and linux, and on Chrome on windows, and all fail. It couldn't try on IE on windows because there doesn't seem to be any pickaxe on IE7.
- 01 Apr 2009
I can confirm this in trunk.
Including the below content in TML will invoke the plugin to include a protected
---+ This is a test
---++ JQuery another test here
---+ 2nd h1 header
The content saves fine, but does not render in
. When user goes back to
the file in wysiwyg mode, all content is still there, including
being protected. Problem happens after clicking pickaxe, and the
This is the same for
* A description of below
* Set VARIABLE = whatever here
will not be saved properly or rendered.
Forcing the user to use TML mode only works as expected.
Fixed by poking TMCE in the naughty bits until it squeaked.
- 03 Apr 2009
I am reopening this task because the original problem (When you edit using the Wysiwyg, then click the pickaxe, and then make changes, when you click save, the page will be saved as it looked when you clicked the pickaxe, and all the changes you did in raw TML view are lost) is present on trunk.
I noticed that the "Wiki text" edit text-box shows HTML very briefly when I click save. I don't really mind the brief appearance of the HTML, but the HTML did not include the change I made in the "Wiki text" edit box. I suspect that might be a problem.
Howevr, if I click on the "Wiki text" button, make some changes and then click on the WYSIWYG button, the changes are transfered to the WYSIWYG editor, and they are saved if I hit the WYSIWYG "save" button.
- 26 Apr 2009
- Set TINYMCEPLUGIN_DISABLE = 0
Interesting. Works perfectly on my server, but not here :-/
Nothing in the apache logs, nothing in the error console, same browser. Are you using the FoswikiSiteSkin, by any chance?
- 29 Apr 2009
This was fixed on trunk somewhere between revisions 3746 and 3794 (probably related to CrawfordCurrie
's 3777 checkin. Changing to closed.
- 01 May 2009