In ShopSite v6.x the order of the text fields and field lables is
switched, with the labels now on the left and fields on the right, both
in separate columns of a table, and the text is right aligned and the
fields are left aligned which gives it a nice centered look. ShopSite
v6.0 has been out for about a year, and v6.1 has been out for quite a
few months too. You can get a demo to try at
http://www.shopsite.com/demo.htmlWhat I have seen done in quite a few v5 and earlier ShopSite carts is
either:
1) start your own table in the fields for text at the top of the
shopping cart screen and end it in the text at the bottom, this way you
can force everything in between into whatever size table width you want.
2) put blockquote tags at the end of a text setting for some piece of
text immediately prior to the checkout fields, like maybe the Billing
Address text field (see Preferences -> Store Text -> Checkout).
Blockquote will act as a sort of tab spacer for everything after it and
it will move the fields over to the right away from the left edge of the
screen.
-Loren
webMaster wrote:
We have lived with this problem for a long time... but I'm trying to
resolve
it now...
In shopsite 5.01, the layout and html on the shopping cart and checkout
pages is just terrible. The billing entry fields appear before the name
of
the field and they are all aligned to the left outside of any table
structure unlike the rest of the page that is centered! Same with the
shipping fields.
For quite some time we have worked around this by using HTML comment
tags
(like this <-- Billing Address ) to hide most of what shopsite generates
dynamically and we placed our own rewritten version of the default HTML
in
the "bottom of the screen" fields.
Recently however, we've discovered a couple problems in taking this
approach... one being that it is not possible to manually display any
dynamic variables that shopsite is using on the checkout page.
Has anyone else experienced this and does anyone know if SHOPSITE
released
any kind of fix or upgrad from version 5.01 that resolves this issue?