Forums › Forums › Search & Filter Pro › Site crashed after updating to 2.0.1
- This topic has 19 replies, 2 voices, and was last updated 9 years, 6 months ago by
Anonymous.
-
Anonymous(Private) February 25, 2016 at 3:13 pm #37944
Hello Ross.
First I want to say thank you for helping me.
I added this:
add_filter(‘body_class’,’add_body_class_to_search_filter’);
function add_body_class_to_search_filter($classes) {global $searchandfilter;
if($searchandfilter->active_sfid()){
$classes[] = “tax-product_cat archive woocommerce woocommerce-page alt-style-default boxed-layout two-col-right width-930 two-col-right-930”;
}
// return the $classes array
return $classes;
}and it is still crashing my staging site. Anything else that needs to be changed?
Thanks
Ross Moderator(Private) February 25, 2016 at 3:37 pm #37946So the plugin is already updated, and you have the above code and its crashing your site?
Thats odd, doesn’t look like anything wrong with that piece of code.
Could be some other code.
Enable WP_DEBUG to get more info on what the error message is, and then we can go from there.
Thanks
Anonymous(Private) February 26, 2016 at 3:50 pm #38062Alright, I enabled it.
And when the site breaks after adding the code to the functions.php of my theme this is the error I see:
Warning: mysqli_real_connect(): Headers and client library minor version mismatch. Headers:50544 Library:50629 in /var/www/dogloverstore/staging-site/wp-includes/wp-db.php on line 1488
That is all I see though, nothing else, just a white screen.
Thanks
Ross Moderator(Private) February 26, 2016 at 4:07 pm #38065Thats very strange, seems to be a DB error of some kind.
What happens, when you comment out all the custom S&F code completely?
Can you then also disable S&F to ensure it is in fact S&F generating this error?
Thanks
Anonymous(Private) February 26, 2016 at 6:10 pm #38097When I comment out the code in the functions.php file the warning stays the same but the site loads normally. If I remove the commenting out, the site breaks and the warning still exists.
Also, when I deactivate S+F that warning still persists, so it doesn’t seem like S+F is causing that warning but it is breaking my site when the code is added to the functions.php file.
Thanks
Ross Moderator(Private) March 2, 2016 at 10:17 am #38439Jsut replied via email, should all be sorted 🙂
-
AuthorPosts