survivehive
Forum Replies Created
-
Forum: Plugins
In reply to: [Autoptimize] 500 error in WooCommerce Pages, when crawled by GoogleBotThis worked perfectly. Googlebot was able to fetch and render those pages.
It is missing an open bracket after the if statement. Corrected code below in case anybody else ever runs into the issue.
Thank you Frank for your persistence!
add_filter('autoptimize_js_do_minify','survivehive_ao_js_minify',10,1); function survivehive_ao_js_minify() { if (strpos($_SERVER['HTTP_USER_AGENT'],"Googlebot")!==false) { return false; } else { return true; } }
Forum: Plugins
In reply to: [Autoptimize] 500 error in WooCommerce Pages, when crawled by GoogleBotI have added min.js, and it still has the same problem.
Forum: Plugins
In reply to: [Autoptimize] 500 error in WooCommerce Pages, when crawled by GoogleBotIt is mobile responsive, but not mobile specific. I have tried a mobile view as well as a mobile view WITH the googlebot useragent. Both worked fine. I also tried a desktop and mobile fetch from googlebot which failed.
I know that is less than helpful. If you think of any other troubleshooting steps, I’d be glad to do them for you!
Forum: Plugins
In reply to: [Autoptimize] 500 error in WooCommerce Pages, when crawled by GoogleBotI tried the googlebot useragent in the emulator built in to chrome and the page loads fine. It’s quite odd… There is certainly something unique to googlebot that causes the issue, I just can’t seem to reproduce it.
Forum: Plugins
In reply to: [Autoptimize] 500 error in WooCommerce Pages, when crawled by GoogleBotI disabled JS Optimization, looked through the source and grabbed all javascript related to woocommerce, and added them to the excludes in the format:
“woocommerce.min.js,add-to-cart.min.js” etc…
I reenabled JS Optimization, saved, and googlebot still gets a 500 error.
I added the @ sign before $tmp_jscode on line 177, and fetched with googlebot, and still got the error.
I disabled JS Optimization and fetched with googlebot, success.
Strangely, It seems as though it’s only googlebot that get’s the 500 error. I can simultaneously browse the same exact page from my PC without any issue whatsoever.
Success — issues resolved in 1.9.0. Outstanding! Thanks!
The src attribute of the resources in question begins with //, not actually https://
I can also monitor the network tab and see no HTTP resources.
I will try 1.9.0 out anyway and report back.
You rock Alin! Thank you! Looking forward to the update!