Inline message of the registration form based on manual approval

Hi @jasonwang2022,

I hope you are doing well today!

We could not open the form export link as it is not publicly available, please share the code using a service such as https://pastebin.com which is free to use.

Please always make sure to use such service to share the code and don’t post the code here directly as it will most likely be unusable.

Kind regards,
Zafer

Hi Zafer,

Thanks for the advice. Can you please try this link?

Great to hear back.

Hi @jasonwang2022,

This is a known issue that our developers are aware of. A fix for this will be included in one of the upcoming updates.

Meanwhile, please try the following workaround.

<?php
add_filter( 'forminator_form_submit_response', 'wpmudev_registration_change_messsage', 20, 2 );
add_filter( 'forminator_form_ajax_submit_response', 'wpmudev_registration_change_messsage', 20, 2 );
function wpmudev_registration_change_messsage( $response, $form_id ){
	if( $form_id != 1381 ){ //Please change the form ID here
		return $response;
	}

	if( $response[ 'behav' ] == 'behaviour-thankyou' ) {
		$response['message'] = wp_kses_post( 'Your new message goes here' );
	}

	return $response;
}

You have to add the code using a mu-plugin. Please find how to add a mu-plugin here: https://wpmudev.com/docs/using-wordpress/installing-wordpress-plugins/#installing-mu-plugins

Note: Please change the form ID from 1381 to your form’s ID in the snippet. Also, please adjust this message Your new message goes here per your requirement.

We recommend testing this on the dev/staging version before putting it on the live site.

Kind Regards,
Nebu John

Hi @wpmudevsupport14

Thanks for the workaround, I appreciate it!

Can you let me know when the proper fix will be available? And do I need to remove the workaround when it’s released?

I remember the fix was mentioned earlier this year but no follow-through. It shouldn’t be a complicated fix, right?

Regards

Hi @jasonwang2022,

As the developers work on more complex issues based on priority, I am afraid an ETA on this cannot be provided at the moment. We will provide more details in the plugin change log when a fix for this is released.

Please feel free to remove the workaround once a fix for this is officially released.

Kind Regards,
Nebu John

Understood. Thanks Nebu.