Every few months my client says “custom form isn’t working” and tries to fix it - when the code just needs to be re-verified.
I’d like to turn off the code verification for that specific template since I don’t know when the salts expire and can’t pre-emptively fix it before the client gets to it.
This should probably be a bug report instead of a how to post.
Also see: WAIT: Code signature in Bricks expires every few days
1 Like
Adding my reply here from WAIT: Code signature in Bricks expires every few days
No changing the URL.
@GrowPlugins No one is changing the code - there’s no hacking either - I have an activity logger. It looks like it just expires. I’m estimating around 90 days - since last time it happened was right around end of Jan.
Also - this happens WITHOUT any other plugin/theme/WP updates. I update the site manually (no auto-updates) and haven’t done it in a while since it’s lightweight and only update plugins if there are critical updates. Our firewall is good. So this happened probably a month+ after my last manual update.
1 Like
Hi @aces,
WordPress salts don’t expire on their own. They only change if someone manually updates them in wp-config.php, if you migrate the site to a new server, or if a plugin or server process rotates them.
The reason your custom code’s signature becomes invalid is that the salts were changed. This invalidates any existing signatures, which is exactly how code signing is supposed to work, it’s protecting your site from accepting outdated or tampered code. This is not a bug, it’s working exactly as intended.
Instead of disabling code signatures, you should figure out why the salts are changing. It could be that your hosting provider is automatically rotating them (most providers don’t, but you never know). I recommend reaching out to your host to check.
For a full explanation of how code signatures work and why they matter, see: