[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: |
|
||||||||||||||||
| 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.
|
| 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. |