If you don't want to show a core, or contrib message to the end user, you now have to iterate $_SESSION['messages']
and search for the (translated, token replaced) string to unset it.
If a message has a unique key, you can easily override a message, or unset it.
function backdrop_set_message($message = NULL, $type = 'status', $repeat = TRUE, $message_key = FALSE) {
A simple unset($_SESSION['messages']['status']['unique_key'])
could remove the message, and $_SESSION['messages']['status']['unique_key'] = t('Something else');
changes it.
Recent comments
Hello @NumerousHats, I agree with your assessment. I am looking into this situation right now. The root of this problem is that Backdrop CMS is implemented on top of a "stack" of...
Update Core and Theme via Web interface
I just installed a Backdrop CMS site with version 1.27.0. I then used the user interface to download and update Backdrop CMS to 1.30.0. After starting the update process, and on the...
1.30.0 update.php generates incorrect link
I believe my permissions are set up correctly, as I can install modules from the UI. But for whatever reason, I can't update them. I will, however, double check against that documentation.
Update Core and Theme via Web interface