[PAGES-280] DefaultValue does not work for page properties (new UI framework) Created: 26/Mar/20  Updated: 19/Aug/20  Resolved: 19/Aug/20

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

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2020-03-26 at 15.14.18.png     PNG File Screenshot 2020-03-26 at 15.14.59.png     PNG File rendering_62.png    
Issue Links:
Cloners
clones PAGES-61 DefaultValue does not work for page p... Closed
supersession
is superseded by MGNLUI-5325 Support defaultValue in fields of new... 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
Epic Link: Migrate apps to new UI framework

 Description   

A "defaultValue" property does not work in Page Dialogs: a field is not displayed with the same value assigned to property 'defaultValue' into the correspondent dialog field.

 

To reproduce:

  1. Create a new page with ‘travel home’
  2. Choose informational ‘cookie consent wording’
  3. Save page
  4. Try to open it
  5. Rendering error due to missing consent wording properties

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