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; } } }

FormAPI setValue() causing TinyMCE to throw Javascript errors

Jamik

We're looking at upgrading to 6.7.2 sp2 (we've installed it on our dev box) and also would like to switch wysiwyg editors to TinyMCE. However, we've ran in to an issue with TinyMCE that evidently exists for us in our 6.7.1 sp1 server as well.

I've already talked with Autonomy Interwoven support about this issue and they've labeled it as a bug but I can't believe we're the only ones who've experienced this issue with TinyMCE. I've created a simplified template to demonstrate the issue and I'm curious if anyone else has run into this issue or if our template and/or FormAPI code is configured wrong for TinyMCE.

The scenario is we have a template that is configured to be multiple pages. On one page we have a field that uses TinyMCE. Then in our FormAPI code we try to setValue on that TinyMCE field on an onSaveValid event. If the user tries to save the template on a page that does not contain the TinyMCE field they get one of two javascript errors (i included them as attachments runtimeerror.gif and runtimeerror2.gif). However, if we change the editor back to Ektron's VFE we don't get these errors. Also if we try saving while on the page that does contain the TinyMCE field we do not get the errors and it saves fine. I've included the datacapture for the template which also contains the FormAPI code.

We're using the older datacapture5.0 dtd, iwov formatting for the dcr, and pagination so it might just be the case that this is a real bug with TinyMCE where Autonomy Interwoven didn't test out TinyMCE with templates using pagination and FormAPI targetting the TinyMCE fields. This isn't going to prevent us from upgrading but we'd like to switch to TinyMCE because we feel it's a lot better than Ektron's wysiwyg.

Any help on this one is appreciated.

Find more posts tagged with

Comments

rajivgupta

Hi Jamik ,

We have also faced similar issue but did not reported it to IWOV thinking it as some coding related issue .

Did IWOV provided any black patch for this ??

We're looking at upgrading to 6.7.2 sp2 (we've installed it on our dev box) and also would like to switch wysiwyg editors to TinyMCE. However, we've ran in to an issue with TinyMCE that evidently exists for us in our 6.7.1 sp1 server as well.

I've already talked with Autonomy Interwoven support about this issue and they've labeled it as a bug but I can't believe we're the only ones who've experienced this issue with TinyMCE. I've created a simplified template to demonstrate the issue and I'm curious if anyone else has run into this issue or if our template and/or FormAPI code is configured wrong for TinyMCE.

The scenario is we have a template that is configured to be multiple pages. On one page we have a field that uses TinyMCE. Then in our FormAPI code we try to setValue on that TinyMCE field on an onSaveValid event. If the user tries to save the template on a page that does not contain the TinyMCE field they get one of two javascript errors (i included them as attachments runtimeerror.gif and runtimeerror2.gif). However, if we change the editor back to Ektron's VFE we don't get these errors. Also if we try saving while on the page that does contain the TinyMCE field we do not get the errors and it saves fine. I've included the datacapture for the template which also contains the FormAPI code.

We're using the older datacapture5.0 dtd, iwov formatting for the dcr, and pagination so it might just be the case that this is a real bug with TinyMCE where Autonomy Interwoven didn't test out TinyMCE with templates using pagination and FormAPI targetting the TinyMCE fields. This isn't going to prevent us from upgrading but we'd like to switch to TinyMCE because we feel it's a lot better than Ektron's wysiwyg.

Any help on this one is appreciated.

Synthese_commune.rptdesign

CRB

test the attached datacapture.cfg and didnt get any errors ( ts 671 sp1 patch 6 redhat AS 4)

Jamik

Hi Jamik ,

We have also faced similar issue but did not reported it to IWOV thinking it as some coding related issue .

Did IWOV provided any black patch for this ??

No black patch and this is still an issue for us. IWOV labeled it as a bug I believe, but don't have the bug number handy.

Jamik

test the attached datacapture.cfg and didnt get any errors ( ts 671 sp1 patch 6 redhat AS 4)

yeah the IWOV support folks didn't get the error at first either, but after a few phone conversations they were able to replicate the problem. I forgot to mention this was on a Windows 2003 server, sorry about that.

In your template.cfg, is it configured similar to this:

[html]

[/html]

I think if you're set up with template.cfg like that it should give you the error (make sure you're not on the same page that actually contains the TinyMCE when saving). If it works for you still no biggie as I'm just curious if anyone else has ran into this issue and/or found a fix for it that support doesn't know about yet.

From what I've seen I think it's because we have this set " items-per-page='1'" and the javascript FormAPI code doesn't properly handle pages with TinyMCE when trying to setValue() on those fields. We don't want everything on one page so changing that isn't an option and switching to xml format (for using tabs provided that will work) would be quite the undertaking just to change wysiwygs.