[#29455] - Frontend redirect fails after the site is set as "offline
- Closed
- 14 May 2021
- Medium
- Build: 4.0-dev
- # 29455
Steps to reproduce the issue
After setup the frontend as "offline", the following url is not redirected to frontend offline page:
http://sitename.com/index.php/component/config/
Expected result
Site Offline page only.
Actual result
The website is showing the frontend template along with: the 403 error in content position, displaying modules like: Older Posts, Most read posts, and the main menu module.
System information (as much as possible)
Default Joomla 4.0.0 beta1 package with sample data installed.
Additional comments
joomla-cms-bot
- | Labels |
Added:
?
|
||
The test is made with the default template provided into the Joomla 4 beta package.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/29455.
We are not mind readers ;)
Without knowing the version I had to guess. Which is why you were asked to complete the questions in your report.
I can confirm this error
richard67
- | Status | New | ⇒ | Confirmed |
| Build | staging | ⇒ | 4.0-dev |
this should be closed if it cannot be replicated in almost a year
i've been always in favour of some kind of stale-bot....me unlucky
What was this if not a report of replication
sorry @brianteeman it was 1y ago..so
i hope was Ok to ask if it is still valid .. today or not ?
for the record i mean this bot https://github.com/marketplace/stale
Sorry - I obviously misread your post.
If the frontend if offline then direct URLs, that fail ACL checks, will of course generate a 403 Forbidden and not a 503 offline.
The same is true of the admin console.
The same is true of the admin console.
Kind of true.
SOME admin URLS will give a 403 Forbidden if not logged in - Example #33599
SOME admin URLS will show the login page, but NOT redirect you to a login URL (I was overruled on that decision years ago), and allow you to login, and the page refreshes to the same url you were on before.
I can replicate this reported issue - but I believe it is the expected behaviour at present.
The issue is that the 403 is displayed in content area and the modules are
working while the site is set as "offline" .
When the wire is set as "offline", all frontend URLs must be redirected to
offline page. Any content, displayed in modules, should be unavailable.
On Fri, 14 May 2021, 9:24 pm Phil E. Taylor, @.***>
wrote:
The same is true of the admin console.
Kind of true.
SOME admin URLS will give a 403 Forbidden if not logged in
SOME admin URLS will show the login page, but NOT redirect you to a login
URL (I was overruled on that decision years ago), and allow you to login,
and the page refreshes to the same url you were on before.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#29455 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF5MI4JHLDCUDPKO422SKH3TNVTEBANCNFSM4NV4T56A
.
ok that makes more sense for sure. Thanks for explaining.
| Status | Confirmed | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-05-14 20:45:00 |
| Closed_By | ⇒ | richard67 |
Could you please test with one of the default templates as it sounds like it could be a template issue to me