George
Forum Replies Created
-
Forum: Plugins
In reply to: [WordPress Importer] Plugin slow/crashing on large sitesIn case it helps anyone until (if) this gets fixed, you can limit the records returned by the drop-down with the following filter that returns just users of a specific role.
<?php
/**
* Force the WordPress Importer author dropdown to only load Editors.
* This runs only on the Importer screen to avoid affecting other areas.
*/
add_filter( 'wp_dropdown_users_args', function( $args, $parsed_args ) {
// Only on the Importer screen & only for the WordPress importer.
if ( is_admin()
&& isset( $_GET['import'] ) && $_GET['import'] === 'wordpress' // Tools → Import → WordPress
) {
// Hard-limit to the Editor role.
$args['role'] = 'editor';
// (Optional) keep UI snappy:
$args['orderby'] = 'display_name';
$args['order'] = 'ASC';
$args['number'] = 500; // safety cap; increase if needed
}
return $args;
}, 10, 2 );Forum: Plugins
In reply to: [Meta for WooCommerce] Cookies being set before customer consentHi @marijastuntcoders i’m sorry but you didn’t answer my question. WHERE is this update being worked on? You said it’s not on Github, so where is it?
Forum: Plugins
In reply to: [Meta for WooCommerce] Cookies being set before customer consentForum: Plugins
In reply to: [Meta for WooCommerce] Cookies being set before customer consent@marijastuntcoders I’m sorry i don’t understand what you’re saying.
You previously said “We also have an update in the works that will simplify how consent is handled within the plugin, and we expect it to be released in the coming weeks.“. Where is this being worked on??
Forum: Plugins
In reply to: [Meta for WooCommerce] Cookies being set before customer consentHi @marijastuntcoders ,
I notice the update is not part of release 3.5.7 either so we need to hardcode the change again.
Can you please point us to the related github issue?
Forum: Plugins
In reply to: [Meta for WooCommerce] Cookies being set before customer consentHello, can you please confirm if this was meant to be resolved in Version 3.5.6 that was released a few hours ago, or will it be part of a future update?
Forum: Plugins
In reply to: [Meta for WooCommerce] Cookies being set before customer consentWe use the WP plugin to integrate Facebook, thinking that everything is taken care of without any dev/tech knowledge, however this is not currently the case and a developer is needed.
Are you saying that soon, the plugin will become fully compliant out of the box in a few weeks?
Hi @valuesyndrome can you test with the previous version of the Stripe plugin (8.2.0) and see if the issue persists?
If the issue goes away, you’re likely experiencing the same payment issues like many others on the forum, which is caused by a change on 8.3.0.
More details can be found here https://github.com/woocommerce/woocommerce-gateway-stripe/issues/3154
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Stripe is not updating order statusHi @carolm29 this issue and most of the recent payment issues on the forum are likely related to https://github.com/woocommerce/woocommerce-gateway-stripe/issues/3154
The quick fix for anyone struggling is to revert to the previous version (8.2.0) until 3154 is resolved
Hi @rajeshml it’s highly likely their issue is related to a new bug introduced on 8.3.0 and is reported here https://github.com/woocommerce/woocommerce-gateway-stripe/issues/3154 rather than the older (over a year old) bug you linked.
Many (most?) of the payment issues reported on the forum recently would be caused by 3154 so it needs to be looked at promptly.
@fetenlakhal thanks for your response
As we didn’t have many reports of merchants affected by this bug, we don’t have an ETA for when it will be resolved as the team first needs to analyze the situation and balance that with the other commitments on their plate.
This is flawed approach unfortunately. You assume people are capable of monitoring their logs, but the vast majority of WP/WC sites, are hosted on services where the deprecated warnings are hidden. Even if they are showing for some hosts, it would mean people would need to i) have debug.log enabled ii) know how to read it and make sense of it iii) actually monitor it.
I can guarantee to you, that of the millions of WP sites out there, only a small number of store owners can do the above. Of those, you need to find the ones who use a similar setup to reproduce the issue and of those, you need to find the ones that bother to report the issues.
Unfortunately, you’re left with a tiny percentage of people, so when something is reported by a handful of people, the impact is probably far greater.
As such, if the issue is reproducable, you should be putting every effort to fix. That’s even more important when it’s a deprecated warning, which means that soon it’ll go away. Why wait till the very last minute (or worse) before fixing when you’ve known for a year?
We’ve also reported this on https://ww.wp.xz.cn/support/topic/hook-wcs_renewal_order_meta-is-deprecated/ and woo.com support tickets (#6296281, #6296512 and #7482377) as back as May 2023 (!) but there’s been no progress on this.
I guess the team expects everyone to turn off deprecation warnings and hide issues under the carpet…
thanks for the prompt reply!
Thanks @ndiego
I’m not sure why you’d think this is a GB issue rather than something that needs changing on your plugin?
Here’s another report on their support page saying Yoast is also broken with the latest version, but that’s probably for Yoast to resolve?
@chilliwax have you seen this issue https://github.com/woocommerce/woocommerce/issues/14541 ? Hardcoding the change while waiting to get merged, seems to have greatly reduced the duplicate orders for us.
- This reply was modified 2 years, 6 months ago by George.