nah- i completely understand.. like you said, when you put that much work into something its absolutely reasonable to charge for your time and effort...

It's the way it's displayed, when you compare it to other systems out there, it's scary to the standard customer first coming to the net.

Buttons too small, order details displayed on every page, each page being a mile long, if your not logged in it takes you round in a little circle. Etc.

There's many many sites that make it much simpler and faster. X-carts checkout "works" but it certainly isn't visually user friendly.

How easy is it to simply remove the menus during the checkout process? Just read one of Jakob Nielsen's latest bulletins and it had this snippet:


Not sure where to start on this one.

Thanks

Dan

It can't be that hard. You could wrap your side menus in code similar to that found in customer/home.tpl for the page titles. Like {if $main ne "cart}SHOW MENU{/if}.

Dunno, I'm sure Jon can expound further.

Thanks adpboss, just found this thread which I think will do what I want.

http://forum.x-cart.com/viewtopic.php?t=11543

Dan

An even easier way, which I've done, is to open cart.php

Find:
$smarty->display("customer/home.tpl");

Change to:
$smarty->display("customer/home_checkout.tpl");

Then save home.tpl to home_checkout.tpl and edit it removing all the access.

Thanks Jon, that method is a lot easier and more how I want it looking but am a bit confused about something. In my new home_checkout.tpl I have decided to use:



To NOT show the categories menu when the user checks out (and past the View cart stage). This works when a user is logged in but when an anonymous user comes to checkout, the menu is still present -am I missing something?

Thanks

Dan

OK, it's:


BUT, I seem to have problems writing an or statement like:


and other versions and they don't seem to work...any help?

Thanks

Dan

Should work with no problem.

If that is not working for you try

Thanks, I tried both but for some reason it only seems to want to process the first bit before the OR in both cases...very odd. I've sort of circumvented this so don't need it urgently now...be nice to know what the problem is though for future reference. :?

Thanks again,

Dan