What are the most urgent additions to MODx ?

Fellini and alexw,

Also, what parts are the most lacking the the developer-oriented documentation that we already have up?

http://modxcms.com/developers-guide.html

Thanks!

Okay, the API list is a whole lot bigger than the last time I looked , and I see a lot more detail around some of the other areas. There’s even a lot more info in the modules docs. I now consider myself to have "shot off at the mouth before looking"

But I guess I’m still having trouble getting my head around some of the logic of the advanced stuff like TVs and module/plugin creation and how that would tie into real objectives. Not being a programmer, a lot of this isn’t all that intuitive to me. Usually the way I manage to learn is to take a concrete, working example, and hack at it until I make it do what I’m looking for. The more comments in an example, the better.

I realize there’s a million-zillion ways of doing things, and everyone has their own styles and objectives for their sites. But there’s got to be a "best practice" approach, a "this is how *I* would do it" that gets at what the developers were thinking when they made the feature(s). So I guess my first wish still kind of stands -- there’s common gap that pretty much *all* CMSes have, and that’s "integration with popular applications". If you concentrate some effort on providing a couple of extreeemly documented examples of things like a popular forum, gallery, cart, etc., and turn people loose on that, I think you’ll have a winner here. Because it’s a royal PITA integrating any of the others out there!

I mean, this *was* a wish list, right??

Gallery 2 ... check
SMF ... check
IPB ... partially done
e-commerce ... still in planning

That kinda stuff?

Quote from: rthrash at Oct 18, 2005, 06:41 PM

Gallery 2 ... check

;)

multi lingual sites

Fellini, Plugins are tough. I think it’d probably be very good in fact to have a explanation of how the document parser works, including where and how the different events tap into it.

I’ve started on that; I’ve actually written plugins using two of the Template Service events, and have documented OnWebPagePrerender and how it was used in the adding of the lang variable to links in the page. As I work with them and come to understand them, I’ll be adding to the list.

Quote from: emi at Oct 18, 2005, 08:07 PM

multi lingual sites

Check this.
http://modxcms.com/forums/index.php/topic,409.0.html

e-commerce and an advanced search system (to search for folder, subsites or fields like alias or description)..

For me an important addition would be a better/easier way of organizing and moving snippets/plugins/modules/chunks.

For example I am working on a some code that consists of a module,plugin,snippet and some chunks. I have to keep switching between all the tabs in the resourcemanager to find all the things I am working on. Also it is hard to find the correct snippets/plugins/modules/chunks in the rather long lists I have. It would be nice if you could put the snippets/plugins/modules/chunks in a group so you know they belong together and are easier to find.

Next thing is moving those snippets/plugins/modules/chunks to a productionserver or swap it with other users. Currently you have to copy the code and settings and make sure all the events for plugins are set correctly. This is a quite difficult and timeconsuming process. It would be very nice if you could just "package" the snippets/plugins/modules/chunks you need. They get combined into one file and you can just copy that file to your server and "unpackage" it.

And last I think that the usermanagement is now too complex. I have users that have to login to the frontend and manager and I can’t really explain to them why they have to login twice, have two passwords etc... Also the administration of a person that is twice in the database is a bit difficult to keep them in sync.

Related to that is that it is hard to get a bit of overview of which user can access what documents or the other way around, what documents belong to what documentgroups and which webusergroups/usergroups can access/edit them. It would be nice if you could highlight documents in the documenttree that belong to a specific documentgroup or that can be accessed by the currently selected user/group..

I had some more minor stuff, but I forgot what it was but those are not urgent anyway