[MAGNOLIA-2690] Renaming content causes bogus deactivation message to appear. Created: 15/Apr/09  Updated: 23/Jan/13  Resolved: 17/Apr/09

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 4.0.1, 3.6.5
Fix Version/s: 4.1, 3.6.6, 4.0.2

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
relation
is related to MAGNOLIA-2527 Moved pages should not have a green icon Closed
is related to MAGNOLIA-2173 Moving / rename a page on author sho... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

After renaming activated content in admin interface, the message box appears saying that this action will cause deactivation of the content. After confirming the message, content status is turned to amber (i.e. modified) and content is not deactivated.
Steps to reproduce:

  • login to admin interface
  • create piece of content
  • activate the content
  • rename the content
    ... after renaming the content message box will appear asking for confirmation of the change and notifying user that content will be deactivated. However after confirmation of the message, content is not deactivated. It's status is changed to "modified". The message is wrong and should not appear since fixing MAGNOLIA-2173 & MAGNOLIA-2527


 Comments   
Comment by Jan Haderka [ 17/Apr/09 ]

Fixed as of r24363 in trunk, r24421 on 4.0 branch and r24417 on 3.6 branch.

Generated at Mon Feb 12 03:39:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.