Alexandre Froger

addressed in 1.3.16

If there is front end update of a user profile, it is done by a third party (plugin or theme). It is up to the third party to call the correct hooks to notify other plugins of the update. Please contact the author of the theme or plugin responsible for the chose front end.

Please hire a developer.

Multisite support has been added as of v2.0. If it isn’t available for download yet, it should be shortly.

Please check whether there is any javascript error in the browser console as it very likely comes from a third party (unable to reproduce).
As of v2.0, better error handling and fallback for redirection have been added, and updating may help with your issue. If it isn’t available for download yet, it should be shortly.

Please check whether there is any javascript error in the browser console as it very likely comes from a third party (unable to reproduce).
As of v2.0, better error handling and fallback for redirection have been added, and updating may help with your issue. If it isn’t available for download yet, it should be shortly.

Please check whether there is any javascript error in the browser console as it very likely comes from a third party (unable to reproduce).
As of v2.0, better error handling and fallback for redirection have been added, and updating may help with your issue. If it isn’t available for download yet, it should be shortly.

Hi, and thank you for the candid review of v1.2.11.

There was no need to update the plugin except for the compatibility flag – which does not affect how the plugin works.
WPRUS has been designed with long-term compatibility in mind from the ground up – php 8 deprecation warnings were minor, would not affect sites in production environment, and have been solved in v1.2.12.
Explicit updates are usually deployed whenever my personal time allows for it (and it hasn’t for a while), or?in all cases as #1 priority when a bug has been reported and documented adequately?for it to be fixed (as was the case with v1.2.12).

If the issue you encountered (login loop) persists, you have a reliable & repeatable procedure to reproduce it on a fresh installation, and a way to pinpoint the piece of code responsible for it, please feel free to contact me, and I will fix it.

Best,
Alexandre Froger

Hi, and thank you for the candid review of v1.2.11.

There was no need to update the plugin except for the compatibility flag – which does not affect how the plugin works.
WPRUS has been designed with long-term compatibility in mind from the ground up.
Explicit updates are deployed whenever my personal time allows for it (and it hasn’t for a while), or in all cases as #1 priority when a bug has been reported and documented adequately for it to be fixed (as was the case with v1.2.12).

Best,
Alexandre Froger

Hi and thank you for the review! There is a video here on YouTube (not by me, no affiliation). Hope it helps!

Hi @szymonfortuna ,

Being based on very stable WordPress core functions, the plugin doesn’t need constant updates. The alert message you see is simply a flag that I didn’t update the compatibility flag, but to be honest I find it a waste of time to push a new version on the repo and up the plugin’s version number just for that.

Hi @robwent ,

Do you have more info about that?

• Browser used
• Plugins/theme used (rule of thumb: this is a WPRUS issue if it happens with Storefront/any other WP default theme and no WP plugin enabled)
• WPRUS settings – both sites – specially the “Miscellaneous” section

Best

• This reply was modified 2 years, 4 months ago by Alexandre Froger.

As a side note: this behavior can be customised by developers with a combination of overloading the API classes and using the WordPress action and filter hooks provided by the plugin.

Merely matching the tone of the thread.

It does not contradict itself. If a user profile is updated on Site A, with the set of actions indicated in the same paragraph of the FAQ properly configured, then the user is created on site B if it does not exist.

User logs in on site A > Login action fails on site B > profile is updated somehow on site A (in the instance of WooCommerce you described it happened at order time) > user gets created on Site B

A user cannot be simply created at Login, because the payload for Login and Logout sent to Site B cannot and will not include the entirety of the user account data.

• This reply was modified 2 years, 4 months ago by Alexandre Froger.
• This reply was modified 2 years, 4 months ago by Alexandre Froger.

Support may only be good as the user’s due diligence and feedback, I suppose…

What if the user to synchronise does not exist on the remote site?

If the incoming Create action is enabled along with the incoming Update action, the user will be synchronised on the remote website upon user update.
If other actions for this user are fired before that (Login, Logout, Delete, Password, Metadata), nothing will happen, and an action failure log entry will be recorded if the “Enable Logs” box is checked.

From the FAQ.