Hi @carlosmarugan, thanks for the clear details!
A couple of quick checks first:
- Members doesn’t force “Subscriber” at registration. It only provides/edits roles. When a user is created, WordPress (or the form plugin) assigns the role.
- Please confirm Settings → General → New User Default Role isn’t set to Subscriber in a way that overrides your form’s choice.
- In Fluent Forms → User Registration feed, make sure the User Role mapping is explicitly set to your role’s slug (e.g. organizer), not just the display name.
If you still see “Subscriber” with Members active:
- Try a quick conflict test (temporarily leave only Members + Fluent Forms active) and retest the same form.
- If the role still flips back to Subscriber, it’s likely just a hook priority/order issue during user creation rather than a hard conflict.
You can also set the role after the form finishes by running the change later in the hook order (this ensures nothing else overwrites it). For example, attach your role assignment to the registration event with a higher priority (e.g., 999) and make sure you’re using the role slug organizer.
Regards,
Hi @omarelhawary
I had already verified everything you say and continue creating users as subscribers. The only thing that makes it work correctly is deactivating the plugin. It’s very strange.
I have WordPress configured so that users who register do so with the ‘artist’ role by default (not with subscriber)
I have tried the code with priority 999 but it continues to create it as a subscriber.
add_action(‘fluentform_user_registered’, function($user_id, $form_data, $form) {
if ($form->id == 8) {
$user = new WP_User($user_id);
$user->set_role(‘organizador’);
error_log(‘Rol asignado forzosamente a: ‘ . $user_id);
}
}, 999, 3);
I don’t know what else to try.
Any ideas?
Thank you
Hi @carlosmarugan,
Thanks for your patience while we dug into this!
Please try this fix:
- Move the file: Move the file fluent-forms-members-fix.php to: /wp-content/mu-plugins/. This ensures it always loads and won’t be affected by plugin updates. You can download the file from here: https://gist.github.com/omaraelhawary/2c296247feda482d7b0b5322f78aa2db
- Customize as needed:
- Line 46 → change the form ID (8) or role slug (organizer) as needed.
- Line 56 → adjust the fallback role if you prefer a different default.
- Testing:
- After moving the file, submit a new registration through your Fluent Form.
- Then check your wp-content/debug.log file for messages like:
- Fluent Forms Role Fix: Stored role…
- Fluent Forms Role Fix: Applied role…
- These log entries confirm that the fix is working correctly and the role assignment is being applied as intended.
Looking forward to hearing back from you!
Hi @omarelhawary
Thanks for your reply.
I’ve finally discovered that the cause of the conflict between the two plugins is the Members extension: Members – Role Hierarchy.
Once I deactivated it, the users were created with the role that was configured.
I hope this helps someone else.
Thanks.
Carlos