Automatically clearing errors from the dashboard when they no longer exist is the expected behavior by most users. As it stands now, they have to be cleared manually. Seems to me this should be an easy fix/improvement.
1 Like
It’s not a new issue with v17. It’s been like this for a long time. I don’t understand why such an obvious thing needs an issue tracker in the first place, unless nobody cares about trying to improve FPBX anymore.
+1
It would be a nice improvement!
The notifications are suppose to be “auto-healing” if a condition changes the notification should clear. Thar is how much of it is written. I would file tickets against any specific notification that is not doing this. For example in weakpasswords
// Remove all weak password notifications
$nt = notifications::create($db);
$security_notifications = $nt->list_security();
foreach($security_notifications as $notification) {
if($notification['module'] == "weakpasswords") {
$nt->delete($notification['module'],$notification['id']);
}
}
It goes through and kills all of its own notifications then will add back valid ones…
1 Like
If they did go away on their own at one time they certainly don’t now.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.