Bug #86398

Interface state can't be saved

Added by David Bruchmann 12 months ago. Updated 13 days ago.

Status:
Needs Feedback
Priority:
Must have
Assignee:
-
Category:
Backend User Interface
Start date:
2018-09-27
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

The current pagetree always is showing up toggled and I've to open again.
In sys_log I find the following error many times:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: Cannot use object of type stdClass as array | Error thrown in file /typo3/sysext/backend/Classes/Configuration/BackendUserConfiguration.php in line 178. Requested URL: https://www.domain.com/typo3/index.php?route=%%2Fajax%%2Fusersettings%%2Fprocess&token=--AnonymizedToken--

composer.json (1.23 KB) David Bruchmann, 2018-09-27 12:09

History

#1 Updated by Andreas Fernandez 12 months ago

  • Status changed from New to Needs Feedback

I can't reproduce this issue in current master. Do you have any 3rd party extension installed?

#2 Updated by David Bruchmann 12 months ago

Yes, this is from composer.json:


    "require": {
        "in2code/powermail": "^6.1",
        "causal/image_autoresize": "dev-master",
        "svewap/ws-flexslider": "dev-master",
        "wdb/secure-downloads": "dev-master",
        "helhum/typo3-console": "^5.5.4",
        "typo3/minimal": "^9.4",
        "typo3/cms-about": "^9.4",
        "typo3/cms-adminpanel": "^9.4",
        "typo3/cms-belog": "^9.4",
        "typo3/cms-beuser": "^9.4",
        "typo3/cms-felogin": "^9.4",
        "typo3/cms-fluid-styled-content": "^9.4",
        "typo3/cms-form": "^9.4",
        "typo3/cms-impexp": "^9.4",
        "typo3/cms-info": "^9.4",
        "typo3/cms-redirects": "^9.4",
        "typo3/cms-reports": "^9.4",
        "typo3/cms-rte-ckeditor": "^9.4",
        "typo3/cms-seo": "^9.4",
        "typo3/cms-sys-note": "^9.4",
        "typo3/cms-t3editor": "^9.4",
        "typo3/cms-tstemplate": "^9.4",
        "typo3/cms-viewpage": "^9.4",
        "typo3/cms-lowlevel": "^9.4" 
    },

If it helps to reproduce, all BE-users get the uid in BE-shown.
I can't see that it has any impact though, I disabled it and same behavior.

options {
  pageTree.showPageIdWithTitle = 1
}

#3 Updated by David Bruchmann 12 months ago

#4 Updated by Michael Dittberner 11 months ago

I had the same error. It seems to occur when upgrading an old TYPO3 installation to 9.5. It was concerning only existing users - new users didn't have this problem. I suppose the reason is in the structure of the serialized array in be_users.uc. There might have been some structural changes.

My solution was quite simple: User Settings -> Edit and Advanced functions -> Reset user settings to default state.
Then the user config data is written new and the system can use it.

Maybe there coud be provided an upgrade wizard for this...

#5 Updated by Georg Dümmler 7 months ago

Same Error here after upgrade from TYPO3 6.1 up to 9.5.4.

#6 Updated by Ingo Fabbri 7 months ago

Michael Dittberner wrote:

I had the same error. It seems to occur when upgrading an old TYPO3 installation to 9.5. It was concerning only existing users - new users didn't have this problem. I suppose the reason is in the structure of the serialized array in be_users.uc. There might have been some structural changes.

My solution was quite simple: User Settings -> Edit and Advanced functions -> Reset user settings to default state.
Then the user config data is written new and the system can use it.

Maybe there coud be provided an upgrade wizard for this...

Reset the user settings did the job. Thanks for the hint!

#7 Updated by Sven Juergens 6 months ago

Michael Dittberner wrote:

I had the same error. It seems to occur when upgrading an old TYPO3 installation to 9.5. It was concerning only existing users - new users didn't have this problem. I suppose the reason is in the structure of the serialized array in be_users.uc. There might have been some structural changes.

My solution was quite simple: User Settings -> Edit and Advanced functions -> Reset user settings to default state.
Then the user config data is written new and the system can use it.

Maybe there coud be provided an upgrade wizard for this...

Same Problem here :) Thanks for the hint!

To reset all users at once, you can use the option "Maintenance" -> "Reset Backend User Preferences" as admin

#8 Updated by Benni Mack 5 months ago

  • Target version changed from next-patchlevel to Candidate for patchlevel

#9 Updated by Johannes Hollmann 13 days ago

I had the same error on backend login with existing user.

My solution was to create a new admin user over cli and use them to reset all backend user preferences like Sven Juergen wrote above.

Also available in: Atom PDF