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

blank DCR

boskovuk

This happens on our DEV server (started Wednesday last week).

As the DCR loads, the form is empty (see pic2.JPG file).

We looked at various things trying to understand what triggered this condition. No success yet.

As we were troubleshooting we noticed that a new Event started to happen (last Wednesday as well), which could be potentially responsible for the issue (see iwproxy-error.jpg).

Would anyone have any suggestions regarding the problem?

TIA

Find more posts tagged with

Comments

nipper

OK, just ot be certain, have is the DCR still good ? I assume the data in them have not changed. Has templating.cfg changed or the DCT ?

Is this all DCRs or one type or one ? What happens if you create a new one ? Can you view it after the fact ? The proxy errors are a concern but *should* not cause this. You need to figure out what is causing that.

theme_bug.zip

CRB

As the DCR loads, the form is empty (see pic1.JPG file).

i dont think your pic1.JPG is showing what you are talking about...

boskovuk

i dont think your pic1.JPG is showing what you are talking about...

Fixed (it should have been pic2.JPG). Thanks Smiley Happy

CRB

ok it looks like your DCR is not loading, does your browser indicate any javascript error? you might want to enbale script debugging on IE and try to open ur DCR. does ur iwui\serveltd_out.log show any errors?

boskovuk

OK, just ot be certain, have is the DCR still good ? I assume the data in them have not changed. Has templating.cfg changed or the DCT ?

Is this all DCRs or one type or one ? What happens if you create a new one ? Can you view it after the fact ? The proxy errors are a concern but *should* not cause this. You need to figure out what is causing that.

DCRs are good (all of them are affected - this is not one DCR only problem).

We are able to create and save new DCRs as well. New ones are failing the same way as the existing DCRs.

use case 1:
when we view/open generated pages within htdocs folder, the iwproxy.exe crashes and the generated page never gets loaded

use case 2:
Open (View or Edit) DCR opens up, however, the DCR window is empty (see attached image).

nipper

OK, all DCRs of all types ?

All users ? Browsers ?

restart iwproxy from the shell and put it in debug mode, see if you can figure out why it is crashing

Adam Stoller

This kind of thing happens most often when the DCT is written in one style ("iwov" or "xml") and declared in templating.cfg as the other style ("xml" or "iwov") - or when the DCT style is inconsistent between the two styles.

Can you post the DCT and the relevant line from the templating.cfg file for it?

nipper

This kind of thing happens most often when the DCT is written in one style ("iwov" or "xml") and declared in templating.cfg as the other style ("xml" or "iwov") - or when the DCT style is inconsistent between the two styles.

Can you post the DCT and the relevant line from the templating.cfg file for it?

If he really creates a new one, saves it and then opens and gets the same result I am not so sure.

I did ask in an earlier post if templating.cfg changed however.

Adam Stoller

If he really creates a new one, saves it and then opens and gets the same result I am not so sure.

That sounds very much like mixed-up DCT coding and/or conflicting specification in the templating.cfg

I did ask in an earlier post if templating.cfg changed however.

I know, however sometimes there's someone else making changes to files that don't get communicated to everyone who should know about it. (Or sometimes people do things without thinking / realizing)