Issue with previous updates – field mapping

Hi @jejonesjnr

I hope you’re well today!

There is an issue on plugin end and it’s being investigated by our developers so should be fixed with one of upcoming releases – but I don’t have ETA yet.

For now, other than downgrade of the plugin, using this code should fix the issue too:

https://gist.github.com/wpmudev-sls/9f1a22896e7318dd26d06872b8467419

You would need to add code to the site as a Must-Use plugin:

– create an empty file with a .php extension (e.g. “forminator-upload-mapping-patch.php”)
– copy and paste code into it
– upload the file to the “/wp-content/mu-plugins” folder of your WordPress installation on the server

and you’d need to “configure” the code by replacing numbers with your form(s) ID’s in both copies of this line in the code

if( !in_array( $form_id, $form_ids ) ){

and defining your custom field(s) name(s) in this line:

if ( $post_val['key'] == 'test_image' ) { //Please change test_image to your custom field name

Note:
a) if it’s about a single custom field, simply replace “test_image” with the field name
b) if it’s about multiple custom fields then you will need to replace this line with following

$fields_names = array( 'test_image', 'another_image', 'third_field' ); // comma separated custom fields names
if ( in_array( $post_val['key'], $fields_names ) ) {

Best regards,
Adam

Thank you very much for your quick response.

This is still not resolved in the latest version (1.23.3)

Hi @jejonesjnr,

I understand your frustration, and apologize for not being able to provide you with a specific timeframe for a fix. However, please be assured that our Forminator team tries to fix each bug as soon as possible.

In general, providing an ETA for a bug fix can be challenging since our developers need to consider the issue’s complexity, prioritize bugs depending on their severity, and manage their workload. Those fixes should also be checked by our QA team. This is why we could not provide a clear timeline for the specific bug you’re experiencing. Our Forminator team is planning to release the fix with v1.24

Thanks for your understanding and patience.

Kind regards,
Zafer

I appreciate the response however, this functionality worked perfectly well in version 1.22.1. Surely, if an upgrade breaks existing functionality, it should be rectified as a priority, no?

Hi again @jejonesjnr,

You are correct, this issue has already the higher priority comparing to the others, however we could not provide any ETA at the moment due to the reasons I mentioned.

Kind regards,
Zafer