[MGNLUI-7625] Pages app should change page status to unpublished/modified after importing Created: 25/Mar/21 Updated: 05/Jan/23 |
|
| Status: | Open |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2.26 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Canh Nguyen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| 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: |
[X]*
Steps to reproduce, expected, and actual results filled
[X]*
Affected version filled
|
||||
| Date of First Response: | |||||
| Epic Link: | AuthorX Support | ||||
| Team: | |||||
| Description |
| Comments |
| Comment by Paulina Jagielka [ 21/Jan/22 ] |
|
Hi All, Coul you please let us know what is the plan for fixing this issue ? In which update we can expect it ? Br Paulina |
| Comment by David Martin [ 16/Nov/22 ] |
|
It also affects Assets. I'd argue it's more serious than a minor bug. I encountered it here - https://jira.magnolia-cms.com/servicedesk/customer/portal/6/HELPDESK-3440 In Paas Magnolia Publish including Sub nodes is set to only publish modified subnodes only. So if you publish an imported node and it's subnodes - it doesn't do anything. The subnodes appear to have the status of published, so it doesn't publish them. There's no error message displayed or any indication of the problem. The workaround is pretty simple but wildly unintuitive, Unpublish the parent node
There's a simpler way to replicate the problem
|