Project

General

Profile

Actions

Bug #31065

closed

Adminpanel option "simulate usergroup" affects FE pages where admin panel is not active

Added by Björn Pedersen about 13 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-10-18
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

If the "simulate usergroup" feature of the admin panel is used, all FE pages are affected.
Even pages where the admin panel is not active/shown because the user does not have edit access
are affected.

The admin panel settings should only be active on pages where it is activated.

Actions #1

Updated by Björn Pedersen about 13 years ago

How to reproduce:

page 1: BE user has edit access, admin panel is shown

page 2 in an unrelated tree: BE user does not have BE access, a FE group restriction is in effect.

Selecting a FE group to simulate on page1, that is different from page 2 allowed groups will hide page 2

Actions #2

Updated by Steffen Ritter about 13 years ago

  • Complexity set to medium

Hi Björn,
did this behaviour change in comparison to 4.5, or why did you it especially address for 4.6.

Anyways I do not consider this as a 4.6 blocker and could be tackled later on.

Actions #3

Updated by Björn Pedersen about 13 years ago

I did not check it for earlier versions. But I guess this could alos be present in 4.5

And I agree that this is something with target 4.7.

Actions #4

Updated by Alexander Opitz almost 10 years ago

  • Status changed from New to Needs Feedback
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.7)?

Actions #5

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF