Announcement

**wjcampbe** · 14-Jul-2005, 12:38 AM

</table> followed by </td> is valid if the full code is
<td>
<table>
</table>
</td>

in other words a table fully nested in a cell of another table.

Actinic have apparently built their code with some of it in templates that we can add to, and some of it hard coded into the program to prevent reverse engineering. Once we start taking the templates apart, we are left with the hard coded bits to resolve and that will keep tripping you up.

Each template is expected to follow/be wrapped within/be followed by another template. Code id often split between different templates which the program combines into one page.

The opening tag for the table cell that is closed in your 17th line is obviously meant to be somewhere back inside another table back in the original act_primary which you are not using.......

**magicalwonders** · 14-Jul-2005, 09:42 AM

Hi Bill,

I understand what you say. I've had a look at the original act_primary and the code that is generated from it and still can't see where this extra </td> has come from.

Here is a URL showing original code, with nothing added or taken away.
http://www.magicalwonders.com/acatalog/index.html

You'll notice that the code is not compacted and is displaying the extra tag as before.

<Actinic:TEMPLATE type="end" filename="C:\Program Files\Actinic v7\Sites\Site1\Act_SectionLineSmallText.html"/><Actinic:TEMPLATE type="begin" filename="C:\Program Files\Actinic v7\Sites\Site1\Act_SectionLineSmallText.html"/>



<A HREF="More_Products.html"><span class="actxsmall">More Stuff</span></A>
</TD>
</TR></TABLE>
</td>

It's obviously come from somewhere?

Myles

**wjcampbe** · 14-Jul-2005, 12:39 PM

When I post your code into an HTML editor, I see the opening <taqble tag in line 216 of the source code, the opening <td tag in line 216 and the closing tag - the one you are worrying about - down in line 240. Everything in between is the Navigation Menu along the top of the site page.

Line 241 opens another cell in the original table - a couple more tables are opened and closed in this cell, then a third cell opens before the whole original table is finally closed in line 382 of the expanded code. Right at the bottom of the page.

Try this yourself using a good clean html editor (such as 1st Page 2000) and add comments above each table and cell opening/closing tag to track (eg ,  etc).

Sorry but there is no extra tag - just a fair bit of separation between the beginning and end of the table.

**magicalwonders** · 14-Jul-2005, 04:13 PM

Thanks Bill,

I just couldn't see where this </td> was coming from. As it happens, W3C didn't complain about this tag, but when I saw it, it just looked wrong.

Thanks for the tips.

Myles

**magicalwonders** · 14-Jul-2005, 07:28 PM

O.K. At the risk of ending up in the funny farm, I've turned my attentions to sorting out this matter of <forms>.

I've re-instated the original code in the Act_CatalogBody and uploaded the page.

I've had a look at the code this produces and have noticed that whilst the results are O.K. for the products page, it produces errors for the index page.

http://www.magicalwonders.com/acatalog/index.html

On this page the first form starts with a closing tag </form> and the second form ends with no tag. It's occured to me that as different templates and layouts can be specified for different sections of the store, would it be possible to contruct a template for the index page that validates the tags and then revert to the original template for the rest of the store? Sounds like this should be possible?

I've read and re-read the advice Chris gave a million times (O.K. at least 20 times!) but I don't understand how this works.

My current Act_primary has the <FormBegin> and <Formend> with the TD tags, as follows:

<TD align="center" width=550>
NETQUOTEVAR:FORMBEGIN
<A name=top><INPUT type=hidden value=NETQUOTEVAR:RANDOM name=RANDOM></A>
NETQUOTEVAR:HIDDENFIELDS
NETQUOTEVAR:BULK
NETQUOTEVAR:FORMEND</TD>

Am I able to edit this so that the forms on this page validate?

Any ideas on this?

Myles

**wjcampbe** · 14-Jul-2005, 08:37 PM

Myles,

if you can load the uncompacted code, it's a lot easier to look at. It will also show which of the stitched together templates, the code that is bothering you is really in.

