conflict with Yoast 19.2

Oops, sorry – on OUR staging site. I’m certain that your own staging site is just fine, lol.

Thanks again ??

Well that is a compliment isn’t it! Firstly, apologies for your issue, and thank you for using (and keeping activated!) Persistent Login.

This is the first report of a conflict with Yoast, and I personally use Rank Math myself so haven’t tested the two plugins together.

I’ll install Yoast and see if I get the same issue on my end. Can I ask if Yoast & Persistent Login are enabled on your staging site now? As I’m not seeing any fatal errors?

It may also be worth listing your website’s setup (Linux/windows, PHP version, WP version and the theme you use).

Please do not share any login details with me on this forum or via email. It is against the rules for support to free users. But we should be able to work this out without needing any access to your website ??

Thanks,
Luke

Hi Luke, thanks so much for your reply.

As of right now, only Persistent Login is activated, and Yoast is deactivated. Here’s the error we get when I both are active:

Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /srv/users/live2/apps/quietself-live/public/wp-includes/class-wp-user.php on line 522

There has been a critical error on this website. Please check your site admin email inbox for instructions.

Learn more about troubleshooting WordPress.

Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /srv/users/live2/apps/quietself-live/public/wp-includes/class-wp-user.php on line 522

We’re quite sure that memory is not the actual issue. We have allocated 512, which should be adequate.

To answer your question:

Umbutu
PHP 7.4
WP 6.0
Nirvana (child theme)
Elementor with Elementor Pro

Is there any other info I can provide? We’re currently doing some tests on the staging site, but I would be happy to leave it in its fatal error state if I have a general idea when you might be able to take a look at it.

Just to fill in any gaps, I did reach out to the Yoast developers who said to allocate more memory, lol.

Thanks again. Looking forward to any insights and/or info on when to put the staging site into its fatal error state ??

Great, thank you for that information. The error message will help to identify where the issue is.

Please carry on with the work you’re doing on the staging site, I just wanted to see the actual error message but you’ve provided that so thank you.

The only other information that would be useful right now is to know what settings you have enabled on Persistent Login. Are you using the Limit Active Logins feature, or just the Persistent Login feature? Does the error occur if you switch off Active Logins?

I will start looking at this tonight for you, but as Yoast is quite a large plugin, it could take time for me to find a conflict and fix it. I would expect this could take a week or two to fully resolve, just so you’re aware.

Thanks, Luke. Totally understandable that it will take awhile. Just to reiterate, Persistent Login with Yoast 19.1 and earlier showed no conflict. Whatever they did in 19.2 began our tale of woe.

I prepared 3 screenshots before realizing that I cannot upload them here. So, here’s the info:

1. Hide “At a Glance” dashboard stats is NOT checked.
2. Allow duplicate sessions is NOT checked (that we know of, no one is having trouble with multiple logins)
3. Limit Active Logins to 1 is NOT checked.

Per your inquiry, I did try activating the Limit Active Logins to 1 option and then updated Yoast to 19.2. This resulted in the fatal error. So…yeah, it’s not that, lol.

If there are any other tests to try, just let me know. And if Yoast releases an update, I’ll give it go and report back forthwith.

Super big many thanks ??

Hi Luke –

As promised, when I noticed a Yoast update (1.93), I applied it. Unfortunately, it continues to result in a fatal error for logged-in admins only:

Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /srv/users/live2/apps/quietself-live/public/wp-includes/class-wp-user.php on line 522

Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /srv/users/live2/apps/quietself-live/public/wp-includes/class-wp-user.php on line 520

Hoping that this feedback might contribute to a solution.

Thanks so much.

Hi,

Apologies for the delay on this, it is still something I’ve been looking at but haven’t had the time to find the solution just yet.

Do bare with me on it. I am looking at it for you. Thanks.

No worries, Luke. It’s completely understandable that the fix will take time. For now, we’ve disabled Persistent Login and instead have assigned login length at the code level. However, there are fine features in Persistent Login we look forward to again enjoying. We’ll circle back in the future to see if perhaps we can dip back in. Many thanks for your fine work!

Hi Luke –

I saw that there was an update to Yoast (19.4), so I did try it with a new installation of Persistent Login. Same issue:

Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /srv/users/live2/apps/quietself-live/public/wp-includes/class-wp-user.php on line 522

Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /srv/users/live2/apps/quietself-live/public/wp-includes/class-wp-user.php on line 522

What I find especially puzzling is that two long-time admins here in the U.S. get this error, while a much newer admin in Turkey does not. Odd?

Anyway, I hope that this is informative to your ongoing work on Persistent Login. It’s a great plugin. We miss it and hold hope that one day we’ll be able to use it again.

Thanks ??

We’re experiencing this conflict, too. Looking forward to the update. Thanks for a great plugin!

We’re experiencing this conflict, too. Looking forward to the update. Thanks for a great plugin!

Thanks all for the confirmation. This is being looked into for everyone, apologies it’s taking a while!

Hi,

Could everyone please tell me what the PHP Memory Limit is on their website? And also how many users you have on your website please?

Can you also please confirm if there are only certain users getting a 500 error, or if all users are getting the error?

You can find the memory limit from: Tools > Site Health > Info (tab) > Server (dropdown).

User count can be found from Users > All Users.

Thanks,
Luke

• This reply was modified 2 years, 2 months ago by lukeseager.

hi Luke,

for us it’s:
PHP memory limit 256M

number of users is: 80

Hope this helps!
Kind regards,
Jolanda

Hi all,

I’m unable to replicate this issue on any local or remote server after a lot of testing.

Is there another common plugin or theme being used by everyone?

• This reply was modified 2 years, 2 months ago by lukeseager.