We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 20358
    • 10 Posts
    Hi Everyone,

    Before committing to modx, I first wanted to take it for a test spin, so I installed to a subdirectory (ie. mydomain.com/modx). I got everything up and running great and decided I was ready to make the switch. I did a bit of searching around ahead of time, as I figured even with a simple directory move (vs. a whole server move) there would be some settings that would need to be updated. Ultimately, here’s the steps I took:

    1) Pulled down the whole "modx" directory from the site
    2) Nuked *everything* in the public_html folder (this is just a hobby site... DON’T do this on a production site smiley)
    3) Exported the modx database and dropped it
    4) Added the "setup" directory back into my saved copy of the modx directory
    5) Uploaded the contents of the saved modx directory (including the recently re-added setup directory) and ran a FRESH install
    6) Dropped the database again and imported from my backup
    7) Updated modx_workspaces to set the correct path

    This actually worked much better than I expected. The core site fired up just fine and most of the addons worked fine (tinymce, getresources, wayfinder, etc). However, two of the addons are being total jerks: Quip and Gallery. I’ve done as complete of an uninstall as I can think of, but still can’t get them working. I’ve uninstalled, removed the files, and even dropped the corresponding tables in the database.

    Re-installation runs without complaints and they both work on the front end. I just can’t do anything in the Manager > Components screen. Trying to view/update/add any items from there (in both apps) results in "loading" pop-up that just runs for ever.

    I’m wondering if there is some mystery setting somehwere that I’ve missed. Like I said, I already updated the workspaces table and I stumbled on this thread: http://modxcms.com/forums/index.php/topic,61890.0.html, which got me to check the config.inc.php files, but those all look good. The only other table I stumbled on in my tinkering that looked related was the modx_namespaces directory. There is a value in here called something like {core_path} and I’m not sure exactly how that’s defined.

    Any tips would be greatly appreciated.

    Thanks!

    Swill
      • 3749
      • 24,544 Posts
      {core_path} is replaced with whatever is in the config.core.php file in the MODX root.

      Quip and Gallery may create and set their own System Settings, (or User Settings or Context Settings) so you might look for those -- they’d probably leave them alone on a reinstall.
        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
        • 20358
        • 10 Posts
        Quote from: BobRay at Apr 21, 2011, 12:48 AM

        Quip and Gallery may create and set their own System Settings, (or User Settings or Context Settings) so you might look for those -- they’d probably leave them alone on a reinstall.

        Yeah, that’s kind of what I was thinking. I dropped all of the quip* and gallery* tables from the database for this reason, but I wouldn’t be surprised if there is a general place in the core modx tables where individual package config is written.

        I think a key note here is that the only two packages I’m having trouble with (quip and gallery) are the only two that create a new Manager section under the Components menu. I’m going to check through the snippets too and see if there’s something silly like a hardcoded path directly in one of those. I would be surprised if that was the case, but I should check at least to rule it out.

        Swill
          • 20358
          • 10 Posts
          Now here’s something strange. My config.core.php file in root is totally blank. I’m assuming it shouldn’t be. Here’s what’s in the other config.core.php files (under manager and components):

          <?php
          define('MODX_CORE_PATH', dirname(dirname(__FILE__)) . '/core/');
          define('MODX_CONFIG_KEY', 'config');
          


          Should I just copy that? Maybe I’ll just try it...

          Swill
            • 3749
            • 24,544 Posts
            Don’t copy, they’re at a different level. You’d have to make it dirname($__FILE__).

            Actually, you should be able to just run Setup in upgrade mode. Make sure that file is editable first.
              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
              • 20358
              • 10 Posts
              Ok, so I just pulled out the shotgun and killed it. And now it’s working great. Here’s what I did:

              1) Nuked all the gallery* and quip* tables from the database
              2) Pulled a fresh export of the database
              3) Completely nuked all the modx specific files/directories from my root folder
              4) Uploaded a brand new modx revo zip file
              5) Ran installer from scratch
              6) Dropped all tables from the modx database and restored from my export file
              7) Installed Gallery and Quip

              The only bummer is that restoring the gallery from a data export seems to risky based on the problems I’ve already had, so I’m just going to manually put it all back together.

              The root of this whole thing was likely file permissions when I originally tried running the install over my existing modx directory structure instead of just starting from scratch. Just out of curiousity, has anyone managed to handle this task without all of the trouble I had? It seems simply moving to a new directory shouldn’t be that complicated...

              Swill