Based on the error logs and the behavior you’ve described, the issue with the WordPress post not updating properly and causing a 500 internal server error seems to be related to a function in your theme or a plugin that is interacting with the content, particularly images. Here’s a breakdown of what the logs suggest … Read more
WordPress tells PHP, using ini_set(), in wp_debug_mode() which errors should be handled and which file they should be written to. The function is called in wp-settings.php when WP is starting up. As suggested by David in How to catch all PHP errors with custom error handler? answers you could use PHP’s set_error_handler() to define a … Read more
Pretty simple. comments.php is trying to call a function twentyseventeen_get_svg() which doesn’t exist: Uncaught Error: Call to undefined function You’ll probably need to contact the theme developer or, just find the part of the code in comments.php (line 88) that calls the function and comment it out. Looks like that function comes with the theme … Read more
Most likely this problem is caused by a plugin calling wp_die too early. For instance, if a plugin would decide something is wrong at the init stage and call wp_die then, the query would not have been set yet, resulting in this error (see the action reference for the order in which things happen). You … Read more
If you are using cPanel this may be triggered by a ModSecurity rule that block uploaded files higher than the predefined limit they use. This is a very tricky error to spot since it’s only logged serverwise. Within this log: /usr/local/apache/logs/error_log Here is a cPanel tutorial which explains why it happens and how to override … Read more
The errors were generated because there was a plugin that forced sql modes to be used on the database that are actually “incompatible” with wordpress. The following code was sadly executed for every request… private function set_sql_mode() : void { // Make sure no sql modes can be blocked (By wordpress built-in incompatible modes) add_filter(‘incompatible_sql_modes’, … Read more
<? } else { } ?> This is your problem: PHP short opening tags were deprecated in PHP 7.4 and completely removed in 8.0, so while your old server may have had 8.2.18 installed it wasn’t using it to run the site (versions of PHP can exist side by side). Replace the <? with <?php … Read more
the site seems to be infected by malware: https://sitecheck.sucuri.net/results/https/webscraping.pro which could explain the issues you have; these guides should help you deal with malware removal: https://wordpress.org/support/article/faq-my-site-was-hacked/ https://sucuri.net/guides/how-to-clean-hacked-wordpress/
I found the source of the error, and I’ll post my solution here if some lost soul with the same problem happens to stumble upon this question. The culprit was a piece of JavaScript at the start of the page (some old piece of Google Tagmanager/Analytics that didn’t even work). I found it by making … Read more
If you are using WordPress 5.2 or newer, then the site should by default send a fatal error notification email to your admin email address. The email should have some sort of stack trace in it, which shows where the error occured. Then either login to the site using the recovery mode link found on … Read more