nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TinyMCE and Replicants

rsteeves

Greetings,

We are currently using TS 6.7.1 SP1, Windows 2003 Server. We are experiencing problems using TinyMCE inside a replicant. The first instance works fine. However, when you attempt to add another instance of the replicant, TinyMCE will not load, and all we get is a read-only textarea. Each replicant is defined as indicated in the attached file.

Has anyone ever run into this? Is there a support case that addresses this? I've searched high and low and have found nothing like this so far. Any help that anyone can provide would be most welcome.

Thanks in advance,

Rich

UPDATE 05/12/2008:

It seems that this issue is related to page refreshing and when the TinyMCE configuration is loaded. If I create a new instance, save the DCR and hit 'refresh', ALL instances of TinyMCE are refreshed and made available.

Anyone have any ideas on how to get around this one? Thanks!

Rich

Find more posts tagged with

Comments

Pawan

Rich,

Is the tinymce customised or the default configuration?
Is this behaviour consistent throughout all the datatypes?
Which browser does it affect which it doesn't?

We had a similar issue, and were provided some patches for tinymce by support. In your case, you should contact support as similar behaviour was reported as bug.

rsteeves

Pawan,

- We have customized the TinyMCE toolbar, and thus have a custom configuration
- We are using a single datatype, so yes, it affects all datatypes
- IE and Firefox are both affected

We have a patch that deals with TinyMCE losing its configuration settings when changing pages on the DCT, but that's the only patch that we have installed. I have been less than impressed with Interwoven's response to the problems we've been having with TinyMCE and would prefer not having to deal with them any more on this issue (they are very non-responsive overall).

Thanks,

Rich

Pawan

I felt the same frustration with iwov support on tinymce issues, but as this is a third party tool, so i guess iwov has to get back to moxiecode each time and wait for the response. My case took over three months, hope yours will be resolved earlier than this.

btw, i would like to try with the default config of tinymce and reproduce the same issue, so that you can be sure, its not your customisation that is causing the problem.

Firenze

TinyMCE has display problems when there is not a visible instance (i.e. inside a replicant that is not created or expanded) of tinyMCE first loaded.

We have submitted this to IWOV and bugs have been recorded.

A workaround we have been toying with, so far with success, is to load a tinyMCE textarea at the bottom of the DCT and then hiding it when the form loads.

If your form supports a tinyMCE that makes sense to be visible to the user on Form Load then you don't have to do the hide step.

Gregg Faus

Did these issues get cleared up in latest release of TeamSite (either 6.7.2 SP1 or 6.7.2 Patch #2-7668)? I'm experiencing similar issues where multiple tinyMCE editors will generate javascript errors when using a custom config.

CRB

iwov provided a newer version of tinyMCE with teamsite's latest patch (5)... there is huge list of fixed issue in the release notes and i think this issue is one of them. eitherway, i think upgrading tinymce will resolve a lot of your tinymce issues.

Gregg Faus

Aftering testing on a TeamSite 6.7.2 SP1 server, the javascript errors related to replicants and tabs with TinyMCE were resolved for me.

Garth McMillan

Even though this is an old topic, I thought I'd just throw my two cents in here, as we have the same, or at least similar, issue with our TeamSite 6.7.2 SP2.

In our case, if we specified a TinyMCE configuration (via the @external-editor-config attribute) and the item was not shown when the DCF initially loads (such as in a different tab) then it wouldn't initialize correctly.

I found two options that worked:

1. Don't use a custom configuration. For example:

[PHP][/PHP] 2. Specify a @row attribute of greater than 8. For example: [PHP]<textarea external-editor="tinymce" required="f" external-editor-config="standard" rows="10">[/PHP] I have no idea why 9 and above work and 8 and below don't... Anyway. I hope this helps someone.