Coding errors

[stonda]

Hi. After some modifications, in checkout page 1, I have a red exclamation point. Clicking on it, I have 2 syntax error, line 450 and 474.
How can I find the errors ?

[jont]

Click on the error and it should take you to the offending code in the design tab mode.

[pinbrook]

I have exactly the same problem, you beat me to posting.... its in all my checkout pages

The line number does not relate to a line number in a layout...

[jont]

I think the line numbers relate to the overall page (made up from all the layouts) .. although could be wrong as usual

[stonda]

In the Order 01 Bulk Area layout I have 423 lines. So cannot find the code. A double click on the error don't take me to the error. So ?

[stonda]

Any Idea ???
I have the syntax error in the offline preview, and also in the site http://www.supreme.fr/cgi-bin/os000001.pl, with a information for the line. But impossible to find where the problem is ?

[pinbrook]

I think the line numbers relate to the overall page (made up from all the layouts) .. although could be wrong as usual

thats what i assumed too, but it doesn't help in finding the actual offending code...

It hasn't caused me any productivity errors yet so i haven't allocated any serious time to debugging...maybe tomorrow

[stonda]

I think the line numbers relate to the overall page (made up from all the layouts) .. although could be wrong as usual

Yes it probably does, but on the specified line, I do not have any error. Now there is so much blank line in the overall page !

[pinbrook]

maybe I'll phone support tomorrow, and ask them

I'll report back on progress

[stonda]

I sent an email to the support this evening : I will keep you inform (but probably phone will be quicker !)

[leehack]

Isn't reverting to factory settings the quickest repair? You have coding errors after making some amendments - come on Sherlock, there's a big red arrow pointing at the problem.

Revert the layout and start again, just reapply a bit gentler and check along the way more.

[pinbrook]

Not necessarily as the red exclamation mark appears on all checkout layouts including those not changed. and there is no coding error as such, just what actinic perceives as a coding error....the wonderful world of actinic

[leehack]

I must be on my different version again then, i've never once seen a coding error on a standard or even a modified checkout page.

Although not certain of course, Didier quotes that he amended things and then these errors cropped up. Given that he is fumbling round a bit at the moment and finding his feet, i know what would be my first port of call to check.

Only time i ever see the coding error is for a genuine one or when actinic seems to struggle on a large change. It loves the "used out of context" error - must have been the buzz word that week when it was built. However, flick to content tab and flick back and it disappears 9/10 times.

I think Designer (the product) is the problem personally, MS seems less problematic.

[pinbrook]

I may still return to eat my hat....

but the pesky checkout works on the live site

in the meanwhile i'm off to bed

[pinbrook]

The error I get is "script error at line 260: Object expected"

I've compared layouts to factory defaults, although nothing is actually telling me which layout seemingly has the error, but script error makes me think its not actually any bodge i've done to the code ie HTML

The most useful thing to know is how to find line 260.

Also when comaring factory layouts there are 3

I presume?

current library is my amended one
current factory is the one it would revert to

so what is the function of previous factory layout?

I must be on my different version again then, i've never once seen a coding error on a standard or even a modified checkout page.

Although not certain of course, Didier quotes that he amended things and then these errors cropped up. Given that he is fumbling round a bit at the moment and finding his feet, i know what would be my first port of call to check.

Only time i ever see the coding error is for a genuine one or when actinic seems to struggle on a large change. It loves the "used out of context" error - must have been the buzz word that week when it was built. However, flick to content tab and flick back and it disappears 9/10 times.

I think Designer (the product) is the problem personally, MS seems less problematic.

I understand what you are saying Lee, but to me the most useful thing here is to determine how to find the line that the coding error refers to, Didier and I have different problems with checkout code, but we have the commonality that Actinic is not being useful and actually telling us where the errors are, it points to line numbers that cannot be traced to layouts.

I'm not going to revert to factory until i know what line is being objected to