We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 10512
    • 28 Posts
    OK, whew. I ran the upgrade installer and all is restored (locally, that is). So since I am a newbie wink -- here is what I learned in case this happens to someone else...ZAP’s suggestion to look at the database in a text editor was good. I decided to try an upgrade, and it seems to have fixed the problem.

    I created a local db with the same name as the remote, imported the data- downloaded the current modx installation- overwrote most of the modx files, making sure that I had a back up stored somewhere else- put the original config file back in (manager/includes) and ran the installer- updater. Then I copied my old assets files (images, and any assets folders I had created earlier) and all is well again.

    Thanks to all who gave suggestions. I have a new motto- BACK UP EVERYTHING...I have no trust in my host and will be moving shortly.

    Catherine
      • 25663 MODX Staff
      • 12,272 Posts
      Glad that worked out gata. smiley
        Ryan Thrash, MODX Co-Founder
        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
        • 33372
        • 1,611 Posts
        Very good news indeed. I agree wholeheartedly with your new motto. I used to ask myself whether another backup was really necessary if I’d made one recently, but now I’ve conditioned myself just to do it reflexively every time I make any significant changes to a site.
          "Things are not what they appear to be; nor are they otherwise." - Buddha

          "Well, gee, Buddha - that wasn't very helpful..." - ZAP

          Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options