View Single Post
Old 09-19-2012, 11:50 PM
Cpt.Crashtastic Cpt.Crashtastic is offline

Join Date: Jan 2006
Posts: 219

Default Re: Overiding CDev Module css

XPlorer's methos was a lot easier and the one I did not try before doing it programatically.

This is an interesting debate.

Which method would make it easier to identify where the problem was if this or any other template was altered during the upgrade process?

Replacing a skin completely may make it easier to identify quicker.

I need to do some testing on what would happen if you have multiple skins themes installed. If this is the case, altering the CDev css is not an option, in my opinion, as you would have nothing working to go back to.

What happens if we have multiple modules altering a CDev modules CSS? It could get proper messy

If you are gong to sell skins you need some element of control.

If there was a notification process for developers that gave them say a weeks notice for an impending upgrade it would make life easier.

I've just got an x-cart next test site up and running with Drupal if you are interested. It took a suprisingly long time to get there.
Xcart 4.4.?
Xcart Next
Litecommerce with Drupal

Custom Mods, Hosting and Support for Xcart-Next and LiteCommerce
Reply With Quote