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

Error: well-formed character data or markup

febysm

A problem was encountered trying to parse the datacapture.cfg file for type //ABC/default/main/WORKAREA/SM/templatedata/project/news/datacapture.cfg. Please contact your system administrator.

Root cause:
Couldn't parse DCT bytes into DOM [datacapture.dct_parse.error.msg ]:The content of elements must consist of well-formed character data or markup.

I am getting above error when enter for loop in formAPI.
Without loop its working fine.
Any configuration issue is there?

Find more posts tagged with

Comments

nipper

Is this an include or directly in the DCT ? The error implies it is directly in the DCT.

ISCBorisB

Any configuration issue is there?

Yes. Your problem is < symbol in the "for (var i=0; i<=itemChild.length; i++)...".
That makes your DCT XML malformed. So:

<script><![CDATA[
Your FormAPI Code
]]></script>

Better yet, abstract FormAPI into JS Library

febysm

Thanks Andy and Boris
<![CDATA[ worked Smiley Happy

nipper

FYI, you should take the JS out of the DCT and put it into a library as Bo mention.

Something like:

[html]
<script language="javascript" location="webserver" src="/iw/FormApi/Page.js"/>
[/html]

And your JS goes into $iwhome/httpd/iw/FormApi/Page.js

You can also play with the location parameters. This works for me since I have everything on my config branch so I change the JS in teamsite and use my WF to push it to iwhome

Andy

gzevin

And your JS goes into $iwhome/httpd/iw/FormApi/Page.js

not necessarily. as you mentioned, the location attribute will set where it is located. Some people prefer to keep JS parallel to DCT in the content store. I don't Smiley Happy

Adam Stoller

not necessarily. as you mentioned, the location attribute will set where it is located. Some people prefer to keep JS parallel to DCT in the content store. I don't

I usually keep it right next to the DCT - and call it simply "local.js".
If I have need for more re-usable FormAPI code - then I tend to put it where Nipper suggested and usually call it simply "global.js" - I've yet to have need for more than those two files - but then again, most of my FormAPI coding has been relatively simplistic in nature.

There was a presentation a couple (few?) years ago at GearUp by John and Jon that covered a more elaborate structure of FormAPI code along with information about being able to handle multiple callServer requests and such ... I'm not sure if that's still available on-line though (didn't look)

gzevin

I usually keep it right next to the DCT - and call it simply "local.js".
If I have need for more re-usable FormAPI code - then I tend to put it where Nipper suggested and usually call it simply "global.js" - I've yet to have need for more than those two files - but then again, most of my FormAPI coding has been relatively simplistic in nature.

There was a presentation a couple (few?) years ago at GearUp by John and Jon that covered a more elaborate structure of FormAPI code along with information about being able to handle multiple callServer requests and such ... I'm not sure if that's still available on-line though (didn't look)

It all depends. At the project I am finishing now, I keep all central, including DCTs and TPLs. FormAPI lives in where Andy has mentioned. But yes, I saw both usages. depends on the need. as usual Smiley Happy

with that preso, I think I might have saved it.

nipper

There was a presentation a couple (few?) years ago at GearUp by John and Jon that covered a more elaborate structure of FormAPI code along with information about being able to handle multiple callServer requests and such ... I'm not sure if that's still available on-line though (didn't look)

I think you mean Jeff and Jon (Bonafaci and Gulbrandsen). It was 1 1/2 years ago. Good preso, lousy speakers but a good preso. Smiley Very Happy

nipper

not necessarily. as you mentioned, the location attribute will set where it is located. Some people prefer to keep JS parallel to DCT in the content store. I don't

If you and I agree, we must be right.

Even if I do not need to make reusable code I do this anyway. I tend to keep the same structure from one implementation to another, it makes the startup much easier. There is also always a need for a utility.js, to do some very common functions. That is something I tend to write pretty quickly.

gzevin

If you and I agree, we must be right.

Even if I do not need to make reusable code I do this anyway. I tend to keep the same structure from one implementation to another, it makes the startup much easier. There is also always a need for a utility.js, to do some very common functions. That is something I tend to write pretty quickly.

true. but these days I somtimes I come into an existing shop, where the things are done they way they done....

Adam Stoller

I think you mean Jeff and Jon (Bonafaci and Gulbrandsen). It was 1 1/2 years ago. Good preso, lousy speakers but a good preso.

Oops - my bad - yes Jeff and Jon (I was being so careful to leave out the 'h' in the latter than I goofed on the former ;-)