Hello wpForo Team,
I’m experiencing a permission issue on a fresh wpForo 3.1.2 installation and would appreciate your advice.
Environment
- WordPress 7.0.1
- wpForo 3.1.2
- Fresh installation (no upgrade from wpForo 2.x)
- Forum created from scratch
- No custom usergroups or forum access sets created
- Only the default configuration was used
The problem
Administrators can use the forum normally.
Guests can also browse the forum as expected (read-only).
However, every registered user (Subscriber → Registered usergroup) is almost completely locked out.
Symptoms:
- Forum index is empty.
- “What’s New” is empty.
- “Recent Posts” is empty.
- The user cannot open their own profile.
- Opening the profile shows:
You do not have permission to view this page.
The profile widget only shows the Logout button.
The user is correctly logged in, but wpForo behaves as if almost all frontend permissions were denied.
User configuration
WordPress role:
- Subscriber
wpForo usergroup:
- Registered
Forum Access:
- Standard Access
Only one usergroup is assigned.
Permissions checked
I verified all of the following:
- Registered usergroup permissions
- Standard Access permissions
- Forum permissions
- Category permissions
Registered has Standard Access everywhere.
The Standard Access permission set contains all required permissions (View Forum, View Topics, Enter Topics, Reply, Create Topics, etc.).
Membership addon
I also tested with the Paid Memberships Pro integration disabled.
The problem remains exactly the same.
Therefore, PMPro does not appear to be the cause.
Database
wpForo → Tools → Database reports:
No Problems Found
Additional information
- The problem affects multiple test users, not only one account.
- The installation is not migrated from another server.
- The forum was created directly with wpForo 3.1.2.
- I did not modify or recreate the default Forum Access sets.
- I did not recreate the Registered usergroup.
Since Guests work correctly and Administrators work correctly, but all Registered users are denied access to almost every frontend page, I suspect that something in the internal permission resolution may not be working as expected.
Has anyone seen this behaviour before, or is there anything else I should inspect?
Thank you very much!