-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
White screen on upgrade to upgrademodx-2.1.4-pl #69
Comments
Just came here to report the same issue. Thanks @lektriq for the detailed report. I used the same fix. |
Thanks for the heads up! I've updated the 2.1.4 package at modx.com/extras. For those experiencing the problem, you can get into the Manager by putting this in your browser's address bar (corrected for the site URL and name of manager folder):
Once you're in the Manager:
Or just change line 180 of the upgrademodx.class.php file to:
Sorry about the trouble. For the curious, this got by me because my dev. environment has another vendor directory at that location. The new version should also work in MODX 3. Let me know if this works. |
Yes, that works, earlier today I updated about 60 websites through SiteDash, and I really don't want to have to update every one of them manually. Any way you can make this 2.1.5 so that SiteDash can see the change? |
Yes, 2.1.5 is there now. |
Thanks! All good now. |
On upgrade I’m presented with a white screen on manager access attempt.
Upgrading to upgrademodx-2.1.4-pl
MODX 2.8.1
With custom core location
Manger error log shows
[22-Mar-2021 11:38:57 Europe/London] PHP Fatal error: require_once(): Failed opening required '/home/XXXXX/public_html/1XXXXX/core/components/upgrademodx/vendor/autoload.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/XXXXX/modx-system/XXXXX/core/components/upgrademodx/model/upgrademodx/upgrademodx.class.php on line 182
This was fixed by editing core/components/upgrademodx/model/upgrademodx/upgrademodx.class.php at line 180
Original content was:
To fix, edited to:
The text was updated successfully, but these errors were encountered: