Bug #16769
closedUnaccessible page redirects to an other in rootline without transmission of pid
0%
Description
The following is from http://wiki.typo3.org/index.php/Newloginbox/Wishlist:
- If a page is not accessible because of frontend-user-rights, the rootline is searched upwards for the first accessible page.
- The original requested page-id is stored but not communicated to the new page.
In detail:
- A visitor is requesting an access-restricted page.
- index.php calls typo3/sysext/cms/tslib/index_ts.php
- On the lines 319+331 of index_ts.php determineId() is called
- determineId() calls fetch_the_id() (750,770,784 in class.tslib_fe.php)
- fetch_the_id() now stores on line 872 (same class) the original requested id in a local variable $requestedId which is not used anymore further.
- on line 873 an accessible page is searched: getPageAndRootLineWithDomain() > getPageAndRootLine() on lines 912ff.
If the requested page-id is not accessible with the current user-rights the rootline is being searched upwards until an accessible page is found and the requested page-id is overwritten with that page. - As far as I see the page that is effectively called does not "know" about the original requested page - which does not make sense in every case, i.e. the requested page is a shortcut. The only hint is the http_referrer which IMHO isn't useful for this situation
It would be nice if a patch can be created for T3 4 ++ and made available as an extension or as part of a bugfix version.
This is important for the use of ext newloginbox
(issue imported from #M4619)
Updated by Martin Kutschker almost 18 years ago
Why do you need the value and where do want the page "to know the value"? eg instead of a local variable a property of $TSFE could be used.
So any script may read $TSFE->id and have a look at $TSFE->requestedId.
Updated by Andreas Balzer almost 18 years ago
As I'm no developer of newloginbox I don't know where this should be integrated. It would just be nice, if an extension can read that value and work with it.. So I guess it's up to your choice.
Updated by Alexander Opitz over 11 years ago
- Category deleted (
Communication) - Status changed from New to Needs Feedback
- Target version deleted (
0) - PHP Version deleted (
4)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
No feedback for over 90 days.