David Marín Carreño
Forum Replies Created
-
Forum: Plugins
In reply to: [DFX Automatic Role Changer for WooCommerce] functionalityHi!
Sorry, I’m afraid this plugin doesn’t work this way.
Marking as resolved.
Hi all!
I just generated a new version, marking it as compatible with WooCommerce HPOS (it already was compatible, but I needed to activate a flag so Woo considers it that way).
Thanks for reporting!
Basically, we have a custom plugin that makes use of this hook without providing a second argument (without $user_data), this way:
do_action( 'lostpassword_post', $errors );
This doesn’t cause any problem without WP-2FA (as all the functions in WordPress called by this hook receive one argument), but if WP-2FA is active, this call generates a fatal error due to the missing parameter.
We just propose you to simply change the line 46 of class-reset-passord.php from:
public static function lostpassword_post( $errors, $user_data ) {
to:
public static function lostpassword_post( $errors, $user_data = false ) {
Thanks for your answer.
I’m adding this try/catch block to our site, and I’ll keep working to determine why this is happening. Unfortunately, the problem doesn’t seem to be deterministic. In all our tests, and in the general case, everything works correctly. There’s something that causes this in 3 or 4 orders per week.
I’ll keep you informed if I get something clear from my tests.
We’ve seen this problem for both Credit Cards and Paypal, but in the last weeks it’s much more frequent with Paypal.
Our main concern is the fact that a problem when saving the token causes the order to be moved to failed status, even after the payment has correctly been charged. Having problems saving the token in the vault should never make the already-charged order to be moved to failed status.
Having problems retrieving the token is, at this moment, secondary for us.
Could we have an option, or even better, a filter to decide if the “Saved Account” or the “New Account” radio button is selected by default?
As I said, for us it’s really important to show the “Paypal Later” button.
Exactly.
For anonymous users, or for registered users without a Paypal payment method in their account, the Checkout page replaces WooCommerce’s default “Place Order” button with the two Paypal Buttons.
In our page, if the user already has a registered Paypal payment method associated to their account, when the saved account is selected, the Checkout page doesn’t show the typical Paypal buttons to proceed with the payment, but only the original WooCommerce’s “Place Order” button:
In this example, the selected cart doesn’t include any subscription. However, the current user has an active subscription paid through Paypal, with the saved account.
If the user selects “New Account” the two typical Paypal buttons (the standard PayPal one and the one from Paypal Later) are shown.
- This reply was modified 10 months, 4 weeks ago by David Marín Carreño.
@polevaultweb I’ve been told by ACF-Pro support that you won’t support fields associated to Orders once orders in the site won’t be custom post types any longer.
I’d just like to confirm this information, in order to start moving our current Order-associated custom fields into native WooCommerce fields inside their meta-boxes, or we still should wait for a short-term incoming support: these fields currently are one of the few things that are blocking us from moving our system to HPOS.
Forum: Plugins
In reply to: [Klaviyo] Deprecated warning php 8.1Sorry for the misunderstanding. With “You” I meant the plugin developers 😉
I’m also affected by this bug!
Forum: Plugins
In reply to: [Klaviyo] Deprecated warning php 8.1Yep. I’m afraid you’ve used a deprecated feature to fix the issue with the get_klaviyo_option() function…
Please, consider replacing
return $filter_var($option_value, FILTER_SANITIZE_STRING);
with the following code
$option_value = preg_replace('/\x00|<[^>]*>?/', '', $option_value); return str_replace(["'", '"'], [''', '"'], $option_value);
Forum: Plugins
In reply to: [Random User IDs] Database HelpHi!
The plugin only carries out the user_id substitution in the default WordPress tables wp_users and wp_usermeta, and in the table wp_posts for the post_author meta.
You should check your database, checking for tables including user_id columns, or metadata tables checking for metadata referencing user ids.
Certainly, this is a bit tricky step, but unfortunately I cannot give support to the whole WordPress ecosystem!
Hi!
The thing you are probably seeing is that they are assigned a very high number instead of the probably-expected lower ID.
New users won’t have a random IDs any longer, but sequential ones.
I’m afraid there’s nothing we can do about this: when generating the next user_id, MySQL will take the highest existing user_id and add one to it.
Forum: Themes and Templates
In reply to: [Blocksy] Remove extra deprecations in PHP 8.1Hi!
I confirm the deprecation warnings are now solved with version 1.8.69.
Thanks for your kind support.
Forum: Themes and Templates
In reply to: [Blocksy] Remove extra deprecations in PHP 8.1I just checked again, and only one of the three targeted deprecations had already been solved.
This would be the correct patch for the last version of Blocksy
diff --git a/inc/components/hero-section.php b/inc/components/hero-section.php index 8c8c06b93..3e18067b5 100644 --- a/inc/components/hero-section.php +++ b/inc/components/hero-section.php @@ -38,7 +38,7 @@ if (! function_exists('blocksy_get_page_title_source')) { return $result; } - if (strpos($prefix, 'single') !== false || ( + if (strpos($prefix ?? '', 'single') !== false || ( function_exists('is_shop') && is_shop() ) && ! is_search()) { $post_options = blocksy_get_post_options(); diff --git a/inc/sidebar.php b/inc/sidebar.php index 0f4b1d248..20e411c88 100644 --- a/inc/sidebar.php +++ b/inc/sidebar.php @@ -182,7 +182,7 @@ if (! function_exists('blocksy_sidebar_position_unfiltered')) { ]); if ( - strpos($prefix, '_archive') !== false + strpos($prefix ?? '', '_archive') !== false || $prefix === 'search' || @@ -220,7 +220,7 @@ if (! function_exists('blocksy_sidebar_position_unfiltered')) { && $prefix !== 'product' && - strpos($prefix, '_single') === false + strpos($prefix ?? '', '_single') === false && ( $prefix !== 'courses_archive'