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

Performance Issue | Multiple tinymce containers in DCR

anud

I am using tinymce in replicatable container in DCT. I have created DCR which contains 293 containers. I am facing performance issue while editing DCR. I am neither able to add new container nor modify existing container in DCR.

Find more posts tagged with

Comments

Adam Stoller

I am using tinymce in replicatable container in DCT. I have created DCR which contains 293 containers. I am facing performance issue while editing DCR. I am neither able to add new container nor modify existing container in DCR.

Having that many replicant instances within a single DCR is a questionable design regardless of whether TinyMCE is involved.

What version of TeamSite are you using?
Do you have the containers start up expanded or collapsed? If not collapsed by default, you should try making that change and see if it helps resolve your issue.

anud

TeamSite: 7.2.1
By default, all the containers are in collapsed state.

Adam Stoller

TeamSite: 7.2.1
By default, all the containers are in collapsed state.

Well, that's about as new a version and as efficient a state as one could have it.
While you should open a case with Support to see if they can reproduce your issue in-house (and thus be able to file it with engineering) - you'll probably need to explain to them (and it would be nice if you explained to us) why you need a DCR with so many replicant instances.

If this is a stress-test - you've obviously stressed it.
If this is for a real purpose - understanding that purpose may lead to alternative mechanisms for satisfying it that might be more efficient / less troublesome.

ShashankJain

After opening the dcr click on expand all then on collapse all, this will load the dcr in one go.To verify this popup an alert as the first line.

Yes this is questionable why you have 293 containers in one DCT,you should be calling inline command and place your containers in IPL's.This will surely increase performance.

Adam Stoller

Yes this is questionable why you have 293 containers in one DCT,you should be calling inline command and place your containers in IPL's.This will surely increase performance.

I'm not sure I follow your logic here.
Are you suggesting that they call 293 inline scripts to improve performance?

My assumption is that there is a replicant instance with a TinyMCE text area in it and that the replicant either has a huge or even unbounded 'max' attribute such that they are able to create 200+ instances of the same container element, each with a TinyMCE text area - putting an inline script here to create the container or TinyMCE text area would have little to no effect and perhaps even an adverse / harmful effect on performance.

Putting an upward bound on the replicant's 'max' attribute, if reasonable (like 25 or 50) would probably have a positive effect on performance - but that's only reasonable if the usage of the replicant is okay being limited to 25 or 50 instances. If there's really a "need" for 200+ instances of the replicant then placing a lower restriction on the instances may help performance but fall drastically short of usage needs.

Hence, I'd like to understand if this is an actual requirement (and if so, based on what) or if this is part of a stress test (in which case it succeeded).

You might be able to replace the TinyMCE text area with a callout script the brings up a separate window with a TinyMCE text area embedded within it and which then stores the resultant content in a hidden field within the DCT/DCR -- it's a bit more cumbersome in terms of usage but likely to perform better with 200+ instances because they wouldn't be running concurrently. I still wouldn't want to navigate through 200+ instances of a replicant in a DCR, but then again, I'm not the customer here...

anud

This is not the stress testing. It is an actual requirement where we have to store term and its definition in one DCR. There are 295 such terms.

Secondly, I am using replicant container which has one text field for term and tinymce to store definition.

When I encountered this problem, I thought of using inline CGI call to display tinymce in pop up. But I am not sure how to go about this.

Thanks,
Suruchi

Crsb

Are you loading OOTB tinymce or do you have some kind of custom version of tinymce that you are loading?
it might not work, but you can try to strip down tinymce to just the plugins and formats you need and see if that will help.