[MGNLUI-3855] RichTextField required property not functioning properly Created: 21/Apr/16  Updated: 27/Jul/16  Resolved: 28/Apr/16

Status: Closed
Project: Magnolia UI
Component/s: widgets
Affects Version/s: 5.4.5
Fix Version/s: 5.4.6

Type: Bug Priority: Neutral
Reporter: Federico Grilli Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
duplicate
is duplicated by MAGNOLIA-6506 Rich text field does not show require... 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
Date of First Response:

 Description   

If i set to required: true, the "*" does not appear in the label.

If the richtextfield is required: true, and if other field in the form failed the validation, this richtextfield, even if it has value, will show error. This only happens when you are creating the data. Updating the data will not encounter this issue.

As reported by a user on our forum https://forum.magnolia-cms.com/forum/thread.html?threadId=8c6c0b0f-380d-4e91-be56-c7528856b5f6 and verified personally by yours truly.



 Comments   
Comment by Richard Gange [ 22/Apr/16 ]

jenny_87 I've update the ticket to include both the issues you pointed you. Thanks for letting us know.

Comment by Jennylyn Sze [ 28/Apr/16 ]

I updated today to 5.4.6, the two issues are both fixed already.
I'm able to see the "*" if the richtextfield is mandatory.
There's also no more validation issue when the richtextfield is mandatory and other validators failed.

It's weird though, I didnt see this in the release changes for 5.4.6 haha! But I'm happy that it's fix already, no need for me to wait for the next release

Thanks!

Comment by Federico Grilli [ 28/Apr/16 ]

Good to know! Evidently I tested it against 5.4.5

Generated at Mon Feb 12 09:10:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.