October 8, 2021 at 8:22 pm #121256Andrew FriedemannParticipant
I have been very happy with this plugin, but updated yesterday now certain roles just get continual 404 messages. Using 18.104.22.16861
Where can I find the previous version to roll back and see what happens. Also how do I do so.October 8, 2021 at 8:24 pm #121257
Sorry about that.
Can you please make sure that, your role has all the ‘read_others_’ capabilities checked?
Please let me know if you don’t know how to do this.
SyamOctober 8, 2021 at 10:19 pm #121265Andrew FriedemannParticipant
This is not helping unfortunately – I am also getting a @too many redirects’ message when someone tries to visit the site. Disabling the plugin allows access, but I need it working for my site.October 8, 2021 at 10:46 pm #121266
One other place you can check is individual posts permissions, by editing it.
Do you think you can give me access to your site?
SyamOctober 11, 2021 at 7:44 pm #121427Dirk MaassParticipant
I have the same problem caused by WPFPro. Log in to user account leads to 404. All our sites with WPFPro are affected.
DirkOctober 11, 2021 at 7:48 pm #121435
Can you go into the edit page of the post you are having issues with and check what is the view access for the role? It will most probably be view access denied with deny action set to 404.
If that is the case, then you can reset your permissions. To update multiple posts together use Bulk Edit.
Please let me know if you need any help.
SyamOctober 16, 2021 at 4:05 am #122292Jordan DackParticipant
Has there been a fix? I am experience exactly the same thing. How can I roll back to a previous version of the plugin? Thanks.October 16, 2021 at 5:35 am #122301Eli LinaresParticipant
Looking for the same here, if you find out, please let me know.October 16, 2021 at 9:00 am #122318
Hi Jordan & Eli,
Can you please update to the development version and follow the debug instructions to find from where the issue is coming?
You can download the previous version from your purchase history.
SyamOctober 18, 2021 at 11:46 pm #122523Sebastian RouxSpectator
I’ll add something to this conversation.
We used the Beta and Updated to the Full Release Pro Version.
What we now see is, that CPT readings arn’t working properly (like adding new CPT). After checking the Rolepermissions of the Administrator we could see that some Permissions are missing.
You can’t even activate them anymore.
What I did:
-> Add new Role -> Clone from Administrator -> Name it SuperAdmin (or whatever you like) -> Activate everything (mostly this terms: Uses "manage_categories" capability. You can Customize Capabilities by providing a capability slug.) -> Saved Role -> Updated Role -> Checked the Permission count on the old Administrator (now gained 20 more permissions) -> Checking CPT = Working
When I created the Clone and saved, the original Adminrole auto updated itself and gained all permissions.
Reason for the behaviour from the ppl here:
404 or redirects is because you’ll get a 403 when you go on a Page and the settings (404 shown or redirect) are determine what will happen.
It might help discover the Issue, since we didn’t update our CPT’s or any other Code.October 19, 2021 at 7:38 am #122563
Thank you for the detailed info.
To add missing capabilities to “Administrator” role, try restoring it.
SyamOctober 19, 2021 at 9:12 pm #122645Sebastian RouxSpectator
That didn’t worked, I tried that before I did above.October 20, 2021 at 2:44 am #122672Magnus JohanssonParticipant
My site also got affected by the latest version 3.x of the plugin.
1) All our users that only was assigned a custom created role, were unable to see any content of the front page etc.
2) Some pages are highly secured so that only a specific role can read the content. For these pages, everyone got 404/not found, even myself when trying access them as Administrator. I was able to see the title of the pages under WP-Admin / Pages / All pages, however, there was not even a link to click in order to edit the page.
When downgrading to the previous 2.x version, everything works again as expected.October 20, 2021 at 9:40 am #122702
Have you tried the debugging instructions?
SyamOctober 27, 2021 at 6:24 pm #123254
There was a bug fix to address a similar issue.
Please test with version 3.1.0 and see if it fixes your issue.
- You must be logged in to reply to this topic.