[PAGES-71] Pages Detail-App: Missing & strange ActionBar behaviour with missing cms:page and/or cma:area directives Created: 12/Jan/16 Updated: 19/May/22 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Magnolia pages module |
| Component/s: | None |
| Affects Version/s: | 5.4.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Christian Ringele | Assignee: | Unassigned |
| Resolution: | Won't Do | 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
|
||||||||
| Date of First Response: | |||||||||
| Description |
| Comments |
| Comment by Mikaël Geljić [ 11/Apr/16 ] |
|
I expect that if you uncomment the area tag, without uncommenting the page tag, you should get a warning since If I exclude the correct cases, we're only left with the cases where templates do not have any cms tag at all:
Hope this helps |
| Comment by Christian Ringele [ 11/Apr/16 ] |
Why should I add a "cms:area" tag to non existing areas, which I don't want to use? If I get then a pop up, that would also not be beneficial. Out of my view, it leaves all the situations open as BUG or as WRONG POP UP. Imagine you start with a empty script and want to try out things, and in the end |
| Comment by Roman Kovařík [ 19/May/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
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, |