KvnKrft
Forum Replies Created
-
Forum: Plugins
In reply to: [Autoptimize] CSS on Search Page@optimizingmatters – Thank you, I really appreciate it. You should offer some smaller packages our hourly rates… 🙂
Forum: Plugins
In reply to: [Autoptimize] CSS on Search PageHey @optimizingmatters – How’s this?
https://www.healthfulpursuit.com/?s=benfits&is_v=1
Do you see the massive CSS dump at the top?
Forum: Reviews
In reply to: [WooCommerce] Not stable. Requires constant fixing and troubleshooting.Hi Mike,
The problem with PHP notices in logs is that they will eventually turn into problems. Once we know who “owns” the notice and will resolve it, it isn’t as big of a deal. Our first priority is always to figure out who will fix it.
The other problem with the PHP notices is that they clutter up the logs. We don’t want any errors in our error logs for any sort of time.
Hope that helps explain our problems with the PHP notices.
K
Forum: Reviews
In reply to: [WooCommerce] Highly disappointedMike, are you the owner of WooCommerce?
Forum: Reviews
In reply to: [WooCommerce] Not stable. Requires constant fixing and troubleshooting.More issues. More issues.
It would be really great if we could get a premium support option – so we can get these issues resolved quickly. Also, I’m extremely worried that issues cause data problems or problems with payment processor status synchronization (e.g. PayPal has a subscription active but WooCommerce shows it canceled).
Don’t get me wrong, I’m still a big fan (not that it matters), but we want to provide our customers with a good experience. We also don’t want to frustrate our team, who needs to wait for me to get tech issues resolved (via WooCommerce tickets).
It looks like WooCommerce Order Status Control, WooCommerce Google Analytics Pro, Woocommerce Subscriptions, WooCommerce Social Login, and Woocommerce Memberships use WC_Order_Item_Meta which seems to be the cause of 8+ entries in our server log. Ticket created (#601100), but its… another ticket to track and follow-up on.
Then we seem to have customers who are getting billed for subscriptions that are set to canceled in WooCommerce. Another ticket created (#598822), replies/updates on the ticket are slow, while I’m sweating about more customers being impacted.
If I can help somehow, please let me know.
Forum: Reviews
In reply to: [WooCommerce] Highly disappointedHey,
Sorry to hear about your issues and experience with WooCommerce support. I often get the “it’s your code” reply, which is frustrating. They do always end up on the same page with me though and things do get resolved. The problem with that is… while things are getting resolved customers are being impacted.
I am a WooCommerce/Wordpress fan – just because the other solutions out there are more restrictive and have issues as well (with support that’s worse). Hang in there, that’s my recommendation.
K
Forum: Reviews
In reply to: [WooCommerce] Not stable. Requires constant fixing and troubleshooting.Hi Mike,
Thanks for the reply – again. No need to follow-up. I create tickets for each of these, sometimes WooCommerce support acknowledges the bug, sometimes support tries to blame something. Eventually, we get it figured out.
And yea, we understand the 3.0 was a big change, it doesn’t change the fact that WooCommerce has become much more onerous and time-consuming for us to maintain as a business. Other businesses may not have had the same experience, but it’s important to share our experience pros and cons with the community.
Forum: Reviews
In reply to: [WooCommerce] Not stable. Requires constant fixing and troubleshooting.Hi Mike,
Thank you for your reply. Michael helped me with the test/production environment. For now, we will:
1.) Deactivate licenses for our production environment
2.) Activate licenses for our test environment
3.) Update and test in our test environment
4.) Deactivate licenses for our test environment
5.) Activate licenses for our production environment
6.) Update extensions in production and validateWe have had many problems with extensions. The difficulty is that we don’t want to ignore PHP errors and notices in logs because we don’t know what impacts they have.
Here are a few examples. We report them right away, and they seem to have been fixed, but it’s an ongoing thing. We are constantly finding these and reporting them.
[07-Jun-2017 16:31:19 UTC] PHP Notice: Array to string conversion in /web/sites/###/shop/wp-content/plugins/woocommerce-cart-reports/admin/cart_index_interface.php on line 318
[16-Jun-2017 20:38:11 UTC] PHP Fatal error: Uncaught Error: Call to a member function getOffsetTimestamp() on null in /web/sites/###/shop/wp-content/plugins/woocommerce/includes/data-stores/abstract-wc-order-data-store-cpt.php:124
[05-Jun-2017 03:09:46 UTC] The WC_Coupon::exclude_sale_items function is deprecated since version 3.0. Replace with WC_Coupon::get_exclude_sale_items.
[Mon May 08 20:20:48.088386 2017] [:error] [pid 2152] [client ##.##.##.##:49270] billing_email was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, do_action(‘woocommerce_checkout_order_processed’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Mailchimp_Integration->send_order_data, WC_Mailchimp_API->subscribe_to_list, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0., referer: https://www.###.com/shop/checkout/
[Wed May 03 18:19:01.260933 2017] [:error] [pid 26380] [client ##.##.##.##:59446] WC_Checkout->posted was called incorrectly. Use $_POST directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->create_order, WC_Order->save, WC_Data_Store->create, WC_Order_Data_Store_CPT->create, do_action(‘woocommerce_new_order’), WP_Hook->do_action, WP_Hook->apply_filters, AV8_Cart_Reports->save_order_id, AV8_Cart_Receipt->save_order_id, WC_Checkout->__get, wc_doing_it_wrong. This message was added in version 3.0.0., referer: https://www.site.com/shop/checkout/
WooCommerce used to be pretty low maintenance, but since 3.0 it has gotten much heavier to maintain – and more expensive and time-consuming for us.
Forum: Plugins
In reply to: [Redirection] Undefined index: HTTP_USER_AGENT (redirect.php on line 349)Hi @pxforti isn’t this the support forum for that plugin?
What am I missing here?
Forum: Plugins
In reply to: [Code Snippets] Undefined offset: 0Hi Shea, thanks for your help. I really appreciate it.
Forum: Plugins
In reply to: [Code Snippets] Undefined offset: 0Hey Shea. Is there any way to expand the debug output to troubleshoot these types of issues?
And THANK YOU for your help!
Forum: Reviews
In reply to: [upPrev] Great plugin and authorClearly, you are maintaining this plugin and I didn’t know what I was talking about 🙂
Thank you. I tested quickly in our staging environment, then moved it over to production, and archived the logs. Will let you know.
Forum: Plugins
In reply to: [WP Limit Login Attempts] Error In LogsHi, I updated the plugin but W3TC is still not agreeing with the plugin:
[Wed Apr 26 14:31:20.800949 2017] [:error] [pid 11257] [client 69.63.163.14:60469] PHP Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /web/sites/#######/#######.com/wp-content/plugins/w3-total-cache/PgCache_ContentGrabber.php:339) in /web/sites/#######/#######.com/wp-content/plugins/wp-limit-login-attempts/wp-limit-login-attempts.php on line 67, referer: https://www.google.com/
[Wed Apr 26 14:31:20.801308 2017] [:error] [pid 11257] [client 69.63.163.14:60469] PHP Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /web/sites/#######/#######.com/wp-content/plugins/w3-total-cache/PgCache_ContentGrabber.php:339) in /web/sites/#######/#######.com/wp-content/plugins/wp-limit-login-attempts/wp-limit-login-attempts.php on line 67, referer: https://www.google.com/
[Wed Apr 26 14:32:13.106280 2017] [:error] [pid 11423] [client 104.129.194.74:24827] PHP Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /web/sites/#######/#######.com/wp-content/plugins/w3-total-cache/PgCache_ContentGrabber.php:339) in /web/sites/#######/#######.com/wp-content/plugins/wp-limit-login-attempts/wp-limit-login-attempts.php on line 67, referer: http://m.facebook.com
[Wed Apr 26 14:32:13.106447 2017] [:error] [pid 11423] [client 104.129.194.74:24827] PHP Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /web/sites/#######/#######.com/wp-content/plugins/w3-total-cache/PgCache_ContentGrabber.php:339) in /web/sites/#######/#######.com/wp-content/plugins/wp-limit-login-attempts/wp-limit-login-attempts.php on line 67, referer: http://m.facebook.com
Forum: Reviews
In reply to: [JetBackup - Backup, Restore & Migrate] Exercise Caution@backup-guard: Lisa, nothing is “impossible”. A plugin is code that has permission to do almost anything. A little bug or uncaught edge case can lead to issues. My recommendation to you is that you slow down, take a step back, get the details first before getting into confrontational replies and discussions.
Sorry David, but our serverS are NOT overloaded and closely monitored. They are currently sitting at ~5% CPU and ~13% memory usage. None of our servers exceeds more than 14% CPU and 28% memory usage during peak times.