Run Simultaneous Worlds on Tekkit Lite, Voltz, Etc.Install Dynmap, a Web-Based Dynamic Map.Install CraftBukkit Plugins on a Modded Minecraft Server (Tekkit, Hexxit, Feed the Beast, etc.).Install CraftBukkit Plugins on a Minecraft and Tekkit Classic Server.Upload a World to Your Minecraft Server.Setup a Whitelist for your Minecraft Server.Agree to the EULA on a Minecraft Server.Keep following us for more WordPress tips. Thank you for reading this WordPress tutorial explaining how to read error logs. I hope this work was helpful for you to solve any inconvenience with your WordPress site. If you have access to your server, you can use the methods explained in this tutorial, or other methods like SSH as explained in the introduction of this article. Knowing how to enable the debugging mode to read logs is mandatory for any WordPress administrator in order to afford possible unknown problems. ConclusionĪs shown in this tutorial, enabling and reading WordPress error logs is easy as long as you have access to your hosting files. Now the debugging mode is enabled, and you can check the debug.log file under the wp-content directory to read WordPress error logs. Overwrite the existing wp-config.php file. Then, upload the modified file to your site root directory. Once downloaded, almost at the end of the file, find the line containing the following: Right click the file wp-config.php and download it. If a certificate approval request shows up as shown in the following image, press the OK button.Įnter into the public_html directory, the root directory of your website. Note: In this tutorial, I’m using the Filezilla FTP client. If you are using an FTP client and want to enable error logs in WordPress, connect to your hosting, as shown below. In my case, the errors are reporting an old PHP version. Of course, in many cases, the user won’t understand the log information, but it is great data you can use to realise the specific cause of an error using a search engine, just copy paste last lines related to your issue. Note: Some plugins like Wordfence will prevent the debug.log file from being created, you need to disable it until you finish the debugging process.Īll error logs will be saved in your debug.log or error_log files depending on what file is created in your case. If you still want the debug.log file to be created instead of the error_log file, you can rename it and the debug.log file will be created.
In some cases, users reported the debug.log file wasn’t created, but they found a file named error_log within their root directory. Define ( 'WP_DEBUG_DISPLAY', false ) ini_set ( 'display_errors', 0 ) Īfter pasting that code, you can find a new file named debug.log located within the wp-content subfolder in your hosting.
0 kommentar(er)
