zanza321
Forum Replies Created
-
Forum: Plugins
In reply to: [W3 Total Cache] Question setting up W3TC CDN with Cloudfront ExtensionOk, here is what I see on CloudFront now just for reference
Forum: Plugins
In reply to: [W3 Total Cache] Question setting up W3TC CDN with Cloudfront ExtensionAny idea where these can be found on Cloudflare dash? All I see is an API key section, but it doesn’t mention these terms above.
Forum: Plugins
In reply to: [WooCommerce] Memory issues with Woocommerce?thanks! will try those !
Forum: Plugins
In reply to: [WooCommerce] Memory issues with Woocommerce?As mentioned in the original post, this behavior (which I still am not sure if its a bug or not) happens when the site being visited by potentially 20-30 people at the same time, and assumed they are doing actions such as checking-out, adding items to cart, and attempting payment. How do you suggest we recreate this?
Why can’t WordPress have a memory monitor feature to tracking how much memory each plugin is using? How is it able that a WordPress installation would use up to 2GB of system memory resources, if the config file is limited to 256MB?
Forum: Plugins
In reply to: [WooCommerce] Memory issues with Woocommerce?Hi thanks for the reply! I do appreciate your time. Yes, this does make sense, but unfortunately it will not be possible. We are using the Storefront theme now already too.
We have a lot of integrated plugins, including many critical ones that the site simply wouldn’t function without (like payment plugins, shipping plugins, display Slider, etc). So its simply not really possible to disable everything and “run a test” since the site would not be really be usable to the customer at that point.
Is that really the only way to find an issue, just eliminating all plugins and hope you find the correct one? There isn’t a way to monitor how much memory/resources each individual plugin is using, and then be able to make decisions from this record or log?
Just to clarify, the pages all load fine (those are handled by the caching plugin I assume). The issue is with the checkout and admin panel. Once users get here, it starts to just give “timeout errors” etc… Assuming because this part can’t be cached and is more server intensive.
- This reply was modified 3 years, 1 month ago by zanza321.
seems to be fixed and working for now. Maybe it was a service outage for about 6 hours earlier today ?
Forum: Plugins
In reply to: [WP Super Cache] Problem on checkout wc-ajax=update_order_reviewI did what you said, the XHR request shows “-1” response, which is code for cached nonce error
Forum: Plugins
In reply to: [WP Super Cache] Problem on checkout wc-ajax=update_order_reviewAnd just to clarify, this seems to be somewhat of a new error, although I am not exactly sure when in the past several weeks/months it started happening.
“You need to find out why the js file in the second screenshot is 403 Forbidden ”
About the forbidden file, idk, I checked the filesystem and the permissions are 644 same as everything else for the jquery.js
Forum: Plugins
In reply to: [WP Super Cache] Problem on checkout wc-ajax=update_order_reviewHI, we narrow the problem down to WPSC. That is, I disabled all plugins, and eventually the problem only happens with WPSC, and doesn’t happen without WPSC.
Even more details, is that the problem only happens with WPSC and option “Don’t cache pages for known users.” is unchecked
Versions is latest version of WordPress, and Version 3.5.4 Woocommerce (should be all latest)
New version is working for me. I just looked at your site, it seems you have Express Paypal disabled, and using the standard Paypal Woocommerce payment method so I wasn’t able to test really.
yes, updated to latest version and issue seems to be fixed now!
thanks!
hi Amanda
Yes, you are correct. I didn’t know there were settings governing this. Problem fixed now with setting checked! (I don’t know how it got disabled)
+1
yes, I disabled “Woocommerce Services” on live site and error went away.
The only difference I could see was on the Staging site, there was not live USPS rates, because they disabled that for new sites apparently.