nboot8

Hi @khungate ,
Because of this error I had already switched my customer’s site to another process, so I have no feedback at this time. Thanks for the information though, in case we want to consider it in the future.
Best regards

Version 2.1.10 results in the following error for me:
API Key Invalid :: Your API key may be invalid, or you’ve attempted to access the wrong datacenter.

Version 2.1.11 results in a message “401 unauthorized” next to the API field.

Version 2.1.15 throws the same error as this thread.

This is on a brand new installation with only approximately 60 users to sync.

First-time install of the plugin on our site resulted in this error. Will try to use the old version as discussed in this thread, but I’m posting this to be notified of updates as well as for confirmation that it is still wide-spread and needs to be addressed.

You may want to look for files like these (which were also infected as a result, on our site). I’m not sure how specific they are to each domain (except of course the SiteOrigins infection is only if you run that plug-in).

~/public/wp-content/uploads/siteorigin-widgets/hsnbm2ju9o.php

~/public/7q0ny7bgmy.php

~/public/wp-super_cache.php

…th1s_1s_a_4o4.html…

Same issue here… I have installed 2.0.25 version, but my latest DB version is 2.0.10 and the “updater” will not run – it just sits on “Get upgrades packages…” all day. Really frustrating after the amount of money I have sunk into this over the years.

Anyway, here is the file I found with the virus:

~/public/wp-content/uploads/ultimatemember/temp/tfCE0YbNhMMHQw4IRZiada6vLS1J7XuCEDzohcq0/stream_photo_12261104284b7316c107dd17323d5cb9_5b7ab0958bf57.php

Not sure what it would be for you, but you may just want to clear your whole temp directory.

The worst part is that this crazy instability introduced with the “move” to version 2 of the plug-in has resulted in pretty much an unusable front end for my clients. In this case, even after deleting the virus files, I have an issue that I cannot log in without disabling the plug-in, then re-enabling afterward – which basically means that no user can log in period. What a pain…

Good luck.

Sorry, I see the request to join the forum for this. moving there now. thanks

Hi,
I have this same issue regarding my user pages not showing up and have tried to understand and implement some of the changes suggested here but not had any success.

Could you please send me a private message that I can provide with credentials to check my site? (proatamartialarts.com)

Thanks

PERFECT!!!

Thanks for your excellent and prompt support. I really appreciate you going out of your way to accommodate this requirement.

Have a great weekend!

Testing it now… I’ll let you know the results. Thank you

Hi,
Thanks for the quick response. Yes, I think that would work. Do you have a link that shows the actions associated with that process?

Thanks again…

If you could please point me to an action that UM does trigger, I can also update my functions file with the following:

***

add_action(‘wp_logout’, ‘custom_logon_on_off’);
add_action(‘wp_login’, ‘custom_logon_on_off’);

function custom_logon_on_off() {
global $wc_catalog_restrictions;

$wc_catalog_restrictions->clear_transients();
}

***

Thanks