There are a couple of ways to do this. Each button’s input tag can be edited by clicking your store name, and then clicking the tab for Buttons on the right hand side. Then, over on the right hand side beside the button you want to edit, you’ll see a link for Show Code. If you click that, you can access the input tag, and edit it to add your css class. Be aware that if you click Hide Code it will reset to the original, so you’ll want to leave it set on Show Code.

Editing it this way will update the entire site with that css class. You may not want the class on all of your save buttons, in which case you can easily replace the mvt:item tag with a regular input tag, with your css class added.

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.

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.