Hi guys,
We have this issue on Modx Revo 2.0.6-pl2 & MODx Revolution 2.0.6-pl2 traditional, php5, centOs.
I don’t think much more info would be relevant for this issue, but please ask if you think it is related to another environment information.
I can’t tell about other versions.
Our installs were done through Installatron under Direct Admin.
Here is the issue:
When we download a package from the package manager, it downloads it right, but then can’t find it and generated errors when we try to install it.
Instead of looking into .../public_html/core/packages it looks into .../public_htmlpackages.
Same thing for another install which is installed under a sub-directory public_html/my_site, it looks into public_html/my_sitepackages.
The same problem occured with the Packman package, i generates the package right but then links to the wrong path for the download.
These issues have been fixed for now with this little workaround: we created a symlink public_htmlpackages pointing to public_html/core/packages .
However we are looking into Modx to use it with our future clients and don’t want to use this trick with every install.
Does anyone knows where this issue comes from and a better way to fix/prevent it.
Any help will be greatly appreciated : )
-
MODX Staff
- 10,725 Posts
FWIW, it sounds like someone may have manually added the path field in the modWorkspace record (modx_workspaces table) without a trailing slash.
Hi,
Thanks for the help.
The problem was generated by Installatron but they fixed it after I opened a ticket (they have a really reactive team).
Here is there answer, which match yours:
An update has been deployed to fix this for new installs. For existing installs, your fix is suitable, and it’s also possible to fix this by appending "/core/" to the "path" field of the "workspaces" database table.
Thank you again.
Aurelien