• I’m currently upgrading to 2.0.7 and, so far, it’s been smooth (much nicer, good job!) with one exception.

    In order to allow our users to change their usernames (something neither UM nor WP allows easily), I created a second UM Registration form that an already-logged-in user can complete (putting a new email/username, and their current password which gets validated). I then wrote some hooks that, post-registration of this “new” user, would copy meta data from the old user, disable the old user, and then send the confirmation email to validate the new user email. This was, for us, a great work-around to allowing users to change their core username/email, and why I love UM (actually thinking of purchasing it for the extensions).

    But, as of 2.0, registration forms now seem to have a check in the core plugin code for logged in users (I think in class-shortcodes.php). Which means my work-around I have no longer works.

    Is there a way I can override that check, and disable it for a specific form or just in general? Is there a hook or filter I can use for this? Or is there a way to have a custom version of class-shortcodes.php without modifying the original code?

    I would hate to modify the original code, as it’ll break when it’s time for an upgrade.

    Thanks!

    • This topic was modified 6 years, 7 months ago by pbarmak.
Viewing 1 replies (of 1 total)
  • Were you able to solve this?

    I would like to do something that requires this validation to be a little more sensible.

    I have different user roles and different registration forms for each role. Ideally, I would like to allow an already logged in user to register for another role via the form and if they are already registered for the role that the form is attached to – then show the error message.

    But I suppose disabling this validation message altogether is not a bad idea either.

Viewing 1 replies (of 1 total)
  • The topic ‘Already Registered: Can We Disable This New Check?’ is closed to new replies.