Review main Ready for review

97667[BUGFIX] Ignore stale page and folder state of other users

Simon Schaufelberger CR 0 V -1 Hard +366 −38 updated 11/15/26, 10:20

Commit message

The backend module state is stored in the browser per module and
restored when a module is opened, for example the last selected
page or folder. After switching to another backend user, that
state can point to a page or folder the current user has no access
to. Depending on the module, this resulted in a "You don't have
access to this page" exception or a "Missing folder permissions"
flash message.

The page fallback is now applied in BackendModuleValidator before
the inaccessible page triggers an exception: GET requests with an
explicit "id" are redirected (303) to the first page within the web
mounts of the user. POST requests and page IDs derived from "edit"
or "cmd" statements keep their original context.

The file list falls back to the root level folder of the first
browsable storage, which is the first folder within the file mounts
for non-admin users, and redirects GET requests accordingly. The
"Missing folder permissions" labels are marked as unused instead of
being removed, so they can be deleted in a later major version.

Test this change

Run a command in your clone of the TYPO3 Core. Then try what the change does and vote on Verified in Gerrit. How to review a patch

Check out patch set 1
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/67/97667/1 && git checkout FETCH_HEAD
Cherry-pick onto main
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/67/97667/1 && git cherry-pick FETCH_HEAD

Review

  • Code review CR 0 Needs a vote
  • Verified V -1 Blocked
    • Oli Bartsch -1
    • core-ci +1 CI

Merge conflicts 11

Issues 1

Files 10

Review log 23

  1. Simon Schaufelberger uploaded patch set 1 11/14/26, 21:21

  2. core-ci voted on patch set 1 V +1 11/14/26, 21:31 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/114491

  3. Oli Bartsch commented on patch set 1 V -1 11/15/26, 10:20

    Unresolved

    If a user requests a page without access, its correct to show a error. I'm against introducing such a magic fallback. I guess it might not be the best thing to store such info in the local storage. User changing in the same session is IMO totally.