We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 21395
    • 91 Posts
    Following an upgrade to Revo 2.6.1, I've tried to update some extras.

    Bootstrap 1.0.28 -> 1.0.29 fails. The Console window pops up, and remains obstinately blank, and must be closed by killing the window - the Close button is greyed-out.

    Bootstrap then claims to be uninstalled (no longer offering an update), but shows version 1.0.29 of Bootstrap.

    I have tried:

    Clearing the cache the MODX way
    Clearing the cache - brute force - entire contents of /core/cache removed
    Removing and reinstalling Bootstrap
    Reinstalling MODX and repeating the above.

    All to no avail.


    Suggestions of where to go next?


    Nic Boyde





    MODX 2.6.1 • PHP 7.0.27

    This question has been answered by nicboyde. See the first response.

      MODX Revolution 2.6.5-pl (traditional)

      Hosted on MODX Cloud

      Skype: nicbaldeagle
      • 3749
      • 24,544 Posts
      This is just a wild guess, but maybe something caused the upgrade install to abort after deleting some files but before making some changes related to the now-missing files.

      My best guess at a solution would be to uninstall and remove all versions of Bootstrap in Package Manager, check to make sure there are no vestiges in files or the DB, manually clear the cache, then download and install 1.0.29. If that doesn't work, it probably means the 1.0.29 doesn't work in the current version of MODX or with your version of PHP. BTW, If you're using PHP 7.2, I would back off to 7.1. before installing 1.0.29.
        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
        • 21395
        • 91 Posts
        The plot thickens. I have removed all extras, cleared the cache, logged out, and then tried to install Wayfinder.

        Same symptoms as the Bootstrap package. It ain't the Bootstrap package.

        Now to reinstall, again, the whole shebang. I will report.
          MODX Revolution 2.6.5-pl (traditional)

          Hosted on MODX Cloud

          Skype: nicbaldeagle
          • 21395
          • 91 Posts
          Quote from: BobRay at Mar 06, 2018, 09:24 PM
          If that doesn't work, it probably means the 1.0.29 doesn't work in the current version of MODX or with your version of PHP.

          Bob

          We can eliminate that. I have cleaned out all the transport packages, the cache and reinstalled 2.6.1 on top of the existing database. The database has tables in it from former packages (QUIP et al) that were not removed when the package was uninstalled, but I can find no trace of any reference to Wayfinder, for example, in the database. This site is on PHP 7.0.27.

          I then tried to install Wayfinder. No dice. Same symptoms. All extras fail to install. Something's badly broken. It isn't the extras. It has to be the database, no?

          It may be relevant that I had MoreGallery 1.5.5 installed and an offered upgrade to 1.6.2 failed with these symptoms. Since then, no extra has been able to upgraded or installed.

          Any more ideas, or am I looking at a full site rebuild?



          Nic Boyde
            MODX Revolution 2.6.5-pl (traditional)

            Hosted on MODX Cloud

            Skype: nicbaldeagle
            • 38783
            • 571 Posts
            Do you have TinyMCE installed? I have occasionally encountered problems installing other packages when it is present.
              If I help you out on these forums I would be very grateful if you would consider rating me on Trustpilot: https://uk.trustpilot.com/review/andytough.com

              email: [email protected] | website: https://andytough.com
              • 21395
              • 91 Posts
              Quote from: andytough at Mar 07, 2018, 05:26 PM
              Do you have TinyMCE installed? I have occasionally encountered problems installing other packages when it is present.

              I did Andy. I took it out first when I started trying to isolate the problem. It took several Remove Package instructions before it removed itself. Not that, I'm afraid.



              Nic
                MODX Revolution 2.6.5-pl (traditional)

                Hosted on MODX Cloud

                Skype: nicbaldeagle
                • 38783
                • 571 Posts
                Can you manually upload a package and then run it as a local install?

                Permissions on the folders in which the packages reside? (Unlikely if you have successfully reinstalled MODX)

                Have you recently moved any of your folders? ie: core/packages. If the config file was pointing to the old location this could cause it. (Again unlikely if you have successfully reinstalled MODX)

                Can't think of anything else at the moment!
                  If I help you out on these forums I would be very grateful if you would consider rating me on Trustpilot: https://uk.trustpilot.com/review/andytough.com

                  email: [email protected] | website: https://andytough.com
                  • 3749
                  • 24,544 Posts
                  Could the permissions have changed for the core/packages directory?

                  Is there anything in the MODX error log?

                    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
                  • discuss.answer
                    • 21395
                    • 91 Posts
                    The problem is now solved. Modmore got on the case and identified a problem exacerbated by a bug. It seems that since the last MODX upgrade, my hosting firm have tightened up on their mod_security installation which picked up on, and blocked, the output from a modx bug in the package installer which was sending information that it shouldn't, including raw code.

                    Modmore's fix at GitHub: https://github.com/modxcms/revolution/pull/13813

                    Full details there.

                    Big thank you to Mark Hamstra.
                      MODX Revolution 2.6.5-pl (traditional)

                      Hosted on MODX Cloud

                      Skype: nicbaldeagle
                      • 3749
                      • 24,544 Posts
                      I'm glad you got it sorted. Hats off to Mark (again).

                      For future reference, there's a technique described here that might have helped find the problem: https://bobsguides.com/blog.html/2013/05/22/debugging-cmps-a-horror-story/
                        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