-
- 571 Posts
Is the MODX 'core' directory stored outside of the web root?
-
- 1,145 Posts
I bet there is no such folder home/en
And besides it is not within your rightful shared hosting public_html (I am assuming this is some kind of shared hosting)
When do you get this error?
Does this error prevent Upgrade?
Are you able to access anything in the Manager?
TinymceWrapper: Complete back/frontend content solution.
Harden your MODX site by
passwording your three main folders:
core, manager, connectors and renaming your
assets (thank me later!)
5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
-
- 67 Posts
Correct, there is no /home/en. I don't know why the setup file(s) would be looking there.
I get the error when I try to launch the upgrade from 2.5.4 to 2.5.7.
Yes I can access the manager just fine but since I unpacked the modx-2.5.7 setup files into my system, I don't know if there's any danger in that.
I guess I should try to unpack the 2.5.4 files and see if I can reinstall that?
-
- 1,145 Posts
By chance, are using some multilingual setup, in htaccess, or index.html/php, or Babel, etc?
TinymceWrapper: Complete back/frontend content solution.
Harden your MODX site by
passwording your three main folders:
core, manager, connectors and renaming your
assets (thank me later!)
5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
-
- 67 Posts
No multilingual on this site.
-
- 24,544 Posts
I'm guessing that the second line here is where the problem is coming from (in setup/controllers/language.php):
$cookiePath = preg_replace('#[/\\\\]$#', '', dirname(dirname($_SERVER['REQUEST_URI'])));
setcookie('modx_setup_language', $language, 0, $cookiePath . '/');
You might try putting this between the two lines:
echo "<br>Request URI: " . $_SERVER['REQUEST_URI'];
echo "<br>Cookie Path: " . $cookiePath;
If you have access to the Manager, you could set the current version setting in UpgradeMODX back to 2.5.0. I think that would let you use UGM to "upgrade" to 2.5.4. If that works, you could try the real upgrade again in case the download was corrupted.