[#36105] - 2 issues in 404 pages: images are broken and content plugins are not triggered
- New
- Medium
- Build: 4.0-dev
- # 36105
Steps to reproduce the issue
Take a multilingual Joomla 4 website (maybe not related to multilingual, but all my sites are multilingual so I cannot tel :) )
Surf to a non existing page, like /en/test
For example, go to https://www.whatt.eu/en/test
Expected result
You should have a 404 page... with images that do appear and content plugins which are triggered
Actual result
- The images are not displayed (see logo in Menu position, but also the logo in the Footer). Example:
https://www.whatt.eu/images/woluweb/woluweb-light-nospace-mini.png
becomes
https://www.whatt.eu/**en**/images/**images**/woluweb/woluweb-light-nospace-mini.png - And the {yyyy} in the footer is not replaced by the current year (done "on the fly" for example with ReReplacer). So this suggests that Content Plugins are not triggered or something
System information (as much as possible)
J!4.0.4
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
Txs @brianteeman
I have tested UNsuccessfully.
See the result live: https://www.whatt.eu/en/test
Probably something else at hand here I am afraid (even the image in the footer is broken. It sound like a "redirection" of all resources URL, with the Language Code being added to the url of the image for example)
@woluweb for the logo please use
<img alt="Whatt logo" loading="lazy" src="/images/Whatt_WHITE.svg" width="149" height="73">
instead of
<img alt="Whatt logo" loading="lazy" src="images/Whatt_WHITE.svg" width="149" height="73">
so add / to the image path in the custom module
txs @wojsmol
actually, even when you manually add that / TinyMCE will remove it
(so of course here I for the sake of testing, I disabled TinyMCE, added the /, re-enabled TinyMCE. But you cannot expect end-users to disable editors constantly. The whole site works fine, only the error page breaks the images)
It's a bit of an egg <=> hen problem here. If you trigger plugins on error pages it will lead to an infinite redirect when a plugin itself is the reason for the 404. Also the "/" solution is no real solution as all pages installed in subfolders are broken. The only real fix is to fix the base path in Joomla! (was broken in 3.x and instead of fixed it was removed in 4.x)
It's a bit of an egg <=> hen problem here. If you trigger plugins on error pages it will lead to an infinite redirect when a plugin itself is the reason for the 404. Also the "/" solution is no real solution as all pages installed in subfolders are broken. The only real fix is to fix the base path in Joomla! (was broken in 3.x and instead of fixed it was removed in 4.x)
Txs @bembelimen Benjamin,
OK, the "good news" is: it is not "just me" :D
I have no clue of how to fix this, but it seems to me very annoying if indeed all 404 pages in Joomla are "natively broken" :)
If there is a PR I'll be happy to test
Hackwar
- | Labels |
Added:
bug
|
||
please test #36106 for the logo
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/36105.