ablears
Forum Replies Created
-
I fixed my missing conditional field by updating checks for
mwb_upsell_bump_checkbox_containertowps_upsell_bump_checkbox_container.Sadly, upgrading to 2.1.0 stopped a conditional field at checkout from showing when the order bump was selected. So I downgraded to 2.0.2 and my order bumps don’t show in admin any more.
Looking into it I see your option changed from mwb_ubo_bump_list to wps_ubo_bump_list which explains why downgrading lost the data.
- This reply was modified 4 years, 1 month ago by ablears. Reason: added detail
Forum: Plugins
In reply to: [WooCommerce] Critical error with Woocommerce 6.2Great. Thanks @ospiotr, this works with Woo 6.2.
@makewebbetter this is an 8 month old thread that you’ve marked as resolved and yet the issue still remains. Please commit to including a fix in your next release.
Forum: Plugins
In reply to: [WooCommerce] Critical error with Woocommerce 6.2For me, disabling https://wordpress.org/plugins/disable-dashboard-for-woocommerce/ stopped the error, though I have that enabled for good reason as without it Woo would go nuts querying the 100+ sites on the network for the latest orders.
2.6.9 apparently fixes this issue.
From the changelog:
2022-xx-xx – version 2.6.9
* Fix – Replace is_ajax with wp_doing_ajaxI am using 2.0.1 and the issue remains for me.
Adding a string to Product Data -> Advanced -> Purchase Note didn’t stop
is_order_bump_purchase: truefrom appearing in the invoice or email in my case so a proper fix by @makewebbetter would be most welcome given this was reported 6 months ago.Forum: Plugins
In reply to: [KP Fastest Tawk.to Chat] Use different widgets from the same propertyYou can have a simple check to support both use cases.
$user_chat_id = get_option('kpfttc_chat_link'); if( strpos( $user_chat_id, "/" )===false ){ $user_chat_id .="/default"; } $kpfttc_chat_link = 'https://embed.tawk.to/'.$user_chat_id;Forum: Plugins
In reply to: [KP Fastest Tawk.to Chat] 404 on the embed.tawk.to linkHi, I upgraded to the latest version of your plugin and it looks like it doesn’t include this change, as all my sites using it won’t show the tawk.to widget.
Example incorrect link: https://embed.tawk.to/CHAT-ID/WIDGET-ID/default
Forum: Plugins
In reply to: [KP Fastest Tawk.to Chat] 404 on the embed.tawk.to linkHi, thanks for this.
The JS outputted by your patched plugin is:
setTimeout(function(){ var Tawk_API=Tawk_API||{}, Tawk_LoadStart=new Date(); (function(){ var s1=document.createElement("script"),s0=document.getElementsByTagName("script")[0]; s1.async=true; s1.src='https://embed.tawk.to/CHAT-ID/1eume4rs7'; s1.charset='UTF-8'; s1.setAttribute('crossorigin','*'); s0.parentNode.insertBefore(s1,s0); })(); },3000);Forum: Plugins
In reply to: [Disable Bloat for WordPress & WooCommerce] breaks with 5.0Thanks for the update and for taking the time to create this plugin.
With a commit that small I will make the change to the Woo file rather than wait for 5.0.1 to land.
Cheers!
Gist for anyone else with this issue: https://gist.github.com/ablears/273b6107c502736c2b24bcdca87220d6
Forum: Plugins
In reply to: [Code Snippets] Code Snippets in Production?I suggest you look at Redis as an object cache for WordPress, and WP Rocket as a front-end cache which will create static HTML files so your webserver will deliver those instead of going the expensive Apache/MySQL dynamic route for each request.
- This reply was modified 5 years, 9 months ago by ablears.
I understand, but that is not helpful. In this scenario, there could be support to set a stripe account locale separate from the store locale. In my example, that would mean I could set New Zealand as the Stripe locale and it would work even though the store locale is the Philippines. I see others in this forum have the same need.
Forum: Plugins
In reply to: [WooCommerce PayPal Checkout Payment Gateway] paypal is not definedI had this issue today after upgrading all plugins. Check the js file https://yoursite.nz/wp-content/plugins/woocommerce-gateway-paypal-express-checkout/assets/js/wc-gateway-ppec-smart-payment-buttons.js?ver=2.0.3 isn’t being cached. In my case, Varnish was caching it and a purge fixed the issue.