Coding errors

[leehack]

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

I approach it differently, i copy the existing layout, so i have a bckup and then revert it to see if that solves things. If it doesn't, copy paste the layout back in from the copy you made and in 90 seconds you have reduced one of the possibiilites from the equation in a very short time.

[jont]

I must be on my different version again

As daft as that sounds that would appear to be the case at times with issues not transferring between different installations

[jont]

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

The coding errors re very erratic ... I have one which tests a simple variable specified against each section eg: isVariable == 1

9/10 sections are fine but one reports an error ... delete the condition and enter it back, exactly the same and it disappears for a few reboots whereupon it returns again.

[stonda]

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.

If I revert to the standard layout, it will be a nightmare to get what I have now as there are alot modification. During the week end it worked. So it is a recent modification which give the error.
Now why Actinic gives an error line, if this information is not usefull ?

[Duncan Rounding]

If I revert to the standard layout, it will be a nightmare to get what I have now as there are alot modification. ...

You could copy the layout first, save it as another name and then revert the standard layout back to default. Then gradually add bits in from the saved layout.
Actinic's code checking is not too good sometimes.

[stonda]

I found the 2 errors.
Cut 1 table, check, always error, paste it, cut another one ... to see that the errors was in the Delivery table.
Cut the delivery table, and add block after block to identify error on block 5 and 8. Just to check the code : it was my mistake : onblur="format(this,'capitals')/" instead of onblur="format(this,'capitals')"/
Thanks
But possibility to add into the whishlist a better help into Actinic to find the error : would it be possible to have the exact line on which the error is ?

[pinbrook]

Ok update, my error are being caused we think by GA code (doh!) revert to factory for cart/checkout pages would have been a pointless exercise as the fault is actually in the overall layout. - well actually its the 2nd overall layout i use for checkout pages only. (the body tag doesn't have the GA code in it)

But does anyone every use the check for coding errors option on the Design menu, as when i do this it halts and never completes. It hangs on checking actinic.css - which is logical cos I don't have one, i use my own external style sheet - therefore my question is what is the "check coding errors" looking at that tells it to try to check actinic.css and how do i tell it to bypass. The theory is using this method of check coding errors might bring up a more meaningful error message/line number

[TraceyHand]

But does anyone every use the check for coding errors option on the Design menu..... The theory is using this method of check coding errors might bring up a more meaningful error message/line number

I have done...quite often
It gives exactly the same format/results as when the check is run on upload though.

[stonda]

I have re introduce an error on the checkout page, run check coding errors. No error found !

[TraceyHand]

yes...I had that earlier!
Upload gave me a coding error but I uploaded anyway.
Went to "fix" it...ran the design>check coding errors...no errors found!

Subsequent uploads didn't pick it up either.
Took a snapshot..transferred it to new machine and imported it.

Uploaded website again..."1 coding error"

fickle things, I'm thinking!

[pinbrook]

All the coding errors I had did not cause the upload to fail nor did they stop the checkout from working, I think more attention needs to be paid by Actinic to it to make it a viable feature - it is indeed fickle right now - it was suggested to me by support to use it from the design menu rather than the red exclamation mark as each method can produce conflicting results. Sadly I can not run it from design menu as it freezes on actinic.css.

Lee has already stated that some errors will simply go away if you click on them and return and few times.