Hey @nikbond,
Hope you’re well.
I tested this in my test environment and yes I can replicate the issue. So I just reported this to our developers, I am sure it will be fixed one of the next releases but until that time if we can find any hotfix I will share with you in this thread.
Cheers,
Oguz
Thread Starter
Nik
(@nikbond)
Hi Oguz
Thank you for confirming this – it took me a while to realise that it was the plug-in causing the error and not my coding!
I’ve downgraded to the previous version for now but would indeed be very grateful if you can let me know of any available fix for this.
Warm regards
Nik
Thread Starter
Nik
(@nikbond)
Hi Oguz… or anyone who can help.
Is there any update to this yet? I can’t upgrade to version 4.1.2 until it’s fixed.
I’ve even tried comparing the two versions (4.1.1 and 4.1.2) myself but there are a lot of changes and it’s hard to see where the problem could be occuring.
Just to re-iterate, error messages are no longer being shown on the registration page eg. if the user name is left blank, instead of showing “Please enter a username”, the sign up fails and a red/pink bar appears over the user name field but no actual error message is displayed.
You’ve identified this as an issue yourself. After 5 weeks, is there any chance of a hotfix (if not a full update)? It’s quite a major issue for most people I would think.
With many thanks in advance and here’s hoping…
Thread Starter
Nik
(@nikbond)
Well… I think I’ve fixed this… and just in case you, or anyone else, is interested, this is what I did…
Locate -membership/app/addon/buddypress/class-ms-addon-buddypress.php
Replace lines 542 to 555 with –
private function _create_action_error_cb() {
$bp = buddypress();
if ( ! empty( $bp->signup->errors ) ) {
// There is error, so show errors using action hook
foreach ( (array) $bp->signup->errors as $fieldname => $error_message ) {
add_action( 'bp_' . $fieldname . '_errors', create_function( '', 'echo apply_filters(\'bp_members_signup_error_message\', "<div class=\"error\">" . stripslashes( \'' . addslashes( $error_message ) . '\' ) . "</div>" );' ) );
}
}
}
This is the function as it was in the previous version, which seems to work fine. Not sure why the updated two functions don’t work (it seems that one function has been split into two) – I’ll leave that to your developers to figure out. At least now I can upgrade and take advantage of the other features in 4.1.2 😉
Hope this might be of some help to someone.
Hello @nikbond,
I’m really sorry for the huge waiting time here, somehow we missed this thread.
I’ve already informed our developers about your fix though.
Warm regards,
Dimitris
