David Marín Carre?o

Hi!

When activated, the plugin randomizes the ID for the first admin user, that has ID=1.

If you are finding errors, you should check the new ID for the first admin user and replace it in all tables with a user_id column. The plugin only does that in the users, usermeta and posts tables. You can check the new ID for the user either in the users table, or in the “dfx_randomuserid_first_user_moved_to” option.

You can either replace the remaining appearances of user_id=1 in all the other tables, or bring back the original ID for the first admin user by replacing its ID with 1 in tables users, usermeta and posts.

Yes, please apply the provided patch in future versions!

No. The role is assigned once the “woocommerce_payment_complete” hook is called, typically from the payment gateways.

The feature you are talking about is related to subscriptions. This is not supported by this plugin.

I plan to build a pro version for this plugin that supports WooCommerce Subscriptions, and allow the association of a role to a subscription product, so the role is associated with the active status of the subscription. This is still a work in progress, though, with no ETA.

Hi, @alexanderine

It seems you have found a limitation in the maximum ID number supported by this YITH P&R plugin.

You can always limit the maximum ID number generated by the Random User IDs plugin by using the method described in the “How to customize the range for new user IDs” section in the documentation.

Best regards.

It is!

But this is a so simple plugin that doesn’t need a lot of attention. ??

Sorry, I cannot keep track of the WP versions releasing every other week. This is just a plugin I created for one of my projects, and I’m just maintaining it. I need to pay my invoices, so I cannot invest time into it.

Nevertheless, contributions are welcome in my Paypal account. And, also, you can always create pull requests in my GitHub project (https://github.com/davefx/dfx-woo-role-changer) about plugin compatibility with newer WP versions, or any other feature and I will upgrade the project consequently!

@soham23 I’m sorry but that won’t ever be possible. The WordPress database schema uses an integer as the user ID, and this is not something that can be changed. Lots of features and third-party plugins depend on this as well, so even if we could do something to change this, we would potentially break the sites in many places.

After contacting Braintree support they’ve told me:

Client tokens are only valid for 24 hours. However, we still recommend generating one for each customer for a couple of reasons:

* If too many payment methods are made in short succession using the same client token, it will be invalidated (we do not provide specific figures for this to mitigate fraud risk)

* There are additional parameters you can pass in client token generation that may be customer or currency-specific (customer ID, or merchant account ID respectively). A token will be invalidated after its first use if these parameters are present.

For these 2 reasons, it is a best practice to generate a new client token as frequently as possible, if not for each unique customer session.

As the code is providing the merchant account ID, I’m afraid we won’t be able to activate this caching unless we are also able to invalidate any existing cached value if the client token is used.

• This reply was modified 4 years ago by David Marín Carre?o.
• This reply was modified 4 years ago by David Marín Carre?o.

Maybe it’s ok to leave it, but just changing its name. It could still be useful in those cases in which you want to save the json files to the uploads folder instead of the theme folder…

Something like “ACF JSON to Uploads”

Hi, Iurie Malai

Just a question about Sandbox accounts. In your purchases using them, are the corresponding orders moved to Processing or Completed status after the simulated payment?

I’m just used the standard WooCommerce hook that gets triggered when an order is paid. If this hook is not executed, my plugin won’t be able to do anything.

I just added some documentation to the plugin readme.txt file

Hi! I just added some documentation about this to the plugin web page: https://davefx.com/en/random-user-id/

I’m afraid I still don’t have documentation for it.

Basically a new field will appear in every product edition page, where you can set the desired role that will be assigned to the registered users that purchase that product.

Marking as solved