Thank you for testing it without the multiple roles, so we can rule out that is the problem.
Do you have more conditions/restrictions than the 3 groups depicted in the first screenshot? If so, could you show me a screenshot of the rest?
The latest release introduced the possibility to redirect to custom URLs, instead of just pages, and it improved the way levels are retrieved for each user. But looking at the code again, I cannot find anywhere where it could deny access for authorized users.
If you have a backup, you should be able to downgrade without any problems. If you don’t have a backup, it might be a little harder to get the previous version: You’d need to clone the plugin at Github and fetch its submodules: https://github.com/intoxstudio/restrict-user-access
Thread Starter
kbrian
(@kbrian)
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?
Thread Starter
kbrian
(@kbrian)
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
@kbrian
I am glad that we found out that it is not a bug in Restrict User Access, as I simply could not see where in the code it went wrong 🙂 I hope the problem with the “disconnection” between the application layers is easy to resolve!
If you have any other questions, do not hesitate to open a new support thread.
And if you have time, it would help me a lot if you could rate the plugin here: https://wordpress.org/support/plugin/restrict-user-access/reviews/ Thank you
