Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I just ran into this issue while working on a module that creates its own fields.
I was testing the module by adding new fields through the fields ui but the fields were not being saved. I couldn't figure out why until I realized that an error message was being output but it was being added to the "message okay" box instead of the "message error" box.
It looks like the errors being output through drupal_set_message should have a $type property added.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | without patch.PNG | 43.24 KB | devin carlson |
| #1 | with patch.PNG | 44.74 KB | devin carlson |
| #2 | change-message-type-to-error-1308994-2.patch | 1.29 KB | devin carlson |
Comments
Comment #1
devin carlson commentedScreenshots of what the errors look like currently and when set as warnings.
Comment #2
devin carlson commentedAnd a patch to add a type of 'error' to the messages I encountered.
Comment #3
droplet commentedComment #4
yoroy commentedGood catch, thanks for the screenshots.
Comment #5
dries commentedCommitted to 7.x and 8.x. Nice catch.