Xarigami

project tracker

xarTinyMCE [key: xtm]

All trackers
Summary
Issue List
Road Map
Changelog

Issue xtm-000738

Issue summary Details
Project:
xarTinyMCE
Key:
xtm-000738
Type:
Bug
Reporter:
Lakys
Priority:
Normal
Severity:
Major
Status:
Closed
Resolution:
Fixed
Owner:
Lakys
Due:
- xarTinymce 3.3.0
Milestone:
None

Data not saved if css/js set display to none

Reported:  Jan 24, 2011 12:01 PM    Updated: May 6, 2012 05:16 PM by

Closed: May 6, 2012 05:16 PM    by Jo

Version affected: - xarTinymce 3.1.2

Using some forms with dynamic data fields, and TinyMCE, it is sometime convenient to use some toogle javascript function to unfold/fold some fieldsets in forms.

In previous versions of TinyMCE, the fields were always saved, even if the page loads with a fieldset having a style property display: none, or even set off by javascript at DOM ready event.

Now with the new version, TineMCE fields being at one moment set to display none, are not sent back and saved. This means that even all the page is unfold at load time, suffice you toogle and fold a fieldset, the tinymce data field within won't be saved too.

While this behavior may be considered as a feature to prevent hidden data to be override because it "cannot" be modified (well it is hidden), it ends to be dangerous in the use case above.

If this new feature is manageable, it should be integrated in the configurable parameters in configs, and turned off by default, to prevent functional forms to become broken during a simple TinyMCE module update.

Actions

Is this a bug while turn off editor while editing existing article new value will not be save?

#

[Issue assigned to Lakys by Lakys]

#

Confirmed Lakys Nov 3, 2011 11:19 AM

I found that bug too, I had it on a client site and I had to keep fields not hidden.
Was indeed at the beginning of the year too.

Thanks for reporting it.

#

info from Jo Lakys Nov 15, 2011 02:09 PM

Revision: e4c45c667077b5d6843e3807c244824e097a3a1a
| Parent: 3eb670091545a9d5bd6ae0c5ffb8b21a3ae0353b
| Author: icedlava@2skies.com
| Date: 13/03/2011 10:55:22
| Branch: com.2skies.xarigami.modules.tinymce
|
| Changelog:
|
| Update to upstream tinymce 3.4
that is where it breaks for me
prior to that it is ok
at that revision only the moxiecode tinymce code changes are added for their release 3.4
a major release
http://www.tinymce.com/forum/viewtopic.php?id=25112

#

Similar issues in Drupal Lakys Jan 19, 2012 03:32 PM
In wordpress Lakys Jan 19, 2012 03:36 PM
A workaround (thanks to Jo) Lakys Jan 19, 2012 04:31 PM

This seems to be fixed in the latest upstream tinymce code, now in xartinymce module. Please confirm if you can.

#

Issue closed by Jo

#