houseminute
Forum Replies Created
-
Forum: Plugins
In reply to: [Persistent Login] conflict with Yoast 19.2Luke, 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!
Forum: Plugins
In reply to: [Persistent Login] conflict with Yoast 19.2Oops. 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!
Forum: Plugins
In reply to: [Persistent Login] conflict with Yoast 19.2Hi 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, 2022Bugfixes:
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.
Forum: Plugins
In reply to: [Persistent Login] conflict with Yoast 19.2Hi 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 522What 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 🙂
Forum: Plugins
In reply to: [Persistent Login] conflict with Yoast 19.2No 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!
Forum: Plugins
In reply to: [Persistent Login] conflict with Yoast 19.2Hi 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.
Forum: Plugins
In reply to: [Persistent Login] conflict with Yoast 19.2Thanks, 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 🙂
Forum: Plugins
In reply to: [Persistent Login] conflict with Yoast 19.2Hi 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 522We’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 ProIs 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 🙂
Forum: Plugins
In reply to: [Persistent Login] conflict with Yoast 19.2Oops, sorry – on OUR staging site. I’m certain that your own staging site is just fine, lol.
Thanks again 🙂
Hi @maybellyne. Thanks so much for your reply.
Unfortunately, deleting the plugin and reinstalling did not result in success. We continue to get the fatal error. We have allotted plenty of memory on the server. It’s a conflict, I think, not an actual deficiency of memory.
If you have any other suggestions, I’m all ears.
Since I initially posted, we’ve cloned the live site over to the staging site for some other work, so if you’d like to take a look, I could leave the site in its fatal error state if I know when you’d be able to do that.
If that’s outside of the scope of this support forum, I understand. If we cannot find a resolution, then we’ll have to wait to see if a future update will right the ship for us.
Thanks again!
Forum: Plugins
In reply to: [WP Activity Log] “Activity log database update in progress” stuckHi Robert –
Thanks for the offer, but I set the plugin to delete all its data and started over. A fresh installation of the current plugin worked great. I appreciate that this wouldn’t be an ideal approach for many people, but it wasn’t necessary that we retain previous data and, for us, it was an expedient solution. Thanks again 🙂
Forum: Plugins
In reply to: [Persistent Login] Subscribers Cannot Log OutOhhhh. I found the login code on github. Is it considered acceptable form to post it here? It’s public on github, but I don’t want to be rude by exposing anyone’s code. Please let me know, and I can upload it or get it to you another way. Thanks, sorry for the extra message.
Forum: Plugins
In reply to: [Persistent Login] Subscribers Cannot Log OutHi Luke –
Sorry for the delay in replying. I’m most appreciative of your help, but it took me a few days to get this info. Here’s what my web dev said:
“The login/logout links are part of the functionality provided by PMP. Both log in and log out are added as options to the menu system.”
PMP refers to Paid Memberships Pro (https://github.com/strangerstudios/paid-memberships-pro), which is what we use to create the paywall. Do you suppose that there’s an incompatibility there with Persistent Login?
Their login page is just a site page with their login shortcode.
I opened github and can see a bit of the info I think you want.
Their login.php is this:
<?php
echo pmpro_shortcode_login(”);
?>I do not see any code for logout, so I’m not sure how that’s handled. Sorry, my understanding of code is poor, but if you provide any code that you’d like us to try, I can have my dev do it on our staging site and we can report back.
Many thanks for your help 🙂
Forum: Plugins
In reply to: [Persistent Login] Subscribers Cannot Log OutHi Luke –
Here’s a little more info about what’s happening. Perhaps you can help us get this working again on our site:
Original Menu logout was flawless, for more than 2 years. Not sure at what version things went south – my bad for not keeping track of that – but it’s definitely not working now.
Version just prior to 1.3.21, logout issue flow was as:
Log in – go to some pages
Log out – pops you back to home page but menu still shows Logout (not Login)
Choose Logout again – presented with the WP “you’re attempting to log out of QuietSelf.com” – click log out link – you’re taken back to the home page but the menu STILL says Logout (not Login), although you’re actually logged out.
Now, following an update to WP Persistent Login v1.3.21, this seems to be the new behavior:
Log in – go to some pages
Log out – you’re taken immediately to the the WP “you’re attempting to log out of QuietSelf.com” page – click the “log out” link – you’re taken back to the home page but the menu still says Logout (not Login), although you actually are logged out.
To verify, choose My QuietSelf page, which loads and the menu now says “Login” (as it should).`
We’ve had to disable the plugin until we get this sorted, which is sad. It’s really a terrific customer courtesy.
Any thoughts or suggestions, Luke? I’m all ears.
Thanks again 🙂
Forum: Plugins
In reply to: [Persistent Login] Subscribers Cannot Log OutHi Luke, thank you so very much for your reply!
We’re not using a specific plugin, but we do have our members log in on quietself.com/login. We’re going to be modifying the menu before the end of the week, but I don’t think that it’s a menu issue. If anything, I suspect that it’s just a login page issue, which didn’t used to be an issue. Maybe due to 5.7 update? We’ll keep on it and I’ll report back if we resolve it or if it remains unresolved. We sure love using it. Such a great courtesy to offer our members. It’ll be a sad day at QS if we have to let it go.
Again, thanks so much!