Project

General

Profile

Actions

Bug #95815

closed

page type "shortcut" does not work in rightrestricted structure

Added by Joe Jones over 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Pagetree
Target version:
-
Start date:
2021-10-29
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
11
PHP Version:
Tags:
fe-user rights management page type shortcut target
Complexity:
Is Regression:
Sprint Focus:

Description

Dear TYPO3-develoopers,

we found a problem as part of the rights restricted pages trees. The page type shortcut checks if the shortcut target exists and wheather it is accessable in the frontend. So it is quite reasonable, that it is not possible to tageting a page that is restricted, because someone without the proper rights would get an error.

But often, a whole subleveltree is restriked and accessable for the same FE-usergroup. It should be no problem, to allow a restricted target page if the restriction is the same than the shortcut page: Because averyone who can access the shortcut page would also access the target page.

In the earlier TYPO3-Version and even in TYPO3 11 it is not possible targeting a restricted page from a shortcut page with the same restriction. The shortcut type is therefore useless.

Solution: TYPO3 checks, if the settings of Usergroup Access Rights of shortcut page and target page is the same.


Files

issue_shortcut.jpg (46.5 KB) issue_shortcut.jpg Joe Jones, 2021-10-29 09:10
clipboard-202111011338-vjspo.png (26.1 KB) clipboard-202111011338-vjspo.png Joe Jones, 2021-11-01 12:38

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #60258: showAccessRestrictedPages with shortcuts to restricted pagesClosed2014-07-11

Actions
Related to TYPO3 Core - Bug #65118: showAccessRestrictedPages with shortcuts to restricted pages #2Closed2015-02-17

Actions
Actions #1

Updated by Georg Ringer over 2 years ago

  • Status changed from New to Needs Feedback

thanks for the report! the screenshot you attached is just about the backend.

What do you think about changing the warning into an information to inform editors that there might be a problem in resolving the link?

or does something in the frontend while resolving the shortcut doesn't work?

Actions #2

Updated by Joe Jones over 2 years ago

Georg Ringer wrote in #note-1:

thanks for the report! the screenshot you attached is just about the backend.

What do you think about changing the warning into an information to inform editors that there might be a problem in resolving the link?

or does something in the frontend while resolving the shortcut doesn't work?

Hallo Georg,

no, it's not ony this message: The frontend shows an error "Page Not Found - The page did not exist or was inaccessible. Reason: ID was not an accessible page" Also the page is missing in menues.

Thanks,
Martin

Actions #3

Updated by Riccardo De Contardi over 2 years ago

maybe these ones are related?

#65118

#60258 (if I am not wrong, this one contains a bit of discussion about this topic)

Actions #4

Updated by Benni Mack about 2 years ago

  • Related to Bug #60258: showAccessRestrictedPages with shortcuts to restricted pages added
Actions #5

Updated by Benni Mack about 2 years ago

  • Related to Bug #65118: showAccessRestrictedPages with shortcuts to restricted pages #2 added
Actions #6

Updated by Benni Mack about 2 years ago

Can you recheck with 11.5.5 if this is fixed, please?

Actions #7

Updated by Riccardo De Contardi over 1 year ago

  • Status changed from Needs Feedback to Closed

No feedback since the a very long time => closing this issue.

Also, related issues are marked as solved.

If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem, please reopen it or open a new issue with a reference to this one.

Thank you and best regards

Actions

Also available in: Atom PDF