From reading the advanced guide, Act_Catalogbody opens with a </form> in order to close the <FORM tag opened with NQV:FORMBEGIN and then opens a continuation <form tag which is closed by NQV:FORMEND.

From this, the place to look for the opening form tag is just before the top anchor - have you altered the code in ID=2279?

**magicalwonders** · 14-Jul-2005, 09:47 PM

Hello Bill,

Sorry. I had uncompacted locally, but forgot to upload. The site's been uploaded so many times over the last couple of days, I think I deserve a certificate from Actinic!

Anyway, it just seems to be the index page which is throwing a spanner in the works as far as the <form> tags go.

http://www.magicalwonders.com/acatalog/index.html

Is producing this code:

</FORM>
<FORM METHOD="POST" ACTION="http://www.magicalwonders.com/cgi-bin/ss000001.pl">
<INPUT TYPE=HIDDEN NAME="SHOP" VALUE="">

</FORM>
<FORM METHOD=POST ACTION="http://www.magicalwonders.com/cgi-bin/ca000001.pl">
<INPUT TYPE=HIDDEN NAME="SHOP" VALUE="">

Which appears to be as a result of the code in Act_CatalogBody.

However, when looking at products in section pages such as this:

http://www.magicalwonders.com/acatal..._Products.html

The form tags are correct, with each opening tag <form> having a closing tag </form>

I now appreciate the reason why the first tag in Act_CatalogBody is a closing tag. It's obviously working as intended in Section pages, but it doesn't appear to do the job quite right when imported into the index page. That is why I was wondering if it's possible to rig a one off Act_primary for the index page that forces the form tags to work?

Myles

**wjcampbe** · 14-Jul-2005, 11:00 PM

You can specify different overall layout (primary) templates - so that is a yes. Problem is what to put in the added <form> tag and where to add it.

Have just looked up <form> in the html reference that comes with the html editor I use. Form tag MUST have an action attribute - what action to assign? Needs more study...

**magicalwonders** · 15-Jul-2005, 11:12 AM

Hi Bill, Everybody,

I've been experimenting!

Have created a separate Act-Primary for the index page. Or rather the other way around. A separate layout for all the other pages - as you don't seem to be able to specify a template for the index page.

I tried commenting out the NQV:Bulk first of all. Everything worked fine except for the link to "Term of Business" This reduced the errors on page to three. The shopping cart worked as it should and no problems other than this one link not working.

I then re-instated the NQV:Bulk and commented the first <FormBegin> above the bulk area. Again everything works fine, including all the links and shopping cart. Form error eliminated. Total errors reduced to seven.

The first option obviously produces the best results. But I can't figure out why the TOB link doesn't work without the NQV:Bulk whilst everything else does.

Any ideas?

**magicalwonders** · 15-Jul-2005, 12:04 PM

I then re-instated the NQV:Bulk and commented the first <FormBegin> above the bulk area. Again everything works fine, including all the links and shopping cart. Form error eliminated. Total errors reduced to seven.

Ooops, Sorry. A bit of mis-information here. Just spotted that the code in Act_catalogBody was edited. The original code still produces the form error.

The first results hold true though. So If I can sort out a working link for TOB, I'm back on track!

Myles

**magicalwonders** · 08-Aug-2005, 07:28 PM

Hello Folks,

A bit of progress to report in my quest for validating code.

My index page http://www.magicalwonders.com/acatalog/index.html is now fully compliant and passes validation. Hoorah! I had to cheat a little bit to get there but what the heck, nothing seems to be broke!

The product pages are a slightly different story. Have got shot of all <tag> errors and am down to 11 errors with one product on page. These errors will of course increase as more products are added.

Just a couple of questions: I've commented ACTINIC:BASEHREF VALUE="NETQUOTEVAR:BASEHREF" and replaced with <base href="http://www.magicalwonders.com/acatalog/"> Everything seems to work O.K. Just wondering if there are any dire consequences awaiting to befall me for taking this action? Am I destined to sit on the Actinic naughty step?

