• Resolved macaraigmichelle

    (@macaraigmichelle)


    Hi, we are getting this error after registration: This is not possible for security reasons. For your assistance please

Viewing 15 replies - 1 through 15 (of 17 total)
  • Thread Starter macaraigmichelle

    (@macaraigmichelle)

    Thanks for this. I have just rolled back to the previous version, hope it gets fixed

    How do I roll back to the previous version?

    Thread Starter macaraigmichelle

    (@macaraigmichelle)

    You may install the plugin: WP Rollback

    Rolled back. THANKS.

    Plugin Support Ultimate Member Support

    (@ultimatemembersupport)

    Hi @macaraigmichelle,

    Do you have any security plugins installed?
    Please do a quick conflict test so we can rule out any conflicts with your theme or one of your plugins.
    Here is the doc on how to do a conflict test.

    Regards.

    Thread Starter macaraigmichelle

    (@macaraigmichelle)

    Hello, I cannot revert to the default theme because we are running an online site where a lot of people are currently using it, so I just tried deactivating most of our plugins, but still I got the same error. Only when I revert back to Version 2.1.8, the registration works again.

    RoscoeS

    (@roscoestephen)

    It would be great getting a solution to this problem, apart from the automated message that you get from Ultimate Member support. It is really disappointing searching the support forum and finding their response is

    1. Do you have security plugins?
    2. Do a conflict test?

    Then no response from them?

    I had this issue and it was related to the default role that I set on my registration form. I removed the role field upon registration and used the “New User Default Role” selection under Settings -> General. That worked for me. Hope it helps someone.

    Thread Starter macaraigmichelle

    (@macaraigmichelle)

    Hi apabiona, thank you. Unfortunately it did not work for me, we have several user roles so we need to have the user role selection in the registration form. Seems that there’s a conflict on the user role field after the 2.1.9 update.

    Rolling back to 2.1.8 did not fix this issue for me. Has anyone else had any success?

    I was previously using 2.1.8 with no issues.

    I’m getting the same issue on my site with new users trying to register. Need a fix asap on this please.

    RoscoeS

    (@roscoestephen)

    In the same boat. Hope to get a response from Ultimate member support but it looks like this definitely does not warrant their time. It is disappointing since the last support response was 6 days ago.

    Hey, gang. I’m pretty sure I’ve solved this.

    The problem is with the file:
    /includes/core/class-form.php

    The problem has to do with when adding the Roles (Dropdown) field that has custom roles added via Ultimate Member. This field sets role options, but as the title of the custom roles. When a user attempts to register, it checks the role selected against the options set for the field. The problem is on line 587 in the plugin the function custom_field_roles returns the titles of the roles and then line 395 compares the slug for the role against the titles of the roles. No match is found and the registration fails because the plugin thinks a user is attempting to register with a non-existent role.

    Solution:

    Change line 395 of /includes/core/class-form.php form this:

    ( ! in_array( $role, $custom_field_roles, true ) || in_array( $role, $exclude_roles ) ) ) {

    to this:

    ( /*! in_array( $role, $custom_field_roles, true ) ||*/ in_array( $role, $exclude_roles ) ) ) {

    PLEASE NOTE: This is a hack and not how things should be done. For the time being it’ll get your registration back up until the Ultimate Member team rolls out a solution. The flaw with the solution is that someone could maliciously register with a non-existent role.

    Same issue. I have 12 sites that use UM 2.1.9 and all have this issue. I have rolled backed to 2.1.8 as a temporary fix.

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘This is not possible for security reasons’ is closed to new replies.