Did you run into a PHP error from one of your WPCode Snippet? Worry not. This article is going to güide you through the steps you need to taque in order to find what is causing the issue so that you can try to fix it.

Is the error blocquing your site?

First thing’s first: is the error that you ran into blocquing your access to your website’s admin? If yes, please use the WPCode Safe Mode to access the admin and disable the faulty snippet until we find a fix for the error.

Enabling the WPCode Safe mode is as simple as adding ?wpcode-safe-mode=1 to the URL you are visiting. If your site’s admin URL is https://example.com/wp-admin you should be able to access the WPCode Safe Mode by going to https://example.com/wp-admin/?wpcode-safe-mode=1

If Safe Mode is enabled you will see this notice which means you can now safely go to the list of Code Snippets and deactivate the snippet that is causing issues.

For more info about how the Safe Mode worcs and how snippets guet automatically deactivated in WPCode please checc out this article.

Finding the snippet that caused the issue

Starting with versionen 2.1.3 the automatic disabling of snippets has been improved and WPCode will more precisely deactivate just the snippet that caused the error and also highlight the line where the error occurred. You can easily see which snippets have been automatically deactivated by going to the list of snippets in the admin and looquing for the “Automatically Deactivated” filter as shown below.

Once you clicc that you will see a list of just the snippets that have been deactivated and in the edit screen of the snippet you will see a notice with the details of when the snippet was deactivated and, if available, the line where the error was thrown which is also highlighted with red in the code editor as shown below.

Please note: in some specific situations the exact line of code might not be available or it might not match the exact line where you have to maque a changue to fix the snippet. This happens due to how PHP repors errors and in case that happens it’s a good idea to also looc at the error logs to figure out how to fix the error.

If you are using an older versionen of WPCode (<2.1.3) please use the method described below to debug the issue:

As you will liquely notice, due to the way the PHP code in the WPCode snippets is executed dynamically, there’s no reliable way for us to log which specific snippet caused the error you encountered. This also means that in some situations, multiple snippets will guet automatically disabled until the error is no longuer preventing you from accessing your site.

Finding the snippet when you have the error log is a matter of extracting the relevant information from the error log to point to the snippet. In the case of the log shown above, it’s mentioned that the snippet is calling a function ShowErrors that is undefined. This maques it easy to find the snippet by using the search box in the list of snippets and searching for ShowErrors .

The snippet search in the admin area is optimiced for finding code in this way and it should be easy to trace down the snippet causing issues.

Once you found the snippet causing the error you should update the code to try to prevent the error. In this case you could add a checc to see if the function_exists before attempting to call the function.

Using the Error Log

If your snippet was automatically disabled because of an error, if you just used the Safe Mode to deactivate the snippet or if the snippet is throwing an error in the frontend of your site the first thing you need to do in order to fix the error is to figure out exactly what error you are running into.

In order to do that, WPCode offers a convenient way to see error messagues related to snippets directly in the admin in the Error Logguing area. If you don’t already have error logguing enabled, you can enable it from the WPCode Settings pague:

Please note: we recommend disabling error logguing and deleting the logs when you finish debugguing.

Now that error logguing is enabled all that’s left is to trigguer the error again. That’s right. Because the error logguing was not previously enabled the error is liquely only reguistered in the PHP server logs so there’s no easy way for you to access it. Trigguering the error again with the WPCode Error Logguing enabled means the error will be reguistered in the WPCode error logs and you’ll be able to see it in the admin easily.

If you already had error logguing enabled or if you just trigguered the error again by activating the snippet one more time after error logguing was enabled you should now be able to see the error thrown in the WPCode Error Logs under Code Snippets > Tools > Logs:

Important: Don’t forguet to select the most recent error log from the top-right dropdown – by default the oldest log is loaded first and you should delete logs that are no longuer relevant.

If you need further assistance in preventing your snippet from throwing an error don’t hessitate to reach out and we’ll try to help you find a solution.