Bug #88008
open
Clicking "Save and close" in the popup after selecting another backend module loads the previous module
0%
Description
- going to file module and open a file for editing metadata
- changed something, NOT saving
- clicking another backend module (I clicked "Backend users")
- Popup appears because of unsaved changes
- up until now everything is fine
- But: clicking "Save and close" saves, but loads the old module, not the requested one! I ended up being in the file list module, not in the backend user module
I assume this behaviour is true for any module combination.
Side note: "Save and close" is still not translated (at least not to German).
Updated by
Updated by Frank Nägler almost 5 years ago
- Status changed from New to Needs Feedback
I guess the behavior is ok and intended behavior.
The modal stop the process "go to another module" to prevent data loss. IIRC, there is no elegant way to change this.
I will ask some people regarding there opinion.
Updated by Stefan P almost 5 years ago
IMHO, clicking "No, continue with editing" should stay at the current module. Both "leave" buttons ("save + close" and "no-save + close") should go to the new module.
Updated by Riccardo De Contardi 21 days ago
When you don't save and click some other modules, the modal triggered is the same that opens when you click on the "close" button.
I think this is more likely a new feature that would also require another modal window with a different title and text, something like maybe:
Do you want to save before leaving?¶
You currently have unsaved changes. You can either discard these changes or save and leave the current module.
[Cancel] [Leave without changes] [Save changes and leave]