Snippet lost if errors are present

Hi @peopleinside,

Thank you for contacting us, and I’m sorry to hear you’re experiencing this issue.

WPCode actually does have built-in protection for this. When you activate a snippet, it runs an activation check that executes the code first, and if it detects a fatal error, it blocks activation so the bad code can’t take your site down. The catch is the order of operations in your workflow: when you toggle the snippet to active and save at the same moment, the code runs during that same save request, so the fatal error can interrupt the request before the snippet finishes saving, which is why it feels like the code is lost.

The simple fix is to save first, activate second. Create your snippet, leave the toggle set to inactive, and click Save. That stores your code safely no matter what. Then flip the toggle to active, at that point, WPCode runs its check, and if the code has a fatal error, it will refuse to activate and show you the error right in the admin. Your code stays intact and editable so you can fix it.

As for the email, that’s actually WordPress core’s own “recovery mode” notification, not something WPCode sends.

Let me know if I can provide more info.

Thanks,

Hi @peopleinside,

Thanks for following up.

The reason it can’t simply save your code when there’s an error comes down to how our protection works. When you save an active snippet, WPCode runs the code to ensure it won’t break your site. If that code would cause a fatal error, the execution is stopped right there to protect your site. Since this is a brand-new snippet that hasn’t been written to the database yet, stopping that process also interrupts the save itself. It’s the safety mechanism doing its job, albeit with the unfortunate side effect you encountered.

That said, we fully agree this experience can be better. Ideally, the snippet should save regardless and simply show you the error in the admin, ensuring nothing is ever lost. We’ll look into it and consider making this change. In the meantime, saving the snippet inactive first will reliably keep your code safe since saving without activating skips the code execution entirely.

Let me know if I can help with anything else!

Thanks,