Actions
bug #6763
closedEditors do not ask for saving when closing the workbench
Start date:
Due date:
% Done:
100%
Estimated time:
Severity:
normal
Found in Version:
Description
If the specimen editor has unsaved changes and the Taxonomic Editor is closed there is no pop up asking if the user wants to save
Related issues
Updated by Andreas Müller over 5 years ago
- Target version changed from Release 4.9 to Release 4.10
Updated by Patrick Plitzner over 5 years ago
- Target version changed from Release 4.10 to Release 4.11
Yes, this still happens
Updated by Andreas Müller over 5 years ago
- Target version changed from Release 4.11 to Release 4.12
Updated by Patrick Plitzner over 5 years ago
- Subject changed from Specimen editor does not ask for saving when closing the workbench to Editors do not ask for saving when closing the workbench
generalized topic because it happens for all e4 migrated editors while we are still using the e3-e4-bridge.
Updated by Patrick Plitzner over 5 years ago
I added a check prior to closing the workbench where the user is asked to save the editors. Pressing "Cancel" will not stop the workbench from shutting down. This is only temporary as with full e4 migration the behavior is provided by the platform itself and works as expected.
Updated by Andreas Müller over 5 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
Updated by Patrick Plitzner over 5 years ago
- Target version changed from Release 4.12 to Release 4.13
Moving to next milestone. Will only be solved after full migration
Updated by Patrick Plitzner over 5 years ago
- Has duplicate bug #7112: Ask for saving dirty editors when closing Taxeditor added
Updated by Patrick Plitzner over 5 years ago
- Status changed from In Progress to Duplicate
duplicated by #7112
Updated by Andreas Müller over 5 years ago
- Target version changed from Release 4.13 to Release 4.12
Updated by Andreas Müller over 5 years ago
- Status changed from Duplicate to Closed
This was implemented as workaround as long as full e4 migration does not yet exist.
Actions