I installed Joomla, behind an NGinx server, using the recommended config file.
The install process worked as expected and the connection with the DB is working as expected.
The administrator module (ROOT_URL/administrator
) is working well and gives no error / warning.
however, loading the main site (ROOT_URL/index.php
), the login page looks like a pure HTML page and I have a lots of 404 error in the network panel.
Some of the js files also present in the administrator module seem to be found correctly and the http request have the right filename.
The erroneous ones all looks like this:
GET |
scheme | http
host | ROOT_URL (replaced)
filename | /mediasystemjsmessages.js
I would expect these request to contains slash between modules:
filename | /media/system/js/messages.js
Labels |
Added:
No Code Attached Yet
|
Labels |
Added:
Information Required
|
@CharlesGueunet Which Joomla version have you installed?
Ooops, it is the 4.3.2-1 (from the AUR) I have updated the main description accordingly. Thanks
@CharlesGueunet What is "AUR"?
It is simply the way I installed Joomla, it relies on this specific script which simply download the joomla archive and put it under /usr/share/webapps/joomla
and handle permission.
I can git clone on the same folder and this would give the same result.
@CharlesGueunet How shall a reader of this issue know this? That's why I had asked.
Labels |
Removed:
Information Required
|
I can try to spend some time debugging this, but I have no idea where to start. Can someone point me where these URI are built in the joomla codebase ?
Do you use an ".htaccess" file in the Joomla root folder or a parent folder of that folder? If so: What happens if you replace that by the "htaccess.txt" coming with Joomla, i.e. rename ".htaccess" to e.g. ".htaccess.bak" and then "htaccess.txt" to ".htaccess"?
From my understanding, .htaccess
is for Apache. I use the NGinx server with the config file recommended on the joomla website (more details are given on the description).
I still tried your suggestion, with no avail. No change in behavior.
I should add that when I inspect the dom, client side, I already have invalid uri, looking like this:
<link href="[/mediatemplatessitecassiopeiacssvendorjoomla-custom-elementsjoomla-alert.css?0.2.0](view-source:http://[hidden]/mediatemplatessitecassiopeiacssvendorjoomla-custom-elementsjoomla-alert.css?0.2.0)" rel="stylesheet" data-asset-name="webcomponent.joomla-alert" />
I do not think the NGinx engine is involved in writting the URI like that, and I assume it is already invalid, but I am not sure about this.
Ah sorry, I forgot it was NGinx.
I continue my investigations.
Seems like in WebAssetItem.php :: resolvPath
, $file
contains the "/" before the call to HTMLHelper::_
and none after:
Exemple
before: plg_system_debug/debug.min.js
after: mediaplg_system_debugjsdebug.js
I will try to understand how the HTMLHelper
works, seems like it is not an easy one.
It uses HTMLHelper::_('script', $path)
or HTMLHelper::_('stylesheet', $path)
to get a final path.
Wich by default implemented in HTMLHelper::script()
and HTMLHelper::stylesheet()
, but also can be overiden by any plugin.
Labels |
Added:
bug
|
Is this still an issue?
Is this still an issue?
I do not know, I have installed joomla on another distribution and as it worked I removed this one. If I had a penny to bet, I would say the issue was due to the communication with the database that somehow stripped the string from some special character, but I am not a php / web specialist.
I think we can close this.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2024-03-28 08:14:04 |
Closed_By | ⇒ | Hackwar |
thanks. Closing.
@CharlesGueunet Which Joomla version have you installed?