Forum Replies Created
-
Posts
-
Thanks, Assurer.
I do allow cookies of course, but in Chrome “third-party” cookies were blocked and there is a Do not track directive. But I checked the presence of cookies in Chrome and Firefox and found some WordPress and SWM cookies, including swpm_session_in_use, so that appears to be fine.
Hi Assurer,
No, I do not use ANY cache plugins, and from a long career in development, I have the habit of clearing browser cache every few minutes, just in case.
I *WISH* the issue were reproducible in a consistent way, because then I could give you a bug report detailing the exact steps I took. My best guess as to the sequence of events is the following:
Normally, I log in via SWPM Login button, do whatever checks I need to do at the frontend, do whatever maintenance I have to do in the Admin panel, and then close the site. The next few times I return to the site, it does not ask for a Login again, but gives me access to the protected frontend and Admin panel without asking for new authentication. This suits me well.
New behaviour as of a few months ago:
1
Every few days (or weeks), I return to my site, but when I try to access protected feature in the frontend, SWPM displays the login form, with “Session Expired” at the bottom.
2
So I enter my email address (username) and my password, it *appears to accept that*, but
3
when I click on a protected feature again, I get the line “You have to login to use this feature. Not a member? Join us!”
4
If I am foolish enough to try and enter username and pwd again, the same thing happens again and again. I go round and round, logging in, then being told I have to log in.At some point I don’t even get beyond Step 2, because instead of accepting my credentials, it just erases my password and “Session Expired” appears.
When I get worried and start looking for other solutions, I type the native WP url
https://my-site/wp-admin, which gives me the WP login window, and with THAT I can log in to the Admin area and do things in there, BUT any attempt to access something protected in the frontend starts the list of steps above.Please bear in mind that I have 500 subscribed members on this site and I can’t just start debugging in Production, de-activating plugins until something works again!
I have been wondering if new, improved security has been added to the SWPM code, that forces a “Session Expire” every (n) logins? This never used to happen. For many years I was using SWMP and there was never an unexpected forced logout behind the scenes. But I have too many customers now and no time any more to look into the code and see what it is doing.
Thanks in advance
swisspHi mbr
No, I am not using Form Builder. Also I am using the latest version of WordPress and the latest of SWPM.
In my site database I have made a few extra columns in my wp_swpm_members_tbl – of type varchar(255) – that match each textarea I have added to the Add, Edit, and the equivalent Admin forms. I have tried adding:
trim
to the code that outputs the long text, but even that does not change anything …Many thanks,
SPBy the way, there was an error in my second-last post: the membership@ address exists of course … she looks after the membership requests. But the “new member” I created (the webmaster@ address) is one that I recreate and delete every time I do tests in SWPM, so it’s not in the SWPM db until the registration online is received. At that point, the new person appears as “pending” in the SWPM db.
Hi mbr, yes, I did that! The webmaster address is not someone who is registered as a user on this particular site at all.
Hi again
I did another test, with new email address webmaster@mydomain.ch. I received the notification email in my inbox, as expected, and I’m sure the person who uses membership@mydomain.ch (our Membership Secretary) has received that notification too, as I regularly test these features anyway, especially after a new update to SWPM.
The log file shows:
[08/26/2018 10:16 AM] – SUCCESS: Member registration complete email sent to: webmaster@mydomain.ch. From email address value used: membership@mydomain.ch
[08/26/2018 10:16 AM] – SUCCESS: Admin notification email sent to: membership@mydomain.ch
[08/26/2018 10:16 AM] – SUCCESS: [MailChimp] Mailchimp integration addon. After registration hook
[08/26/2018 10:16 AM] – SUCCESS: [MailChimp] Debug data: |webmaster@mydomain.ch|First|Last
[08/26/2018 10:20 AM] – SUCCESS: After login redirection addon. Checking if member need to be redirected.The trouble is that the above proves nothing, because the membership@mydomain.ch address has not been added to my MC list, and I never received any opt-in message either. I check my spam and junk folders daily so the problem is not there.
Hello mbr and smp7,
Yes, I installed the MC add-on, got the API, put it in the field, etc etc etc.
The only diff. I can see between my SWPM setup and the “normal” one is that I never use the “complete registration” feature, because once the Membership Secretary has set the new person to Member and Active, there is nothing to complete for the user. Maybe this step has the piece of code that is needed?
Thanks,
SPYes! As I say, I don’t know WHEN my Addons screen went blank … I was just checking in there the other day and found nothing to look at! Can send a screen capture if this app allows it.
yes, i know that – can you tell me which file calls the membership list? i can hardcode it myself.
thanks.
When you go to the Admin Dashboard, then click on WP Membership in the menu on the left, it opens the list of members, with All members being the active view. I have several categories: Active, Pending, Expired, Left and All. It opens on All by default, but I want this list to open showing Active members by default. The user can click on All if for some reason he wants to see All, but most of the time we want to see Active, which is a much smaller subset of All.
Thank you!
SPWell I remember that it wasn’t always there! I had dates in the format 2016-06-19 and the users had to enter them as such. Then at some point a date-picker (calendar) became available. For our purposes this is more nuisance than help though, as every June one of the dates has to be changed manually from last year’s date to this year’s date, and not everyone enjoys scrolling down to the bottom, then past the bottom, to 2016 – just to change one digit!
For the next big batch of updates to the date, I am working on a workaround, but for now all the scrolling in the calendar is tedious.
SP
