- This topic has 3 replies, 2 voices, and was last updated 12 years, 7 months ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP eMember › WP eMember General Questions › WP eMember and Word Press log in persistance
I am using WP eMember and I am very happy with it except for one thing. There appears to be some disconnect between the membership plugin and the my forum login status which I think uses Word Press to determine if someone is logged in or not.
The widget that reports that the user is logged in after returning to the page from a bookmark, whereas WP and SP has other ideas.
This would indicate that the two are operating independently until an action is taken on the part or the user; for instance if the user uses the widget to log out and then back in again then WP/SP and the membership plugin all agree and all is well.
Of course this is not ideal and I get grumbled at by my forum users.
So does anyone have a solution? Also is there anyway of making the WP login persistence quite long?
Conrad
Are you using a caching plugin? Which forum plugin are you using? When someone lands on a page following a bookmark, they are not staying logged into WP anymore?
I am using simple-press and no I am not using a caching program. Simple-press uses the WP login to detect whether a user is logged in or not. There is a disparity between the widget log in status and the actuality of whether a member is logged into word press or not.
You can test this out at http://abftest.co.uk there is a log in that I provided using the form on the 2nd April, if you no longer have it please email me.
Regards
Conrad
eMember uses it’s own cookie to track returning members. I think whats happening is that when a member returns after some time, his WordPress user login cookie gets expired so he is no longer logged into WordPress but eMember’s login cookie is still valid so it shows that the member is still logged in to eMember (which is correct but I see the issue arising from it).
Can you please verify if above theory would explain the behavior you observed? Once I receive confirmation from you, I will make some tweaks in the plugin to address this scenario.