conflict with Yoast 19.2

Hi Sorry but we decided to give up on this.
Thanks for your time trying to solve it.
Kind regards,
Jolanda

Hi Luke. Two things.

1. To answer your question, we’re using a pretty low-profile theme – a child theme of Nirvana by Cryout. Iit’s unlikely that anyone else is using this same one.

2. In regards to login pages – yes! We use Paid Memberships Pro, and it has its own login page. So, our login is controlled by a shortcode.

Lastly, I did note in the changelog to last update to Yoast:

`19.7.1
Release Date: September 20th, 2022

Bugfixes:

Fixes a bug where a fatal error would be thrown in combination with certain plugins that change the standard login page URL.

Other:

Changes the copy in the robots.txt comment.`

Now, our login page is just /login, but with PMP routing things around based on level, it’s possible that this has been the issue.

No clue about others, but I wanted to provide feedback about our situation. We’ll likely stay with the code changes we made to keep users logged in, rather than returning to Persistent Login. At this juncture, it doesn’t seem feasible for me to continue testing, since I don’t have a beta site on which I can remove our custom log-in code to fiddle with it. But I’ll chat with my coder to see what he thinks. I do very much like the control features offered in Persistent Login, and I do miss them. Our custom solution is very vanilla.

Hoping this feedback helps. You’re a superstar for sticking with it. I’m hoping that Yoast has fixed their glitch completely.

Oops. To clarify: PMP does not have its own login url. Our url is still /login, but the content of that url is a PMP shortcode. I didn’t phrase it correctly above. My bad!

Hi all,

Is anyone able to test applying the steps outlined in this guide on the persistent login website? It will reduce the speed of the user count, in turn reducing the amount of memory used: https://persistentlogin.com/how-to-change-the-speed-of-the-user-count/

Hi Luke,

We are also encountering this issue on all three of our sites. Yoast/Persistent Login conflict is the culprit, but as previous users have said, only Yoast v19.2 onwards. We’ve delayed updating Yoast for some time as a result, but soon we’ll have to abandon the Persistent Login plugin, with much regret. Any updates on getting this resolved?

Thanks!

Andrew

Hi there,

Can I ask if you’ve tried the suggestion above your post, to reduce the speed of the user count?

I am struggling with this issue as I’m not able to replicate the problem on any server and the change causing the issue was created by Yoast rather than Persistent Login.

If people can try my above suggestion and let me know how they get on, there might be something I can do to help the issue, but the problem will still be present in Yoast SEO.

Thanks,
Luke

Hi Luke,

I’ve now tried this (reducing the count speed to 150 as outlined), and I’m sorry to say it has made no difference. Let me know if you have any other ideas.

Best,

Andrew

Hi Luke. I planned to upgrade to premium but I too have now have this issue with Yoast and WP Persistent Login. For me the other plugin I have found to create with issue is Wordfence. When any of these 3 plugins is deactivated my site works. However, with all three I get an error 500.

Strangely on another site on my same server with all three activated it is working. I checked and all of the configurations in wordfence, yoast, and wp persistent links are the same.

This is a strange issue. I thought I would provide this additional info so you can continue your efforts. Several people are having the same issue.

Luke, we also were using the Persistent Login, Yoast and Wordfence. However, in my experiments – wherein I activated Persistent login and then, one by one, reactivated each plugin we require, including WordFence – we did not encounter the same trifecta as @cfebrian. For us, the conflict seemed to be isolated to Persistent Login + Yoast. With solely those 2 plugins active, we got the error 500.

Unfortunately, we no longer have Persistent Login installed, and we’ve adjusted our code to keep people logged in (but without the elegance and options of your wonderful plugin), so I’m unable to provide current viable testing.

Thanks!

Hi all,

I know this has been a long time coming, but I believe that I have found the conflict with Yoast SEO and have pushed an update today.

Please can you let me know if you are still having issues with Yoast SEO.

Thanks,
Luke