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

Extreme Document Load Time

teal001

Has anyone seen the error Extreme Document Load Time? This happened when one of our users was trying to edit a very large template (the template has about 154 sections with Visual Formatters in it). A coworker of mine googled the error, and found out it was an Ektron error (which I believe is the maker of the Visual Formatter). If you have seen the error, are you aware of a workaround or a suggested number of Visual Formatters per template?

Find more posts tagged with

Comments

nipper

What version of TS ? What OS ?

This was a larger issue in older versions of TS, because it would load all of the VFEs no matter what, now it only loads them as needed.

If you are on a very recent copy of TS and it is still a significant issue, then you can change the VFE config from an inline to a callout, where a user needs to click a button to open the editor. Not nearly as easy for the end user, but may be what you need.

teal001

We are using TS 6.5 SP2 on a Solaris Platform.

nipper

Do all 154 VFE windows load at once, or does each load as you click on it ?

teal001

Each loads as you click on them.

nipper

I thought that was the case, then I do not know if VFE is the problem. Do you have a custom config for the VFE ? It may be trying to load 154 of those.

Can you do some testing ? You should have a bunch of these in you DCT:

external-editor="visualformat" external-editor-config="" external-editor-inline="t"

or something like that.

Do a global search/replace for "visualformat" to ""

then see if the load time is better, make certain that your previous DCR is submitted and the new one is not so you can easily revert

DougD

This Ektron knowledge base article may help "The Document Is Not Ready" http://dev.ektron.com/kb_article.aspx?id=752

teal001

Thank you Doug for that link. I can see how that may be a problem as each of these Visual Formatters has a link in it.

Nipper - our DCT has one iteration for the VF, and the users have created 154 sections with it. ;-) Currently, they will max out at 200. So, if I change the one interation to take out the "visualformatter" (because it is in there), obviously that will affect all of them, but what will happen? If it doesn't make a call for the visualformatter, will it load it anyways?

Thanks for the help.

nipper

So, if I change the one interation to take out the "visualformatter" (because it is in there), obviously that will affect all of them, but what will happen? If it doesn't make a call for the visualformatter, will it load it anyways?

Thanks for the help.

That will not load any VFE. This will show if the DCR is just too big, or it is VFE loading (like you think). Another possibility is that you have some FormAPI running over all 154 replicants at startup.

This will help you narrow down where the problem is. If you see significant improvement then check Doug's link.