MODx 0.9.7, contexts and the API

Hi all,

I’m currently rewriting the Doc Manager module for 0.9.7 and wanted to save a few queries on the database by utilising the $modx->getChildIds() method but seem to have a problem (it doesn’t work ) because, as far as I can tell, the resourceMap variable that the new getChildIds() relies is stored in the web context cache and not the mgr context cache.

So, my question is: Am I being dim and missing something obvious, or, is there a way at getting at the resourceMap variable from the mgr context?

I can always query the database direct but getChildIds() would do just want I need at the moment.

Hope that makes sense,
Garry

Good points garryn... this needs to be refactored slightly so we can load resourceMaps from any number of contexts for such purposes.

Is there an approximate timeline as to when we will be able to start testing the contexts system (adding our own contexts, etc)?

Quote from: sirlancelot at May 14, 2007, 10:38 AM

Is there an approximate timeline as to when we will be able to start testing the contexts system (adding our own contexts, etc)?

Several things need to be completed for context support to be implemented in the new manager interface...

• Transport Packages - These will be zip packages that contain serialized data, any dependent file resources, and optional scripts (to perform complex installation or upgrade tasks). An entire context can be exported and packaged from one installation and can then be installed in another in this way. The 0.9.7 release will include the standard web and mgr contexts, plus the new connectors context.
• Upgrades - xPDO will have the ability to detect differences between a model definition and a table. In this way we can have upgrades automatically bring all tables up to date with any structure changes.
• Context Management - How users will interact with and manage contexts in the manager UI needs to be explicitly defined. Right now, I’ve provided the infrastructure in the framework to start making use of them, but that’s only part of the challenge.

I suggest you and I collaborate on implementing specific types of custom contexts so we can full define the implementation and get it usable for a beta release.