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
[4.0] Joomla hates root jail: errors when JPATH_ROOT is / #30756
Comments
Can you check if PR #23149 fixes the issue? |
This change JPATH_ROOT don't work: define('JPATH_ROOT', JPATH_BASE === DIRECTORY_SEPARATOR?'':implode(DIRECTORY_SEPARATOR, $parts)); The test could show false results, I am not able to check it closely. I only have the live version. If this help: Joomla 3.6 works on this configuration, but i can't update it to 3.9. |
That's not the change in #23149. |
@richard67 I have this issue for Joomla 4.0. I have no way to test for v.3.9 |
@bato3 why can't you test on 3.9? |
@N6REJ Because I only have one available place where I can check it and it's occupied by Joomla 4.0. And it's a live version. You know it: All developers have test environments and some even have production environments. |
using 4.0 for a production site is not a wise move imo. |
Steps to reproduce the issue
In some web-server configuration, when
JPATH_ROOT
is/
Joomla don't work correctly:mod_rewrite
work only for main page, others render as 404Expected result
index.php?option=com_content&view=article&layout=edit&id=841
-> http status 200Actual result
/index.php?option=com_content&view=article&id=841
-> http status 404/841-article-title
-> https status 200System information (as much as possible)
Shared web hosting, with domain connected to directory "with site separation".
(Provider:
home.pl
is one of the largest service providers in Poland.)Additional comments
I had no problem with reconfiguration the server, but it took me a long time to find the problem. (And a lot of stress)
If this problem cannot be quickly dealt (HTTP 404), I suggest add warning to installator, admin and site .
The text was updated successfully, but these errors were encountered: