What are the most urgent additions to MODx ?

I would like to see template aliases. What I mean is that since TV are related to templates, if you want to apply different tv sets to sections that use the same template you need to duplicate it. If there were template aliases you could have basically one template and use it with different TV sets. Yes this can be done with chunks and templates but could be better with some sort of aliases which would be a cleaner interface.

I also would like to see more plug-n-play snippets like a single blog tool (complete with admin et all). Having to build a blog (which is one of the most common features) from bits ans pieces is a bit of a drag. Even with the cool tools that we have (Ditto, newspublisher, jot and reflect) it is a bit tougher than it should be. TO make a blog you need to learn how to use several different snippets which makes the learning curve a bit overwhelming.

An integrated simple forum would be very nice as well as a wiki.

Integrated front end web user page editing would be fantastic, quick edit is the coolest thing since the slinky but not being able to allow web users to use it is a drag. And making everyone a manager user is not a good idea...this could work if the manager was not so complicated (as a developer I like it, but from a user pov it is a bit overwhelming).

I know that v1 will resolve a few issues, just thought I would add my views to the list.

Once WLPE gets to a stable enough release, I’d suggest adding that in as one of the core scripts. It’s something that not a lot of CMS’s have (at least to the level Scotty coded it), so it would be a nice thing to "show off" in the CMS arena.

Quote from: davidm at Oct 20, 2007, 05:19 AM

Would you mind (if not already done) sharing your hack with the core team ?

Maybe they can fit it into the totally new caching mechanism of 0.9.7, who knows ?

I didn’t record the changes I made and my code is a mess. Basically I just commented out the cache processor writing the document meta arrays and after this siteCache file is loaded I run some SELECTS to get the require document meta data in real time.

If a mod really wants my hacked mess they can have it but I’m sure they can code something more elegant! They said they are addressing the 5000 document limit - not sure if via the same method?

Cheers

The 5000 document limit will be adressed indeed, let me quote Jason (OpenGeek) :

Quote from: OpenGeek at Oct 11, 2007, 07:57 PM

Just an additional note regarding some of the caching improvements that are coming in MODx 0.9.7 to address performance and scalability against a graph of volume a site’s content repository might consist of:

• More modular cache files, loaded on demand; config is separate from the document map, which is divided into contexts, scripts and content are separate, etc.
• More control over what parts get cached and which parts don’t; even how/where it gets cached. You can even disable caching entirely; however, the database load at that point would be tremendous, unless you had...
• Database result set caching to address database load in general, with support for memcached or your own custom cache implementations. Individual result sets can even be cached indefinitely, for a specified number of seconds, or excluded from the cache via the new xPDO-powered API.
• More granular ability to control caching on any kind of content element (i.e. chunk, snippet, TV, plugin, module, template, etc.) via tags or API, i.e. force TVs not to be cached.

But, that’s the challenge in developing any web application with an eye for performance and scalability; it’s a constant struggle to balance the two because they are, and will always be, at odds.

Great - whens 0.9.7 out?

Quote from: Fellini at Oct 18, 2005, 10:14 AM

A thoroughly-documented API.

Yea, that wiki is kinda red on quite a lot of the API pages
One central and complete source of documentation for snippet and plugin writers would open ModX right up to many more users. In turn that could help generate more features and even maybe more eyeballs to help tweak the core code to help with the development cycles of existing modules etc.
God knows I wish I used more of the undocumented api’s whilst re-writting some of the core php but wasn’t able to spend time experimenting to get results.

I understand it’s a spare-time resource and y’all are busy on 0.97 but one day I’d love to see the api completely in there and benefit from that awesome functionality that using ModX api’s gives.

Cheers

TxRx

Quote from: TXRX at Dec 07, 2007, 08:39 AM

Yea, that wiki is kinda red on quite a lot of the API pages
One central and complete source of documentation for snippet and plugin writers would open ModX right up to many more users. In turn that could help generate more features and even maybe more eyeballs to help tweak the core code to help with the development cycles of existing modules etc.
God knows I wish I used more of the undocumented api’s whilst re-writting some of the core php but wasn’t able to spend time experimenting to get results.
I understand it’s a spare-time resource and y’all are busy on 0.97 but one day I’d love to see the api completely in there and benefit from that awesome functionality that using ModX api’s gives.
Cheers
TxRx

http://docs.modxcms.com/ - 0.9.7 API Documentation

Eventually this will be populated with more package tutorials and such, but the code itself is pretty heavily documented, so this will help.

Awesome. Looking good and some sound advice indeed
thanks!

TxRx

Please add a thumbnail tool that works with Template Variables. Thanks.

Update the site, I was so confused at the basic blog tutorial. It uses snippets which don’t even come with modx!