Quote from: gspark at Jun 11, 2007, 02:20 PM
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 ?
Yes, transport packages will be able to export data and files from any deployment to any other; of course depending on your specific needs, it may be better to isolate sites to specific databases vs. combining them all. Think of the new MODx architecture as three-or-more-pronged: the core code or framework, one or more ’mgr’ (content management) contexts for administration, and one or more regular ’web’ contexts. You could have one framework, with one database and one manager to administrate all your web contexts, or you could have one framework, with multiple databases and multiple managers to admin each web context individually, just to name two possible usage scenarios; many more will be possible.
Quote from: olafmol at Jun 11, 2007, 02:41 PM
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.
Right now, the only things left to implement from the 0.9.7 roadmap, though not trivial by any means, are the Transport Packaging (in progress), the actual Add-On Content Packs to be installed via the new installer (which will be put together when the Transport Packaging is done), the new Upgrade processes (which will feature at least partially-automated tag and code migration tools), and a few new interfaces/interface changes left in the manager to handle Contexts and few other new/changed features.
Versioning is slated for 1.0 and is dependent on some significant changes to the MODx relational model and schema-change management services that will be added to xPDO (i.e. detect changes to database tables and automatically update table structures/migrate affected data).
Good documentation, though there will be a much better foundation to start with from the code/framework perspective, will simply take time and commitment from more than myself once 0.9.7 is available for general preview.