At least for now i’ve restricted it to the dashboard page
// disable annoying notices on all admin pages except dashboard
add_action( 'in_admin_header', function () {
$current_screen = get_current_screen();
if( $current_screen->id != 'dashboard' ) {
remove_all_actions( 'admin_notices' );
remove_all_actions( 'all_admin_notices' );
}
}, 20 );
@curtisfraser This isn’t true. If you simply dismiss the notice we store an option to hide it forever. No need for extra code. We utilize the “Persist Admin notice Dismissals” library do so: https://github.com/w3guy/persist-admin-notices-dismissal
Unfortunately Caddy Admin upsale message does not ‘simply dismiss’ message.
Many plugins utilize persisting the dismissal of admin notices, which is very nice indeed. Unfortunately Caddy’s method does not work on this site with its Security Headers. I have not come across any other plugins with the same issue as yet, but my code snippet will help with those too.
In case you are wondering what security header is being used:
Header set Referrer-Policy: strict-origin-when-cross-origin
Clicking the ‘X’ in Caddy admin message receives: 403 Forbidden, strict-origin-when-cross-origin
Hi @curtisfraser
Thanks for taking the time to leave feedback, though I wanted to clarify a few things:
We’ve tested the issue you described with the same security headers (along with others) but haven’t been able to reproduce it. It closes fine without any errors for us. We also haven’t seen this happen on other customer sites nor has any other customer reported it. It looks like this may be related to something specific in your setup.
Had you reached out to us directly, we would’ve been more than happy to take a look and get it resolved for you quickly. We’re always responsive and eager to help, especially with unique configurations.
We totally understand frustration when things don’t work as expected, but a negative review without giving us a chance to help feels a bit premature, especially since this doesn’t reflect the experience most users have with Caddy.
If you’re open to it, we’d still love to help get to the bottom of it.
Please reach out to success [at] usecaddy.com
I realize now that there is a contact support now within your plugin. Next time i find an issue I’ll be sure to use that.
The issue occurs in our production Linux environment with the header:
Header set Referrer-Policy: strict-origin-when-cross-origin
It also occurs in our Windows test and dev environments with header:
add name=”Referrer-Policy” value=”strict-origin-when-cross-origin”
I am surprised others have not had this issue, since it is failing in three different environments.
The only options I see are to either remove the security setting so we can get this message to disappear forever, or use the work around I put in place. Either way, it is resolved on our end right now. It was really bothering the authors, editors working on the site.
