but I did it using jquery,

function hide_select(id) {
if($('#'+d+'').is(':visible')) {
$('#'+d+'').css("visibility", "hidden");
} else {
$('#'+d+'').css("visibility", "visible");

}

Thanks!

Cheers!

On some sites, I have added an account login form directly on the OCST page. On the left are the login fields, and on the right is a message to new customers that they’ll be given the option to create an account after checkout. So far it seems to work well with little customer confusion.

You will find the category tree template if you click on your store name, and then on your Category Tree Template tab on the right hand side of the screen. You will need to be certain that you are in Template mode to add the code. A little tip: there is a bug in Miva that causes problems if you have any errors in your template code when you first set it up. To avoid this bug, click to switch to Template mode, and then hit Update without making any changes. Once you’ve got the Template mode successfully added, you can edit as you please.

I’m thinking about implementing this on our site, however I was wondering how you tackled the problem of existing customers trying to log in.

For instance, you have to have a place for customers who already have an account to log in. However, if you have a place to log into an account, but no option to create an account, you’re going to confuse people who want to create an account before placing an order. However, if you have an option to log in, create an account, or place an order without creating an account, that’s what I already have.

The only benefit is that you might get some customers to create an account that wouldn’t have otherwise.

I’m a little puzzled, as I don’t see &mvt:global:customer:ship_fname; anywhere in the code above. Are you referring to this line in the code:

<input type=”hidden” name=”Customer_ShipFirstName” value=”&mvte:order:ship_fname;”>

If so, global variable that is created will be g.Customer_ShipFirstName just like on the
ACAD page. The value &mvte:order:ship_fname is used because on the invoice page, that’s the variable that holds the customer’s first name.

If that doesn’t answer your question, please clarify and I’ll be glad to help.

Yes, global variables can be created in one of three ways:
1. By passing them to the page as a POST variable in a form submission from a prior page
2. By appending them to the URL as a GET variable
3. By creating and assigning them on the current page using one of the “tool” modules

Have you assigned the customer item to your new page?

&mvt:global:customer:ship_fname;

rather than the value statement in ACAD –

&mvte:global:Customer_ShipFirstName;

Might you explain the difference?

I like passing the variable in the form via a hidden input – might this be done with a &MyVariable=’1′ (i.e. as a “GET” variable) in an tag href string?

Enjoy your expertise.

You can create a global variable within a form on any page that will be passed to the next page when the form is submitted. Then you can use that global variable in a conditional to display your custom content.

You create your global variable by putting a hidden input field into your form, for example:
<input type=”hidden” name=”MyVariable” value=”1″>

Then, on the ACAD page, you would write your conditional like so:
<mvt:if expr=”g.MyVariable EQ ‘1′”>
Show my special message.
</mvt:if>

Since the global variable won’t persist past the current page, if you wanted to carry the conditional message through to the ACED page, you would add a second hidden form input inside a conditional (otherwise it will send all of the time), like so:
<mvt:if expr=”g.MyVariable EQ ‘1′”>
<input type=”hidden” name=”MyVariable” value=”1″>
</mvt:if>