[neversettle]

I dug in and found what I was looking for.

In /wp-content/plugins/user-meta/controllers/pro/umPreloadsProController.php on line 153 I changed this:

if( !empty( $login[ 'login_page' ] ) && !empty( $login[ 'disable_wp_login_php' ] )){
wp_redirect( get_permalink( $login[ 'login_page' ] ) );
exit();
}


To this:

if( !empty( $login[ 'login_page' ] ) && !empty( $login[ 'disable_wp_login_php' ] ) && $_GET['action'] != 'postpass'){
wp_redirect( get_permalink( $login[ 'login_page' ] ) );
exit();
}


And this fixed it. Hopefully someone else benefits from this as well.

[neversettle]

Bump. Anyone?

[neversettle]

Quick update – I also had to modify validationEngine.js line 27 because .live is deprecated in new versions of jquery. I changed it

FROM this:
$(“.formError”).live(“click”, function() {

TO this:
$(“.formError”).on(“click”, function() {

Validation wasn’t working at all until I did this (even for built in custom validation like email), but it was really hard to catch because the page refresh on submit reloaded so that it looked like there were no errors. Basically jquery couldn’t hook the submit event to any of the validation classes.

Hopefully this saves someone else some hair pulling.

This is a BUG in the current version of user meta pro (1.1.3).

[neversettle]

Can’t thank you enough @karbon! That is a massive help – so much appreciated. I think it will help others too. When the features of the pro version said field validation I thought there would be a lot more included than what the free version had. But unless I’m missing something it was the same (non-existent). I’m not even sure what the different field types are for (like I can put letters and whatever I want in the Phone field… makes no sense).

Anyway – truly grateful that you shared in such detail what worked for you. I’m sure I can get that similar approach to work too. All the best!

[neversettle]

I ran into this too. Seems like a bug. Clearing cache worked for me, but I would have never thought of that for such a basic core functionality. Thanks for posting what you found!

Seems like there should be a way to make sure this doesn’t happen in the code so that the save notification isn’t misleading in the Forms Editor.

[neversettle]

@karbon can you post more specifics on how you solved this? we’re wondering the same thing. Thanks!

[Author]

Posts