We found that there were some things that we had to remove that were breaking the DCR load, so we removed them, but the config changes are still in place and are working for the toolbar customization and styles.
but the config changes are still in place and are working for the toolbar customization and styles.
TeamSite 6.7.2 SP2 on Solaris 10We recently upgraded from 6.7.1 to 6.7.2 SP2 and are verifying the results of the upgrade. One thing we just found is that if we edit an existing DCR that contains a TinyMCE field, changes to that field are not saving. We can update all other fields in the DCR and when we save the DCR, the change is saved and when we reload the DCR, we see the changes. If we do this in the TinyMCE field, the change is not saved and is gone when we refresh the DCR. Has anyone seen this behavior in the past?Thanks in advance for assistance with this!
i know this is an old post, but we have almost the same issue. let me explain:1- editor opens a DCT, add some content then saves the dcr => good the content in tinymce is saved.2- editor adds more content to the tinymce field , saves the dcr => this time the content within the tinymce is not saved.3- if the editor closes the form completely then add content to the tinymce field it works as step one but the second time he saves the content it is not saved.so i am currious if you were able to resolve the issue or not. by the way this happens in tinymce field no matter what location we put it in. ( for example in container or outside the container. the first field in the form or the last field. )
i know this is an old post, but we have almost the same issue. let me explain:1- editor opens a DCT, add some content then saves the dcr => good the content in tinymce is saved.2- editor adds more content to the tinymce field , saves the dcr => this time the content within the tinymce is not saved.3- if the editor closes the form completely then add content to the tinymce field it works as step one but the second time he saves the content it is not saved.
Is the focus still in the TinyMCE field when they do the save?If so, that's the source of the problem - have them click outside of the textarea and then save and see if that "resolves" the problem.This was supposedly fixed in an SP, but I don't believe that it is 100% fixed even in the latest release.