nyadna

[EDITED: I can confirm there’s a bug on BuddyBoss platform that I will be reporting that creates the following issue I describe below]

Hi @nicolaskulka ,

Thanks again for your work. I just tested this and there’s an improvement! I am able to log in to my website under Elementor’s maintenance mode.

Logging out however still throws a critical error but only when done from the back end’s admin bar. So if I log out from the WP dashboard log out option, I get this error:
https://app.screencast.com/FPsB4cvk18mv9
Notice the log out action includes the BuddyBoss’ member’s slug in the URL. Also, it doesn’t really log me out. I’m still logged in.

The only way I can truly log out is from the front end, it logs me out with no issues and from the link I can see that the log out action is using the custom log in page slug in the URL:
https://app.screencast.com/BcjLu4DGRRoDt

I am also correctly redirected to the “Coming soon” page I’ve set on Elementor.

My error reporting plugin is notifying me of a bunch of errors:
https://app.screencast.com/UtdV0F1UwLper

I also tested this while on BuddyBoss’ maintenance mode (instead of Elementor’s maintenance mode) and it’s the same situation except for when I log out successfully from the front end menu option, I am not shown the maintenance page of BuddyBoss. I am redirected to the custom URL log in page. Something is blocking BB from showing it’s maintenance page.

Now, when I deactive your plugin (because I thought it might be the one triggering this), and I try to log out from the dashboard, I don’t get the critical error but I’m getting a 404 error and the log out URL has the member’s slug again:
https://app.screencast.com/jXYjLb6UoR9W7
I also don’t get truly logged out, so again I have to log out from the front-end. The BuddyBoss maintenance page is also shown now.

So there must be something else going on that creates this error. I guess I should be making a ticket with BuddyBoss about this logout error.

• This reply was modified 4 months, 3 weeks ago by nyadna. Reason: Error confirmed on BuddyBoss instead

Even logging out with no maintenance mode activated gives a page not found critical error:
https://app.screencast.com/aXVuhWRbWvLTc

@nicolaskulka

I’m doing the testing at a staging site, so I’m not really locked out of my website. I keep pushing my healthy live to staging to experiment, so I don’t need to remove that file.

However, if the issue is not addressed, people might get locked out if they use the coming soon/maintanance mode and their cookies expire which would log admins out of their website with no way to get back in unless going into FTP.

Uh oh, there’s another issue now. I have my website under maintenance mode from the tools on Elementor. There was never a problem logging in through my custom log in page but now when trying to log in, I get redirected to the wp-login.php page which shows me the maintenance mode message. In other words, I am getting locked outside my website. The same thing happens when I use the maintenance mode from the BuddyBoss theme options. This was never the case before. When I try to reset the password I also get the maintenance mode message.

Is there a possibility to rollback to a previous version before these issues temporarily till this gets fixed?

Working for me too! Thank you for your prompt work, Nicolas!

I’m getting the memory exhaust issue too when I have the plugin (v. 1.9.16.5) active and try to push updates of my production site to my staging site on Runcloud (server is on AWS). This is the error I’m getting:
https://app.screencast.com/p9rY80JazRH7Z

When I deactivate it, I can sync the two with no issues.

I can also confirm there’s a conflict with Buddyboss (v. 2.6.30) because if I deactivate BB with WPS Hide Login active, the error doesn’t happen.

UPDATE:

The issue has been resolved as from version 2.2. The team was very quick and efficient in handling this issue. Great support!

I also noticed I could place an order (in my case a free trial) and the user can purchase it even if they ignore the inline verification on the checkout page.

1. How is this going to stop bots from creating fake accounts? This is the whole reason we need to verify the customer email.

2. And another scenario: If the user can access the website being “unverified”, with the automatic deletion of unverified users going on every 7 days (in my case) that means that they will get deleted accidentally, lose their online course progress and eventually complain to me because they won’t understand how it happened. How is this useful?

I’m sorry but I don’t understand the logic behind this.

Can you please explain if there’s a way to restrict login completely unless a user is verified?

Thank you.