X-Cart forums

[carpeperdiem]

It's all coming back to me now... there's a reason many (most?) of us try, then give up on replacing the x-cart button system. It was obviously designed by committee but the members of the design team never asked the other guy what they were doing... there are at least 10 (probably more) instances of common button css and at least 6 (definitely more) templates to make the buttons. NOTHING is logical or consistent. And there are instances where css overwrites css which overwrites css. WTF? And that's why everyone who knows xcart leaves it the hell alone.

But...

I was trying to make the X-Payments "lite interface" button look like something that wasn't designed in 1998. And with very little effort and help from google, I now have a spectacular css submit button in X-Payments iFrame "lite", complete with active states and hover. PM me if you want to see it. It is a modern button appropriate for 2012 (unlike most of the xcart buttons). If I can do it in a few minutes for free, shouldn't we expect professional interface designers to do it since we paid them? AH... that's for another thread.

Of course, if I can do it in X-payments, surely I can make this modern button work in xcart.

3 hours later...

OK, some (many, most) of the buttons are behaving and look and function as they should.

Since I am doing a css button, I don't need the 2-part buttons and I successfully removed the "right" portion of the button from

file: /common_files/customer/buttons/button.tpl

FIND:
<img class="right-simple-button" src="{$ImagesDir}/spacer.gif" alt="" />
and
<span class="button-right">

and delete. Bingo. Easy. First time. Right part of *some* buttons are gone, and a simple adjustment to the css padding of the left part makes the button exactly the right size. Perfect!

HOWEVER...

The file, /common_files/customer/buttons/button.tpl seems to be the only place that has the "right" code in a template. HTF does xcart make the other buttons? Webmaster mode is not helpful. OBVIOUSLY it's in the css.

Of course it is...

Another hour of finding css that cascades on top of other css that cascades on top of other css. What were these dudes thinking?????? I know, this is nothing that hasn't been discussed a zillion times before, but I had to get it out.

My buttons are now css, and there is a look and feel that doesn't read, "1998".

[Vacman]

Now where's the Like button for this post...