This is the note from Siteground:
Thanks - can you contact them and let them know about this? That the cache was cleared, that the website is working on desktop computers without any errors? Also: mod_security is a web application firewall and cannot be disabled. If the issue is only on mobile, then perhaps they can review your website in details and check what needs to be done to resolve the issue.
Hi there,
They don’t need to disable it, they just need to exclude these URLs ( http://96.127.158.130/~equineou/wp-content/plugins/woocommerce/assets/js/jquery-cookie/jquery.cookie.js
http://96.127.158.130/~equineou/wp-content/plugins/woocommerce/assets/js/jquery-cookie/jquery.cookie.min.js ) from blacklist (allowing it to load).
Have you tried other options? Like this
http://96.127.158.130/~equineou/wp-content/plugins/woocommerce/assets/js/jquery-cookie/jquery.cookie.js
http://96.127.158.130/~equineou/wp-content/plugins/woocommerce/assets/js/jquery-cookie/jquery.cookie.min.js
to these
http://96.127.158.130/~equineou/wp-content/plugins/woocommerce/assets/js/jquery-cookie/jquery_cookie.js
http://96.127.158.130/~equineou/wp-content/plugins/woocommerce/assets/js/jquery-cookie/jquery_cookie.min.js
add_action( 'wp_enqueue_scripts', 'custom_frontend_scripts' );function custom_frontend_scripts() {global $post, $woocommerce;
$suffix = defined( 'SCRIPT_DEBUG' ) && SCRIPT_DEBUG ? : '.min';
wp_deregister_script( 'jquery-cookie' );
wp_register_script( 'jquery-cookie', $woocommerce->plugin_url() . '/assets/js/jquery-cookie/jquery_cookie' . $suffix . '.js', array( 'jquery' ), '1.3.1', true );
}
Else, you have to try option 3 too.
Thanks!
I tried both of these solutions. Neither worked. Here is the response from Siteground:
I have just checked the server logs but there is no mod_security rule being triggered for your account.
For test purposes, I have temporary disabled the mod_security for your account and have accessed the website on my end but the issue kept persistsiing and what I noticed is that if I hold on the menu button and open it in a new tab it opens the following URL:
http://96.127.158.130/~equineou/#
As for the above provided URL it is actually :
And as you can see nothing is blocking it at the moment.
I am afraid that I will not be able to tell on what is causing the issue on mobile devices but it might be also related to the current temporary URL. Still I will advise you to check this once again with the theme developers, providing them the above information .
Hi there,
What you did is okay, it fixes the Woocommerce cookie issue. One issue at a time since we can’t go forward if the first one hinders our troubleshooting, now other aspects of your site is now functional.
The menu is not clickable too, and to further fix it, please remove this CSS from your global custom CSS
[data-x-icon], [class*="x-icon-"] {
color:white;
}
This hides all your menu icons in a white background.
As for the product on the homepage, it’s configured to work in ajax (didn’t notice this since the cookie part fails), you see nothing since the process is done in the background. But it’s added to the cart. So I went ahead and change your woocommerce setting, under Woocommerce > Settings > Products, I toggled on Redirect to the cart page after successful addition. That should redirect you to cart once you add a product (ajax or not).
Thanks!
Yes, the menu issues is the main issue which started this whole chain. I deleted the CSS but it didn’t really change anything- when I click the menu icon on a mobile device, nothing happens. What now?
Hi,
Something is conflicting in your site, I went ahead and added a temporary fix for the mobile button.
I added this in X > Launch > Options > JS
jQuery(function($) {
$( "a.x-btn-navbar" ).on( "click", function() {
$(this).toggleClass('in');
});
});
Kindly check in your end.
Thanks
Hi there,
The current situation of the page you gave the link is this:
It is full of errors.
First of all the jQuery not defined error which is caused by the code, you added in the Customizer.
Secondly, the HTML is completely problematic and it does not have the closing (>) for tags.
Not sure what is the problem but I would check the meta description section.
I strongly suggest that you open up a new thread and give us detailed information of the problem you are experiencing to be able to help you better. The original name of this thread is completely something else and misleading, also each time one of the support staff tries to answer he/she needs to read from top to bottom, knowing that the original post is resolved and there are other questions.
By this way, you will have more clean answers and better quality service at hand.
Thank you for your understanding.