What are the most urgent additions to MODx ?

[Guest]

Welcome, Guest. Please login or register.
Did you miss your activation email?

1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[davidm]

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

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.

[andytwiz]

Great - whens 0.9.7 out?

[TXRX]

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

[splittingred]

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.

[TXRX]

Awesome. Looking good and some sound advice indeed
thanks!

TxRx

[worchyld]

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

[Ross1234]

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

[doze]

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

You can use phpThumb with image tv.

[neil]

I hope the Phorum Integration will be available soon..Phorum is great, simple and fast forum for small communities.. hmmm.. of course, you all should know..

hehehe

[rx2]

I'd love to be able to schedule chunks for publishing and unpublishing. Most of the promotional content I do on sites is variable. For now I just comment out the contents of the chunk, but having the client being able to schedule them would be great.

[le_block]

1.) I'd like to see a better internatiolization. (one document - multiple languages) for a better explanation try the demo of typepublish http://www.typepublish.org/.

2.) Please redesign the backend of the revolution fork of modx. it looks horrible in an usability point of view. IMO it is a slick GUI (and Ext works fine), but the backenduser will see nothing inspite of a lot of blue buttons. The User will be overwhelmed of the possibilities he/she can click on. thats not the productive way.
I suggest you've a short look at the backend-interface of a wordpress blog (2.5).

Thanks, le block

[smashingred]

le_block

1. I think we all agree that internationalization of single documents needs streamlining. I hesitate to say but think that this will become a modx core addon for revolution once it is out.

2. The backend is not perfect but there are several options for customizing the back end or creating a new one that will be different for editors or managers. You could create a whole new manager interface or what I call a side end that non-admins could use to manage the content, auditing, and other tasks.

BTW. The new WordPress 2.5+ interface is not perfect. The dashboard is utterly useless for regular users. I'd prefer to jump right into tasks. If I was getting stats or some other info there (which can be done with a plugin) but otherwise I would rather end up on the new post or manage screen.