[CONTEDIT-95] Prompt after save & close when content is not changed Created: 05/Apr/17  Updated: 04/Apr/23  Resolved: 04/Apr/23

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: 1.0
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Marcel Boer Assignee: Unassigned
Resolution: Obsolete Votes: 4
Labels: later
Remaining Estimate: 0.05h
Time Spent: Not Specified
Original Estimate: 0.05h

Attachments: PNG File close_editor.png    
Issue Links:
causality
dependency
depends upon CONTEDIT-75 Provide extensive support for Undo/Re... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: AuthorX Support
Team: AuthorX

 Description   

If you save and then close an article, you still get this prompt. That should be unnecessary?

Also clicking on "x" in the Tab of the App, no confirmation message shown.



 Comments   
Comment by Marcel Boer [ 05/Apr/17 ]

From Jan Haderka: Currently we do not re-validate input against repository, but save (or not) blindly. We could implement observation of the content and try to track changes being made since last save to ensure there are none, but it is none trivial task with all the separate components and as such would take while to develop. Personally I would not prioritize this over other improvements that we have on the list currently, however we might be able to tackle that rather easily once we deal with CONTEDIT-75

Comment by Laura Delnevo [ 04/Apr/23 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 00:17:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.