jon

I’m assuming you mean the “New User Approve” plugin when you mentioned “New User Registration”.

Thanks for the updates. I often wonder when I don’t hear back from people, so this is even better.

So glad that you got it to work!

Thank you for explaining the BuddyPress Registration problem so clearly. I will check this out on my test system and see what is going wrong.

FYI, I am sure you are right as I always knew there were issues with Registration but never had a clear idea of exactly what they are.

Sorry about “scary”, but I have bowed to pressure from plugin users who wanted features that can create Redirection Loops in certain circumstances: usually other plugins doing something unexpected that my plugin does not handle. It would be self-defeating if I did not explain the Risk.

I’ll respond here as soon as I have some answers. Thank you for your interest in the plugin!

The four most likely possibilities for this problem that I suggest you check first are:

1. WordPress thinks you are logged on; this occurs when you logout from one Site URL, and access your site from another URL; even www.example.com and example.com are treated as separate logons by WordPress; the only convenient way to eliminate this as the cause of your problem is to logout and delete all cookies in your browser that match the Site URLs that could be used to access your site;
2. Be sure that you are using the same site’s Settings page for the plugin, as the site you are checking for privacy;
3. Find out if you have any plugins that Cache; if so, you will need to “flush” the cache (for the same site) every time you change a Setting in my plugin; during testing, it would be better to disable Caching altogether;
4. Flush your browser’s cache, or try another browser

#1 is the toughest one to deal with. But it is the most likely cause, especially if you use the WordPress MU Domain Mapping plugin.

#1 is also not really a problem, as your site is actually protected from others, even though you can see the site yourself.

As you can see, there are lots of possibilities. If you want more help, please feel free to respond.

Good to know for me, too. Last time I ran into this problem, even Delete Permanently did not solve the problem. Though it did resolve itself in a number of days, a month at most.

Great that you got it working!

WordPress is good a huge databases, so there is no danger of clogging up the database, other than the possibility you are running on a web host with a very low limit on database size.

But, if it were me, and I was serving a bunch of geeks (not meant as an insult, but radio-controlled car club makes geek a fair guess), I would experiment with the following concept: see if you can make a subdirectory/folder visible, so you can go there with a browser and see the contents as a list of file names and sub-subdirectories. Develop some good naming standards that everyone will understand for both sub-subdirectories and files. Create a sub-subdirectory for each evening, and put the 20-30 files in the appropriate sub-subdirectory.

On a WordPress page, simply provide a link to the subdirectory with all the sub-subdirectories in it. And an explanation of your naming conventions so everyone knows how to navigate.

Be sure to test it on all possible browsers, including mobile browsers, to be sure that this approach works before actually going forward with the idea.

(wrote this before I say Clayton’s post; his is a very good idea, too)

Assuming you have access to the file system through FTP or a control panel’s File Manager, you can rename or delete the offending plugin’s directory: /home/u324340871/public_html/wp-content/plugins/badgeos/

You should be able to login after that.

According to the error message, it is not currently possible to have both BadgeOS and buddypress-profile-tabs plugins ACTIVATED at the same time, because they apparently both use the same internal function name.