Support » Fixing WordPress » WP Conflict with Gravity Forms (Bug)

  • Resolved jetxpert



    In the back-end, our Gravity Form (preview mode) works great. However, in the front-end, it behaves differently.

    Specifically, when we upload a file to our form in the back-end, the “Red X” icon next to the uploaded file displays properly. Also, when we upload a file with a file type not recognized by Gravity Forms, we get the proper error message. In turn, the front-end of our same Gravity Form does not function or behave the same way. The “Red X” icon is broken and the message is incorrect. Click below for details:

    Back-End (Works Great):
    Front-End (Does Not Work Great):

    You can replicate the issue by visiting the following link and trying to upload a dummy file (no need to complete the form, just upload a dummy file)


    We tried every possible troubleshooting technique we could think of, but couldn’t find the root cause. All we can think of is that there’s an incompatibility between WordPress and Gravity Forms since that’s the only thing we couldn’t test without deprecating our version of WP and breaking our website.

    Our Website System Information:

    Avada 7.1.1
    WordPress 5.5.1
    PHP 7.3.23
    cURL 7.59.0
    MySQL 5.6.40
    Gravity Forms 2.4.21

    Any help on how to fix this would be appreciated!

    Thank you!

Viewing 4 replies - 1 through 4 (of 4 total)
  • I’m not sure the issue lies with your setup. Your best bet is to reach out to Gravity Forms and have them suggest a solution. You should be able to open up a support ticket on their website:

    Looking at the form, the system is trying to find the [x] image in the root directory ( which is not right ). It should be looking for the file in the plugin directory. This seems like an issue with how the image URL is being generated and would only be fixable by the plugin author.


    Thanks for the input.

    Yes, we did that already (click here) and are waiting for their input as well.

    We also noticed that the wrong source file path is being used by the plugin. The wrong error message also needs to be explained and fixed.

    Still, there’s a possibility the issued could be caused WP’s latest update(s), which we couldn’t test.

    Once I hear back from Gravity Forms, I’ll update this post.





    Issue fixed. As it turns out, we were using Avada’s Code element (and a Gravity Forms shortcode) for our Gravity Forms. Apparently, Avada does not like this so we used Avada’s Gravity Form element instead.

    Avada alerted of this bug. Let’s hope they fix it. Avada’s Code element should work with Gravity Forms’ shortcodes with no issues.




    Final Comment:

    Kudos to Team Friendly for identifying the root cause of our issue and fix.


Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.