problem with 2 config files on 1 DCT

I've seen a few posts on this, but none resolved my issue. I have one DCT that references 2 different config files. The XML in the config files has been validated and the files are where they are expected to be. One config file has almost a full toolbar and the other has just a minimal toolbar. The config files are loaded inline.

Problem - when I move from field to field quickly, eventually I get an error that all XML functionality is disabled [the ewebeditpro+XML license key is missing...]. If I move slowly and let the toolbar build before moving to another field, I don't get this problem. If I move quickly between fields that use the same config file, I also don't get the problem. It is just when switching between fields which use different config files.

I'm not using ewebeditpro+XML, just ewebeditpro.
We're using ewebeditpro 4.2.0.11 and 4.3.0.8
XP servers and XP clients
TeamSite 6.1

I thought I'd try having the textarea that has the minimal toolbar load with the Visual Editor button instead of inline (as an experiment), but that didn't work. The first declaration of the editor seems to determine how all will load.

Is it just too memory intensive to use 2 config files? Is there any workaround?

Find more posts tagged with

Comments

ccprofessional

Just curious-

How is it that you have two different versions of eWebEditPro on one TS 6.1 server?

Are you using the default versions of eWebEditPro?

Chloe

Good question. I have no idea how I ended up with a different version than the others. So far I'm the only one I've found that has the more recent version.

ccprofessional

It's possible you may have some (black?)patch from Interwoven.
It does not sound like a memory issue. Probably some screwed up javascript within ewebeditpro20 directory.
If you have a vanilla install of the same version of TS, you can compare the directories.

Migrateduser

Ran across a similiar problem...

Solution seems to be that all VF fields within a DCT must use the same configuration file or none.
Will this be addressed by Interwoven, or is it just a bug we have to live with?

TS 6.7.1
Win

brvhrt

Ran across a similiar problem...

Solution seems to be that all VF fields within a DCT must use the same configuration file or none.
Will this be addressed by Interwoven, or is it just a bug we have to live with?

TS 6.7.1
Win

my understanding is that before TS 6.x, VF used to be loaded separately to each textarea that uses VF , so if you have a big DCR lets say a DCR which has over 100 replants and each replicant has a textarea that uses VF it takes long time for the dcr to load and it used to cause a performance issue. Now TS is loading the vf once for the dct/dcr and it replicates itself every time you open a textarea with VF in it.

i could be wrong, but this is what i know. and that could be the cause of your problem.

hope to hear from the experts in what they say.

barChart.png