[PAGES-292] Template availability is not working correctly due to field initialisation Created: 21/Apr/20  Updated: 22/Apr/20  Resolved: 22/Apr/20

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 6.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2020-04-21 at 12.09.03.png     PNG File Screenshot 2020-04-21 at 12.15.03.png    
Issue Links:
Relates
relates to PAGES-276 Name and Template are 'pre-filled' wh... Closed
causality
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:
Epic Link: Migrate apps to new UI framework

 Description   

Due to the initialisation of fields in "create page" dialog, template availability is not working correctly allowing users to create subpages of templates which shouldn't be available.

Steps to reproduce in travel demo:

  1. Create a template availability rule for pur template. For example, restricting its access to superuser roleĀ 
  2. Access admin central with an user other than superuser. For example Eric (Editor) and create a new page from the root: public users template is not available as configured in step 1
  3. Now create a new subpage from /travel/members/protected: public users template is selected by default as it is the parent's template, and therefore, it is possible to create a page with this template.

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