Modx 9.7 suggestions

As i’m using the subdomain hack with one modx install sharing all the content, I’m noticing it can get confusing really fast when dealing with several folders and keeping everything separate from area to area, head spinning

I’m not sure if Modx 9.7 makes it any easier, I would recommend the following:

if using one Modx install for multiple domain/subdomain - have some level of smart foldering built-in so we can clearly separate the content

ie if one folder (container) represents one domain then any snippets, documents, code, etc can understand that this particular domain refers to this one container

i think currently Modx paths are based on the the root of the menu tree structure but with multiple domains, a smarter way would be to designate the domain container as the root so that any alias paths begin there. I have some misc unpublished containers with misc published files, this creates a mess when working with alias paths, you wouldn’t want your URL looking like domain.com/misc_trash/content,

It’s a very different feeling handling separate domains with separate Modx installs vs one Modx install for multiple domains similar to running blind, all the more reason to have a smart-folder capability so that the snippet calls know exactly which folder is which.

Perhaps, I need a better understanding on how to organize the folders/documents, having to rely on the root menu tree for alias paths leaves little room to have misc containers

It is my hope with Modx 9.7 + that we can clearly distinquish all documents, containers, snippets, etc domain to domain - am i making any sense ? if not please discard

This is precisely what Contexts (and some related changes) will be used for in 0.9.7+. You can customize some or all of the configuration (i.e. system_settings) by Context. Consider these scenarios:

• multiple domains, multiple databases, multiple managers - One MODx core engine, multiple databases each with a distinct manager interface will be possible in 0.9.7. Just define the location of the directories needed for each domains ’web’ and ’mgr’ contexts, and a custom config and cache directory for each domain, and you can run any number of domains from a single MODx core installation. The MODx core engine essentially becomes a library, similar to PEAR, that can be securely located outside of the webserver document directories; only the code and other web resources needed for each site/site manager will have to be deployed to each domain specific web directory (a unique index.php per context).
• multiple domains, one database, one manager - A context can also be a way to access shared content (i.e. from a single MODx repository) across multiple domains; again, installing MODx in a common location, deploying a single ’mgr’ context common to all domains, and then providing a ’web’ context in each domain-specific web directory (i.e. unique index.php for each web context).
• multiple sub-domains, multiple front-controllers - Same as above, except with sub-domains...
• multiple sub-domains, one front-controller - Same thing as above except all requests go through the same web directory (i.e. same index.php) and the context is determined by some other process (e.g. a snippet, plugin, template, TV, etc.)
• multiple sections, multiple front-controllers - Similar to multiple domains or sub-domains, except sections would just be unique areas (e.g. web sub directories) within a single domain or sub-domain, served by a unique index.php (i.e. each section would have a unique web directory)
• multiple sections, one front-controller - As above, except another process would determine the context and all contexts would be served via the same index.php.

I love MODx - and can´t wait to see 0.9.7 ;-)

What will be the plan for 1.0? Will it be similar to 0.9.7, but absolutely stable and tested, or is the plan to introduce new features?

097 when released finally should be very stable and tested ... it’s been in development for more than a year.

Perfect!

This means, 1.0 will be much, much better? ;-)

Thanks for your time and effort, you put into this project!
(and thanks for sharing it)

Ok, Ryan polarized the issue by answering ambiguously. I’m not going to talk to the stability and testing of the product. It’s open source, and it’s stability and testing depends on the community. But 1.0 will definitely be about new features. 0.9.7 is about the new core engine and architecture, without much change in the feature department. I have a new roadmap I will be posting shortly that covers the coming changes for 0.9.7, and I’ll get one for 1.0 out soon as well.

You (and 0.9.7) are great!

http://modxcms.com/roadmap.html

sounds good so far can’t wait to see it released.

Since modx 9.7 will have the capability for one modx install to rule them all, would there be any feature to import other modx databases ie, content, folders, etc so they are all merged into one modx db ?

sounds good, but how realistic is this roadmap? ie how much time will it take to implement all these functionality? maybe it’s a better idea to focus on a subset of these functions and include these in 0.9.7 and try to aim to release this version in about 6 months from now?
further, the biggest 2 ommisions to lift MODx to the next level that i see are versioning/revisions, and a good documentation.
Still, MODx is by far our favorite CMS/CMF!!

Olaf