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

    I just spend 4 hours to get evo 1.0.3 to work. After an upgrade installation I couldn’t access the frontend anymore (error 500).
    And in the backend the login worked, but after the login i only saw a plain unformatted html site. The main problem was, that the $modx->config was not correct. So the backend couldn’t read the $manager_theme config etc.
    To fix it i had to delete (or rename) the site-cache files under assets/cache . I deleted "siteCacheidx.php" and "sitePublishing.idx.php". After that the backend is accessible as usual and the "Delete Cache" command there should be exectued, to get the frontend to work again.

    Anyone else has those problems? Anyway, thats not what i call plug and play. I had to look into the DocumentParser Code to find out where those config problems come from.
    Can’t the installation script delete the caching files to prevent those errors in future updates? Or show up a very large warning that some files should be deleted manually?