You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following PR (#12125) wraps the {attribute} part of all validation error messages with asterisks *{attribute}*, representing an <em> tag when parsed as markdown.
As I understand it this is an enhancement for the CP and the new error summary stuff.
It maybe just us, but this is not the correct behavior for the front end, where we would now need to include a markdown parser to handle / display any validation error messages that contain markdown.
Ideally messages for our front end would not be modified, not sure if this is configurable or might require a change or setting, but either way I have been unable to find docs or details on the change anywhere.
Craft CMS version
4.5.3
PHP version
8.2.*
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered:
What happened?
Description
The following PR (#12125) wraps the
{attribute}
part of all validation error messages with asterisks*{attribute}*
, representing an<em>
tag when parsed as markdown.As I understand it this is an enhancement for the CP and the new error summary stuff.
It maybe just us, but this is not the correct behavior for the front end, where we would now need to include a markdown parser to handle / display any validation error messages that contain markdown.
Ideally messages for our front end would not be modified, not sure if this is configurable or might require a change or setting, but either way I have been unable to find docs or details on the change anywhere.
Craft CMS version
4.5.3
PHP version
8.2.*
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered: