Upgrade to Pro Crashed Site
JamminSam.com is Hosted with SiteGround.com
PHP 7.1
WordPress v5.0.2
Sucuri Security v2.3
Admin Columns 3.3.1
Advanced Custom Fields 5.7.9
Just purchased and attempted to install Admin Columns Pro v4.4.1
but generated errors (I captured the errors) and the site crashed.
So I restored from backup. Site working as before install.
Here are the errors:
:::::::::::::::::::::::::::::::::::::::::::::::
Fatal Error (hide details) (remove)
The site encountered a problem that it cannot recover from. Please use the following information to try to resolve the problem.
Error Message
Fatal Error: Uncaught Error: Call to undefined function mysql_real_escape_string() in /home/jamminsa/public_html/wp-content/plugins/sucuri-wp-plugin/lib/hooks.php:276 Stack trace: #0 /home/jamminsa/public_html/wp-includes/class-wp-hook.php(286): sucuri_events_without_actions(”) #1 /home/jamminsa/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #2 /home/jamminsa/public_html/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #3 /home/jamminsa/public_html/wp-admin/admin.php(156): do_action(‘admin_init’) #4 /home/jamminsa/public_html/wp-admin/plugins.php(10): require_once(‘/home/jamminsa/…’) #5 {main} thrown in /home/jamminsa/public_html/wp-content/plugins/sucuri-wp-plugin/lib/hooks.php on line 276
Description
The Sucuri Security plugin code created an error that caused PHP execution to fail.
The code tried to run a function that doesn’t exist (mysql_real_escape_string()). This type of error is typically caused by a simple typo (is_hom() rather than is_home()), by calling a function provided by a plugin when that plugin is not activated, by calling a function before it is ready (such as calling a function before the code that creates it has run), or by using a function that no longer exists (the function may have been removed from WordPress core or the plugin/theme that previously supplied it).
Solutions
Invalid code modifications can cause this problem. If you have made any modifications to the plugin, remove them and try to load the site again.
It is possible that this plugin’s code is out of date and that an upgrade is available. Check with the plugin’s author to see if an upgrade is available.
There may be a conflict with another plugin running on the site. Try upgrading the other plugins on the site. A plugin conflict can be ruled out by deactivating all the other active plugins on the site and checking to see if the error still occurs.
The Sucuri Security plugin may not have been fully uploaded. Uploading the plugin again could fix the issue. Important: If you do this, you will lose any modifications made to the plugin.
Error Source Details
Type Plugin
Name Sucuri Security
Version 2.3
Author sucuri.net
Path /home/jamminsa/public_html/wp-content/plugins/sucuri-wp-plugin
File lib/hooks.php
Other Software Details
WordPress Version 5.0.2
PHP Version 7.1.25
Full Error Details
Type Fatal Error (E_ERROR)
Message Uncaught Error: Call to undefined function mysql_real_escape_string() in /home/jamminsa/public_html/wp-content/plugins/sucuri-wp-plugin/lib/hooks.php:276 Stack trace: #0 /home/jamminsa/public_html/wp-includes/class-wp-hook.php(286): sucuri_events_without_actions(”) #1 /home/jamminsa/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #2 /home/jamminsa/public_html/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #3 /home/jamminsa/public_html/wp-admin/admin.php(156): do_action(‘admin_init’) #4 /home/jamminsa/public_html/wp-admin/plugins.php(10): require_once(‘/home/jamminsa/…’) #5 {main} thrown
File /home/jamminsa/public_html/wp-content/plugins/sucuri-wp-plugin/lib/hooks.php
Line 276
Type Description This type of error indicates that PHP cannot continue to run the code. Typical causes of this type of error are code bugs that have typos, missing or incomplete files (such as a file that was only partially uploaded), and the code using more memory than it is allowed.
Note that this message is generated by iThemes.com products when an error is encountered on the site. While an iThemes product is generating this message, it is not necessarily the cause of the problem.
You must be logged in to reply to this topic.