attach file function not working on form

Hello @karlcw

Hope you’re doing well today! Sorry to hear about the issue you’re facing with Forminator Upload field.

Thank you for sharing information from the debug.log. I see that these are mainly warnings and should not affect the functioning of the form itself ideally.

I was able to replicate the issue on the page you’ve shared, I noticed that the issue seems to be occurring as a result of some conflict on your site. I am mentioning this because I noticed when the form loads, there is a console error logged on the page – please refer to the screenshot here: https://monosnap.com/file/zItihcEd3boLKFHtQW6DdFkHRTvA58

I tried to replicate the same issue on my lab site with Divi theme and adding a form with the upload field – and it worked fine without any issues also, the console error was not present. This means that the issue is isolated to your site.

In this case, a good approach to troubleshoot the issue further will be to create a development/staging site which will be an exact replica of your current site and perform a full conflict test. You can refer to the guide on how you can perform a conflict test https://wpmudev.com/docs/getting-started/getting-support/#conflict-test

This handy flowchat will help as well: https://wpmudev.com/wp-content/uploads/2015/09/Support-Process-Support-Process.gif

Basically, on your staging site, you will need to deactivate all the plugins and theme except the Forminator plugin and check if the issue is resolved, if yes, you’ll need to activate one plugin at a time and replicate the issue – the last plugin/theme that you activate after which you notice the issue could be the plugin/theme that could be conflicting with the Form.

In case you wish to perform the test on the live site it will be a good idea to make a full backup of the site and then proceed with the tests.

Furthermore, if you notice the issue is still replicated after deactivating all the plugins and switching to a default theme, please share the form export with us so that we can import it and investigate the issue further.

To share the form export
– Navigate to the “Forminator -> Forms” page in your site’s back-end
– click on a little “gear” icon next to the form in question
– select “Export” option
– copy given export code and paste it at https://pastebin.com
– include link to that paste in your response below.

Note: this export will not include any data that is already submitted – they’ll stay safely on your site and we don’t need them anyway.

Kind Regards,
Saurabh

Hi @karlcw,

I gave a quick check and it appears the issue is occurring due to an outdated library used in the “My Sticky Elements” plugin for intl-tel-input ie v 17.x, while with the latest update in Forminator, it uses an updated library ie v 24.x

So hence you notice the conflict. The issue is more specific due to conflict with outdated intl-tel-input libraries .

Would recommend you to bring this further to the My Sticky Elements support’s attention so this could be sorted out of the box.

You can check and see if the following code helps as a workaround which would remove the library on pages where forminator form loads:

<?php
function wpmu_dequeue_intl_tel_input() {
    global $post;

    if (is_singular() && is_a($post, 'WP_Post')) {

	if (preg_match('/\[forminator_form/', $post->post_content)) {
            wp_dequeue_script('intl-tel-input-js');
        }
    }
}
add_action('wp_print_scripts', 'wpmu_dequeue_intl_tel_input');

You can implement the above code using mu-plugins. Please check this link on how to implement the above code as a mu-plugins:
https://wpmudev.com/docs/using-wordpress/installing-wordpress-plugins/#installing-mu-plugins

Please do note that the above is more of a workaround and we cannot say how well My Sticky Elements would work in such a workflow. It’s something you’ll have to test and see if it works fine.

Please make sure to create a backup of the website or use a staging before testing it out.

Kind Regards,

Nithin