Bug #94924
closed
Acces denied after updating from 9.5.28 to 9.5.30
0%
Description
After updating from TYPO3 9.5.28 to 9.5.30 I get the error access denied in frontend and backend.
I also get this error if I try to clear the cache via console. (ddev environment and ddev typo3cms cache:flush command)
Following packages were updated:
- Upgrading doctrine/annotations (1.13.1 => 1.13.2) - Upgrading enshrined/svg-sanitize (0.14.0 => 0.14.1) - Locking masterminds/html5 (2.7.5) - Upgrading nette/utils (v3.2.2 => v3.2.3) - Upgrading spooner/deployer-information (1.1.4 => 1.2.0) - Upgrading symfony/console (v4.4.27 => v4.4.29) - Upgrading symfony/http-foundation (v5.3.4 => v5.3.6) - Upgrading symfony/http-kernel (v4.4.28 => v4.4.29) - Upgrading symfony/polyfill-mbstring (v1.23.0 => v1.23.1) - Upgrading symfony/polyfill-php80 (v1.23.0 => v1.23.1) - Upgrading symfony/var-dumper (v5.3.4 => v5.3.6) - Upgrading symfony/yaml (v4.4.27 => v4.4.29) - Upgrading typo3/cms-about (v9.5.28 => v9.5.30) - Upgrading typo3/cms-adminpanel (v9.5.28 => v9.5.30) - Upgrading typo3/cms-backend (v9.5.28 => v9.5.30) - Upgrading typo3/cms-belog (v9.5.28 => v9.5.30) - Upgrading typo3/cms-beuser (v9.5.28 => v9.5.30) - Upgrading typo3/cms-core (v9.5.28 => v9.5.30) - Upgrading typo3/cms-extbase (v9.5.28 => v9.5.30) - Upgrading typo3/cms-extensionmanager (v9.5.28 => v9.5.30) - Upgrading typo3/cms-felogin (v9.5.28 => v9.5.30) - Upgrading typo3/cms-filelist (v9.5.28 => v9.5.30) - Upgrading typo3/cms-filemetadata (v9.5.28 => v9.5.30) - Upgrading typo3/cms-fluid (v9.5.28 => v9.5.30) - Upgrading typo3/cms-fluid-styled-content (v9.5.28 => v9.5.30) - Upgrading typo3/cms-form (v9.5.28 => v9.5.30) - Upgrading typo3/cms-frontend (v9.5.28 => v9.5.30) - Upgrading typo3/cms-impexp (v9.5.28 => v9.5.30) - Upgrading typo3/cms-info (v9.5.28 => v9.5.30) - Upgrading typo3/cms-install (v9.5.28 => v9.5.30) - Upgrading typo3/cms-linkvalidator (v9.5.28 => v9.5.30) - Upgrading typo3/cms-lowlevel (v9.5.28 => v9.5.30) - Upgrading typo3/cms-opendocs (v9.5.28 => v9.5.30) - Upgrading typo3/cms-recordlist (v9.5.28 => v9.5.30) - Upgrading typo3/cms-recycler (v9.5.28 => v9.5.30) - Upgrading typo3/cms-redirects (v9.5.28 => v9.5.30) - Upgrading typo3/cms-reports (v9.5.28 => v9.5.30) - Upgrading typo3/cms-rte-ckeditor (v9.5.28 => v9.5.30) - Upgrading typo3/cms-scheduler (v9.5.28 => v9.5.30) - Upgrading typo3/cms-seo (v9.5.28 => v9.5.30) - Upgrading typo3/cms-setup (v9.5.28 => v9.5.30) - Upgrading typo3/cms-sys-note (v9.5.28 => v9.5.30) - Upgrading typo3/cms-t3editor (v9.5.28 => v9.5.30) - Upgrading typo3/cms-tstemplate (v9.5.28 => v9.5.30) - Upgrading typo3/cms-viewpage (v9.5.28 => v9.5.30) - Locking typo3/html-sanitizer (v2.0.9) - Upgrading yoast-seo-for-typo3/yoast_seo (7.2.2 => 7.2.4)
For me it only effects TYPO3 9. I didn't test it on TYPO3 10 or 11.
Files
Updated by Philipp Kuhlmay over 3 years ago
It seems to be broken with the EXT:deployer_information version 1.2. With the version 1.1.4 it still worked.
Updated by Oliver Hader about 3 years ago
- Status changed from New to Needs Feedback
Shall we close this issue in case it is only related to EXT:deployer_information?
Updated by Philipp Kuhlmay about 3 years ago
Yes this can be closed. It was related to EXT:deployer_information which already fixed this issue.
Updated by Riccardo De Contardi about 3 years ago
- Status changed from Needs Feedback to Closed
@Philipp Kuhlmay thank you for your feedback.
Closed in agreement with the reporter;
if you think that this is the wrong decision or experience the issue again, please reopen it or open a new issue with a reference to this one.