FYI:
A new concept has been added to MODx 0.9.7:
workspaces. For now, there is simply one active workspace in a MODx core deployment, which is the core itself. In the future, workspaces will allow you to create alternate core or package installation locations, for instance, to isolate an upgrade to a component from a production core deployment, or even a core upgrade.
For now, all you need to know is that a new management console is available in the manager, under Tools --> Workspaces, which will allow you to create transport package entries (stored/tracked in the MODx database) for actual physical zip packages you place in your workspace’s packages/ directory. Here are the basic steps for installing a package...
- Build or download the component’s transport.zip package into your core/packages directory.
- Go to Tools --> Workspaces and choose Create New Package from the toolbar (or right click on the default workspace and choose Create New Package from the context menu) -- just enter the name of the package (minus the .transport.zip part)
- After the record is created, you should see the package listed in the tree, and you can now select Install, which will execute the package installation process.
Please note, there is a lot of error handling and other nice features left to be added into the installation process, i.e. resolving dependencies, renaming existing components on conflict, etc., but the basic process works well enough.
I will be announcing a temporary download location for getting the available transport packages later this afternoon.
MODX Staff