David Marín Carre?o

The issue is ultimately caused because the plugin initialization code tries to load translated strings:

  /www/1_768/public/wp-blog-header.php 13 calling require_once("\/www\/1_768\/public\/wp-load.php")
  /www/1_768/public/wp-load.php 50 calling require_once("\/www\/1_768\/public\/wp-config.php")
  /www/1_768/public/wp-config.php 136 calling require_once("\/www\/1_768\/public\/wp-settings.php")
  /www/1_768/public/wp-settings.php 526 calling include_once("\/www\/1_768\/public\/wp-content\/plugins\/members\/members.php")
  /www/1_768/public/wp-content/plugins/members/members.php 487 calling members_plugin()
  /www/1_768/public/wp-content/plugins/members/members.php 483 calling get_instance()
  /www/1_768/public/wp-content/plugins/members/members.php 95 calling includes()
  /www/1_768/public/wp-content/plugins/members/members.php 209 calling require_once("\/www\/1_768\/public\/wp-content\/plugins\/members\/inc\/functions-users.php")
  /www/1_768/public/wp-content/plugins/members/inc/functions-users.php 14 calling members_explicitly_deny_caps()
  /www/1_768/public/wp-content/plugins/members/inc/functions-options.php 35 calling members_get_setting("explicit_denied_caps")
  /www/1_768/public/wp-content/plugins/members/inc/functions-options.php 107 calling members_get_default_settings()
  /www/1_768/public/wp-content/plugins/members/inc/functions-options.php 132 calling esc_html__("Sorry, but you do not have permission to view this content.", "members")
  /www/1_768/public/wp-includes/l10n.php 339 calling translate("Sorry, but you do not have permission to view this content.", "members")
  /www/1_768/public/wp-includes/l10n.php 194 calling get_translations_for_domain("members")
  /www/1_768/public/wp-includes/l10n.php 1408 calling _load_textdomain_just_in_time("members")
  /www/1_768/public/wp-includes/l10n.php 1370 calling _doing_it_wrong("_load_textdomain_just_in_time", "Function _load_textdomain_just_in_time was called <strong>incorrectly<\/strong>. Translation loading for the <code>members<\/code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init<\/code> action or later. Please see <a href=\"https:\/\/developer.www.remarpro.com\/advanced-administration\/debug\/debug-wordpress\/\">Debugging in WordPress<\/a> for more information. (This message was added in version 6.7.0.)", "(This message was added in version 6.7.0.)")
 in <b>/www/1_768/public/wp-includes/functions.php</b> on line <b>6160</b><br />

Hi!

Just to confirm: you are operating the plugin so it replaces roles, instead of adding them, right?

Yes, in that case we should prevent replacing the administrator role from admins.
I’ll work to ensure that.

I’ll keep you posted. Thanks for the report!

Hi!

I just added a new feature to the plugin, so you can choose when the role is assigned (on order payment, and/or on status change).

Please verify if this solves your issue.

Thanks for your suggestion!

Acabo de a?adir una nueva funcionalidad en el plugin para permitir elegir entre a?adir el nuevo rol (comportamiento previo, y por defecto) o bien hacer que el nuevo rol sustituya al rol anterior.

Por favor, verifique si este cambio soluciona su problema.

Muchas gracias.

El desarrollo del plugin sigue activo y está funcionando a día de hoy en muchos otros sitios.

No dudo de que no funcione en su instalación. Esto puede ser por muchos y variados motivos. Desde que la pasarela de pago no haga las llamadas de hooks estándar para marcar el pago como completado (conozco el caso de una pasarela que no lo hace), o algún otro problema.

?Podría darme más información sobre su sitio, la pasarela de pago empleada, y otros plugins instalados?

• This reply was modified 5 months, 2 weeks ago by David Marín Carre?o.

No es lo que dicen otros muchos usuarios satisfechos…

Quizá Vd. espera que funcione de una manera diferente a como lo hace. Antes de soltar una opinión así de dura podría ponerse en contacto con el autor para averiguar qué sucede…

In order to say that your plugin is compatible with HPOS you stop considering that orders are posts, and stop messing with the post_type of the post with order_id: when syncing is disabled your plugin causes a mess in the database.

Hi!

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 1 year, 6 months ago by David Marín Carre?o.