-
☆ A M B ☆
- 24,524 Posts
That’s trivial to modify. I have that one in my downloads folder to look at when I’m ready to start working on an ecommerce solution for MODx. I have my own ideas, but if somebody else gets there first it’s not going to bother me any.
Any updates on this topic? I can’t find a more recent (or productive) thread regarding this topic than this one, which is sadly 6 months old.
Hopefully SOMEONE has made some progress in that time!
As modX approaches 1.0, including a native ecommerce solution should be a huge priority!
Also, might I add the goal of MODx 1.0 is not to provide out of the box working solutions, but to enable you to build web applications yourself * (or have it built) with the benefits of MODx’s flexibility

And shorter development time which means better time to market and lower cost... not to mention greater customisation
* That’s the
Framework in Content Management Framework
.: COO - Commerce Guys - Community Driven Innovation :.
MODx est l'outil id
Well, so far I have yet to meet a client that I can use modX with. I don’t do simple brochure sites, and I don’t have time to try and figure out how to make some $400 ecommerce package work with modX, so over the years I’ve been forced to develop my own "Content Management Framework" from which I can build entire applications and drop in whatever software I happen to need without it conflicting with my own code at all.
The way I successfully achieved this goal was by making the content management not interfere with the framework. Seems like modX got this wrong, then? No content management framework implies infinite flexibility, because from there you can do anything. So why make something to restrain what you can achieve, and then spend effort trying to increase flexibility? In that light modX is exactly like any other CMS.
Edit: P.S. please tell me I’m an idiot and modX is exactly what I want, infinitely flexible, won’t get in the way of any proprietary software I want to run with it, all the while having a superb CMS to make the easy stuff, well, easy.
Simply put, if we were like Microsoft and promised everything under the sun and then stripped out the big features what would you say then? If we don’t say what will be in x release, it gives us the freedom to ensure that every release is the best we can make it be and nothing is half baked.
As for Code Igniter, it is a geat framework (although being confined to using controller structures is too restrictive for me), but its not a CMS.