Visible VARs during checkout phase. [Archive]

View Full Version : Visible VARs during checkout phase.

lee.harris

24-Mar-2003, 01:14 PM

Hmmmm. During the checkout phase at our store, I see this:

SEPARATESHIPYes

as well as a similar entry for (IIRC) INVOICECOUNTRY.

I've checkted the Orderxx templates and can't see why these are turning up. Can anyone help me see the wood for the trees.

Thanks

Lee.

murf

24-Mar-2003, 07:52 PM

We cant get rid of:

NETQUOTEVAR:SHIPANDHANDLEINFO

Darren

25-Mar-2003, 04:14 PM

Sorry to hear about the problems you are having.

To get rid of 'INVOICECOUNTRY' and 'SEPARATESHIP' in the Invoice Address page, go to the 'Design | Text' menu and click on the 'Go To' button and enter Phase -1 and ID 2067 to see the prompt:

<TABLE WIDTH="100%" BORDER="0" CELLSPACING="0" CELLPADDING="0">
<TR>
<TD ALIGN=LEFT>%s%s%s<INPUT TYPE="HIDDEN" NAME="%s" VALUE="%s"></TD>
<TD ALIGN="RIGHT"><INPUT TYPE=SUBMIT NAME="ACTION" VALUE="Change"></TD>
</TR>
</TABLE>

Change:

<TABLE WIDTH="100%"

to:

<TABLE WIDTH="100&#37;"

(&#37; is the html for %).

Hope this helps.

BPJSURF

24-Apr-2003, 06:51 PM

this has been a bug in version 5 and six since release 5.x and 6.02. Has this issue been resolved with the new releases?
I have several customers upgrading from 5.01 and 6.02 with complete builds of 5.1.6 and 6.1.2 respectively and this issue continues to be an issue for the cleint.

Is the problem atht the issue has not been fixed in the build or is the problem that the upgrader does not upgrade that code and therefore the bug is passed to the next version.

I would like to know how this issue has seemed to pass from version to version.

I am sooooo confused with this one.

Brian:(

cdicken

25-Apr-2003, 02:11 PM

I have raised a bug for this to be added to the upgrade information. It should not happen in future versions.

jarroyo

20-Sep-2003, 12:19 AM

I had it working before changing to $%#37 in the code! Now I can't get it back to where I can take orders! I am losing customers! ARRRRRRRRRGGGGGGGGGGG!

NormanRouxel

20-Sep-2003, 08:10 AM

I had it working before changing to $%#37 in the code!

That may be because it should be &#37; as correctly mentioned above. You can always change it back and see if thet restores things.

Norman

jarroyo

20-Sep-2003, 12:46 PM

:o

Must have been late. I copied the code on my message from memory. Customers don't come in droves to a site unless you are having problems.