You could make a separate package of your resources with a really simple snippet to run inside MODx:
If would look something like this (cribbed from the EZfaq script):
$res = '1,4,12,15,16'; /* resources you want to package */
$resources = explode(',' , $res);
$package_name = 'ezfaq'; /* The name of the package as it will appear in Workspaces will be this plus the next two variables */
$package_version = '3.2';
$package_release = 'beta1';
echo '<pre>'; /* used for nice formatting for log messages */
$modx->setLogLevel(modX::LOG_LEVEL_INFO);
$modx->setLogTarget('ECHO');
$modx->loadClass('transport.modPackageBuilder','',false, true);
$builder = new modPackageBuilder($modx);
$builder->createPackage($package_name,$package_version,$package_release);
$attributes= array(
xPDOTransport::UNIQUE_KEY => 'pagetitle',
xPDOTransport::UPDATE_OBJECT => true,
);
foreach ($resources as $resource) {
$c = $modx->getObject('modResource', $resource);
$vehicle = $builder->createVehicle($c, $attributes);
$builder->putVehicle($vehicle);
$modx->log(modX::LOG_LEVEL_INFO,'Added resource: ' . $resource);
}
/* now pack in the license file and readme (might not need this) */
$builder->setPackageAttributes(array(
'license' => file_get_contents($path_to_license_file . 'license.txt'),
'readme' => file_get_contents($path_to_readme_file . 'readme.txt'),
));
$builder->pack();
$modx->log(modX::LOG_LEVEL_INFO,"Package completed -- look in core/packages.");
You could also package in the elements here with the same code that’s in the loop, but changing the UNIQUE_KEY line (’name’ for elements, ’templatename’ for templates, ’category’ for categories).