Secondly: The errors I'm left with are the following.

Error Line 3 column 232: element "ACTINIC:COOKIECHECK" undefined.
...as.js"></SCRIPT><ACTINIC:COOKIECHECK /></HEAD><BODY onload=PreloadImages('top

Error Line 3 column 267: an attribute value must be a literal unless it contains only name characters.
...K /></HEAD><BODY onload=PreloadImages('top2.gif','back2.gif','sections2.gif',

Error Line 12 column 759: element "ACTINIC:CARTERROR_LIST" undefined.
...</B></SPAN> <Actinic:CartError_List/></A> <BR></DIV><TABLE WIDTH="550" BO

Error Line 12 column 896: there is no attribute "BLOB".
...><td colspan=3 <Actinic:SECTION BLOB="A0001.cat"/> <FORM METHOD=POST ACTION="

Error Line 12 column 907: element "ACTINIC:SECTION" undefined.
...n=3 <Actinic:SECTION BLOB="A0001.cat"/> <FORM METHOD=POST ACTION="http://www.

Error Line 14 column 644: there is no attribute "PRODREF".
..."middle" ><Actinic:CartError ProdRef="123"/> <!-- <SPAN CLASS="actrequiredcol

Error Line 14 column 649: element "ACTINIC:CARTERROR" undefined.
...le" ><Actinic:CartError ProdRef="123"/> <!-- <SPAN CLASS="actrequiredcolor"><

Error Line 14 column 829: there is no attribute "PROD_REF".
...n="middle" ><Actinic:PRICES PROD_REF="123" RETAIL_PRICE_PROMPT=""><span class

Error Line 14 column 855: there is no attribute "RETAIL_PRICE_PROMPT".
...S PROD_REF="123" RETAIL_PRICE_PROMPT=""><span class="actxsmall"><b>  &n

Error Line 14 column 857: element "ACTINIC:PRICES" undefined.
...PROD_REF="123" RETAIL_PRICE_PROMPT=""><span class="actxsmall"><b>  &nbs

Error Line 14 column 1015: element "ACTINIC:ACTIONS" undefined.
...><TD align="center" ><ACTINIC:ACTIONS><P><INPUT TYPE=SUBMIT VALUE="Buy" NAME=

I know I'm stuck with probably most if not all of these. However, just on the off chance, is there any of them I might be able to fix?

Many thanks,

Myles

**TraceyG** · 10-Aug-2005, 09:40 AM

Hi,

Your posting shows some commenting, are you compacting your html (Design | Options | Miscellaneous | Compact CGI/HTML)?

**magicalwonders** · 10-Aug-2005, 12:27 PM

Hi Tracey,

At the moment I have commented

<base href="http://www.magicalwonders.com/acatalog/"> in my act_primary

As I noticed that it affects preview of site (No pics) when viewed locally.

What are you referring to as commented?

Yes, the site is compacted at the moment.

Are any of the errors I've listed fixable?

Many thanks,

Myles

**TraceyG** · 10-Aug-2005, 01:40 PM

Hi,

<!-- <SPAN CLASS="actrequiredcolor

The <!-- is the start of a comment. If you are compacting the html these should not show in the source of the page.

Are any of the errors I've listed fixable?

To be honest, I don't think so, although I'm not sure what the 2nd one that you list means - I can only guess that it doesn't like the number in your image names. All the others refer to actinic variables that are required

**magicalwonders** · 10-Aug-2005, 02:05 PM

Hi Tracey,

Re:

<!-- <SPAN CLASS="actrequiredcolor

What Url are you seeing this in? I've checked the source code of every page and searched for

<!-- <SPAN CLASS=

The results come back "Not found"

I can only guess that it doesn't like the number in your image names. All the others refer to actinic variables that are required

This error is a result of "onload=NETQUOTEVAR: ONLOAD" In the head area of Act_Primary. I'm told it is required if using PSP, although I'm not sure how that works as it seems to be just a bunch of gifs.

Thanks

Myles

Announcement

Starting Again!

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment