danMWD

I had made the change to the version of jquery by “removing” (dequeue) it using appropriate code from within my functions.php file. The new version of jquery in my case (because I wrote the actual code) was added back in inside of the header.php file, but I could have also added the new version from within my functions.php file.

I suspect the functions.php file is where you may want to look but if you are using a 3rd party theme you may want look for other files that are called by the functions.php as the dequeuing may also have been done there!

It may also be that this is done from some kind of plugin or interface/dashboard that came with your theme.

Short answer: Look for the dequeue of jquery …

• This reply was modified 5 years, 3 months ago by danMWD.

Hi Hannah

Apologies for wasting your time – I managed to track down the issue. Eventually I got the form working on standard Storefront (I have no idea why it was not working there).

In the end the issue was to do with the version of jQuery I was using. I had over-ridden the standard version of jQuery that comes with the latest version of WordPress with jQuery 3.4.1 – this was working well with all my other separate functions and code that requires jQuery. When I removed the replacement and let the normal version of jQuery take over the issue went away…

Thank you for your quick response to my dilemma and apologies again for wasting your time…

Thank you for your reply. I understand you are not able to provide support for customising the plugin. I have also had a look through the links you kindly provided but I am not finding the function or method that is used to filter the wp_user_query search results. Would it be possible to point me at the specific script/file that I can look at over-riding for returning search results without the “wildcard” search.

Thank you again for your time on this matter.

Could you confirm that there will be documentation for the new version of PB and that the documentation will include information on the functions and hooks such as wppb_register_userdata or profile_update OR their new equivalents?

Thanks again for your support.

Thanks for your response.

Could you confirm too that the “errors” I mention above to do with the email being left blank and the password reset in the edit profile area are also going to be resolved in the new version or perhaps if I am misunderstand something and the errors I mentioned are just happening to me. Either way if you could confirm that would be great.

Looking forward to seeing the new version.

Thank you again for your time on this matter.

Have been working on this problem myself. Perhaps there are no hooks available that do what I want, and obviously the original question maybe somewhat hard to answer without knowing the specifics of the other plugin but I have added this to the login script of Profile Builder – it seems to be doing what I expect but I wanted get an opinion as to whether it is safe and/or if there are any other potential issues:

$other_plugin_login = wp_signon( array( 'user_login' => $un, 'user_password' => $pw  );
if ( is_wp_error($other_plugin_login) ) {
	include_once(ABSPATH.'wp-admin/includes/plugin.php');
	if (is_plugin_active('better-wp-security/better-wp-security.php')) {
		$username = $un;
		$_POST['log'] = "1";
		$_POST['pwd'] = "1";
		$nbp = new ITSEC_Brute_Force();
		$nbp->execute_brute_force( $username );
	}
}

Any advice is much appreciated. Thanks.

correction: i meant the wp_signon function not the $wppb_login object.

I have made some advances in my previous issue, by using a counter to allow the function to only run once but I’m afraid I am also having some issues with further issues with the edit.profile script.

Specifically when an email is set to be required and a user edits their profile. If they do not put in a proper email the system returns an error, which is as expected – however if they leave the email field blank – the system doesn’t return an error but a message saying the profile was updated (although it actually isn’t). I believe this is an issue with the if statement on line 332 (or there abouts) that checks to see if an email has been “posted”. I am not 100% sure but I don’t think this if statement is necessary as it is already inside the “if check” to see if the email is required.

Perhaps you could let me know if I am correct. I am reluctant to remove the code myself – because any updates would need similar treatment if they are not fixed.

The other issue seems to be when a user updates their password inside the edit profile page. It seems to work the first time round then if they want to update the password again using the form that is presented after the first update it doesn’t seem to work – no update message is produced. The 3rd time and every other time (5th, 7th etc) seems to be OK. Not sure what is causing this or if it is just me. Perhaps it is something to do with the nonce?

Also could you tell me the equivalent filter for password reset – so I can make sure the password is strong. The example below is for when a user registers – but I am not able to find the equivalent filter for resetting the password.

add_filter(‘wppb_register_posted_password’, ‘verify’);
function verify($password){
/* verify password */
if (strlen($password) < 20)
add_filter(‘wppb_register_extra_error’, ‘nMessage’);

}

function nMessage(){
return ‘NEW ERROR MESSAGE HERE’;
}

Thanks in advance for any tips.

Apologies – I appear to have found what I was looking for: profile_update.