Feature #55977
closed
Store func menu settings in LocalStorage
Added by Pascal Dürsteler over 10 years ago.
Updated over 1 year ago.
Category:
Backend User Interface
Description
While debugging and modifying a big pile of typoscript via the template module, I tried to open up a second browser window, so I could have the editor and the object browser open at the same time.
This didn't work as expected. When I changed something in the editor and then reloaded the TSOB, it jumped to "info/modify", because the last "operation" I did was in there.
I then thought that this may be tied to the browser session, so I fired up a second browser with the TSOB. This gave me the same unexpected behavior, though.
I think it should be possible to work this way without the need of a second user in a second browser.
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
- Translation missing: en.field_remaining_hours set to 0.0
I do get the intention.
We should put some thought into this, because the reason to store this data in the DB is that the intended behavior is that you log into TYPO3 from whatever browser on whatever machine and always get your latest view.
Do you have ideas on how we could keep this behavior but still solve your problem?
Of course you could just create another admin and log in with that one... but that's not really what I'd consider "awesome" ;-)
I get that you want to have the same view that you had when you "logged out", but: There is a "starting page" user setting which does this; Start in e.g. the page module. I know it's not exactly the same, as you may need one or two additional clicks to get there where you were the last time.
Personally, I think the gained benefit from being able to have multiple backend windows/tabs open with the same user is bigger than with the current implementation with one-user-only but more accurate "entry where you were the last time".
As you said: One user per window would be less than awesome ;-)
hmmmmm, no, not really.
As your report also describes, this applies to not only the module you last used, but also the submodule selected, user settings and so on.
Fixing this is rather tricky if not impossible (because of colliding interests)
- Status changed from Needs Feedback to New
Maybe add possibility to have multiple sessions per user.
- Tracker changed from Story to Feature
- Subject changed from Store func menu settings in the session rather than in the database to Store func menu settings in LocalStorage
changed the title to incorporate the solution.
- Status changed from New to Closed
I think this has been resolved with the backend routing approach.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by