kbrian
Forum Replies Created
-
Hi Joachim
I think you’re off the hook. I downloaded your full GitHub commit from
July and replaced the live SFTP files. Saw the loss of features but still experienced the issue. I now believe the error is caused by a disconnect between our Membership database application and WordPress where logging in is successful as a member but not communicated as being logged in to WordPress.I appreciate your assistance and replies and have reverted to updated version of your plugin. Thanks again.
Kim
Hi Joachim
Here’s shot of all restrictions for that level: https://imgur.com/a/eEmhr
Although we’ve had members complain so currently created another two rules, one to extent access to let anyone access the content to by time sorting it out and another locking down a test page to troubleshoot on.
3 levels: https://imgur.com/a/jvhre
test rule: https://imgur.com/a/ufCMr
Test page accessed by admin: https://imgur.com/a/EBdbc
Test page results in redirect: https://imgur.com/a/Qb10v despite that user having just the subscriber role.I’ve brought it right down to rule thing out and still don’t know what’s going wrong. My next thought is to try restrict to a role other than subscriber. Again as a process of elimination.
We do have pre update backups but as I mentioned we cannot revert due to significant daily member purchases and events etc. It would be very tedious to try restore parts on the files and not others.
I will have a look at the GitHub files.
Any ideas what else to try?
Thanks so much for replying so fast. Apologies for hijacking the question. It is indeed. aMember is a paid solution connecting to WordPress via plugin. Their system hasn’t updated in ages but if you don’t think the error is a from your plugin I’ll contact their support. Thank you for your response.
Here’s screenshots and proof…
Here are two users. One with Subscriber role and one with 2 roles (Subscriber and ‘aMember Active’): https://imgur.com/a/FZe90
(Note aMember Active is lower than Subscriber – I believe this second role is why it’s denined)Here’s the Restrict User Access plugin restricting users below ‘subscriber’ to not access ‘comps and opportunities page’
When logged in with the test user who has 2 roles, it redirects me:
But the user who’s ONLY a subscriber, it works:
Please review changes from previous update. The highest given role needs to trump the lowest given role. It’s currently blocking users with aMember Active role even if they also have Subscriber role. This is cause issues as our membership application is fairly complex and it needs to have both of some users.
I think I’m having the same issue. It was working fine up until the last update. Now all the users with 2 roles don’t have access to the restricted pages.