OZONE Asylum
Forums
Site reviews!
Almost finished with the last project...
This page's ID:
21572
Search
QuickChanges
Forums
FAQ
Archives
Register
Edit Post
Who can edit a post?
The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.
Your User Name:
Your Password:
Login Options:
Remember Me On This Computer
Your Text:
Insert Slimies »
Insert UBB Code »
Close
Last Tag
|
All Tags
UBB Help
TP While osCommerce is used on appr 1400 live shops and feels quite reliable in the role it's built for, it does have some serious shortcomings "out of the box" so to speak when it comes to extending/modifying/integrating it in different situations. A couple of things: - Relies on register_globals = on - uses global variables a lot - multilingual pages/texts are not stored in db, it's files holding constants with the texts - it uses OOP for some HTML-generation & the cart, and procedural code for db-access & most logic. - SQL is generated "everywhere" in different places - No templating to speak of, to change the layout you need to change several (5-10) files with HTML + PHP - To add a new text page to the site you need to modify the header-include for the menu, the page-listing file and add one page for each language holding constants for the text (I probably forgot some steps here) - It really lacks in code documentation There are advantages though, it has an extensive admin interface for product management, clients, orders, newsletters and things like that. There are a lot of contributions created, some sort of template system is available as well (which I havn't tried). In short, it takes some time to get to know the code and the thoughts behind it, once you get that, it's workable but not very flexible. The main reason we choose this tool was to get the shop up & running quickly. Had I done this myself a lot of the things that's placed in files now would be in the db, all the db-access would be separated from the business logic and there would be some sort of simple templating system, that's for sure. So, I guess it depends on what you want to gain from the CMS integration, it would probably be doable to "insert" the shop into a site powered by a CMS leaving navigation, header/footer and so on to the CMS. To lose the boxy look you'd have to get into the classes that generates the "boxes" and do something else instead. If I understand what you'd like to do, I'd guess you'd be looking at 2-4 weeks full time work for a simple integration. I've put 60 hours into this and that includes install, configuration, css, images, installing contributions and adding the extra-pages modification. If you can take a 3.6 Mb mail I can send you the .chm file I generated, that gives a fair idea of how much code it is. /Dan [url=http://www.dmsproject.com/] [img]http://www.dmsproject.com/gif/newSiggie.gif[/img] [/url] [url=http://faq.ozoneasylum.com/FaqWiki/shownode.php?sortby=rating&id=260]{cell 260}[/url] -{ a vibration is a movement that doesn't know which way to go }-
Loading...
Options:
Enable Slimies
Enable Linkwords
« Backwards
—
Onwards »