We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 18817 ☆ A M B ☆
    • 205 Posts
    I’ll have to keep on the look out for it smiley

    Thanks again for the all the replies.
      Sal Baldovinos
      SEO & DIGITAL MARKETING

      ARIEL DIGITAL | Maximize Your Potential
      www.arieldigitalmarketing.com
      • 4971
      • 964 Posts
      Download PackMan without installing it if you dont want it
      and it will let you know when there is an update!!
        Website: www.mercologia.com
        MODX Revo Tutorials:  www.modxperience.com

        MODX Professional Partner
        • 3749
        • 24,544 Posts
        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).
          Did I help you? Buy me a beer
          Get my Book: MODX:The Official Guide
          MODX info for everyone: http://bobsguides.com/modx.html
          My MODX Extras
          Bob's Guides is now hosted at A2 MODX Hosting
          • 18817 ☆ A M B ☆
          • 205 Posts
          I like that v2 & 3 will support settings & resources. Hope it’s not too long laugh
            Sal Baldovinos
            SEO & DIGITAL MARKETING

            ARIEL DIGITAL | Maximize Your Potential
            www.arieldigitalmarketing.com