We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Answered 2.3.3 Advanced Upgrade

    • 4172
    • 5,888 Posts
    Bruno17 Reply #11, 11 years, 5 months ago
    Did you try, if a complete clean new advanced setup does work?
      -------------------------------

      you can buy me a beer, if you like MIGX

      http://webcmsolutions.de/migx.html

      Thanks!
    • discuss.answer
      • 50264
      • 15 Posts
      mattkirwan Reply #12, 11 years, 5 months ago
      UPDATE:

      I decided to spin up another server and install on that. It all went perfectly.

      Really bizarre as we use ansible for provisioning each machine, meaning the setup/software was exactly the same.

      I'll be keeping an eye on that particular project/server now (I don't like not knowing what actually caused the problem).

      Again, thank you all for your help. I think I'm gonna hang around here more.

      Matt
        • 50264
        • 15 Posts
        mattkirwan Reply #13, 11 years, 5 months ago
        Quote from: Bruno17 at Apr 16, 2015, 02:09 AM
        Did you try, if a complete clean new advanced setup does work?

        Hi Bruno,

        Yes at some point I did run through the whole process and try to make a new advanced install (negating the DB overwite warning) and the 'test db' link worked straight away (I didn't take it past there, but that was all I needed to know! [connection settings etc...]).

        It feels like there is some kind of caching beyond '/core/cache', 'my browser cache' and the '/web/setup' files - all of which we're wiped everytime. Opcache may have been enabled on the first couple of runs, but that was disabled and reset once I'd realised that requirement.



          • 3749
          • 24,544 Posts
          BobRay Reply #14, 11 years, 5 months ago
          I wonder if one of your plugins might be causing the problem. I think some parts of Setup cause System Events to fire. A plugin connected to one of those events will execute, but MODX isn't really in a normal state (for example, there may be no $modx->user or $modx->resource), so the plugin executing at that point may crash.

          I've seen this happen more than once with upgrades, though it's not very common.
            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