Not all fields captured in Caldera Forms

  • Resolved dmk23

    (@dmk23)


    7 years, 7 months ago

    We implemented HandL UTM Grabber along with Caldera Forms. In the forms we are creating we are adding hidden fields with defaults values defined like this: {request:utm_source} , {request:utm_medium}, {request:handl_original_ref}, etc

    The problem is that while utm_* fields ARE being captured, the handl_* are not. We verified via cookie viewers that handl_* cookies are being created correctly. However, for some reason, their values are not passed to the forms

    Any idea what could be going wrong here?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter dmk23

    (@dmk23)

    Just a quick note, I found and deployed this solution:
    https://gist.github.com/Shelob9/a73ef6103b487e18c2af54f2becf7c9a

    It probably should be part of the plugin though …

    I’m the developer of Caldera Forms. That gist you found I wrote for a user with this exact problem. I think that is all you need.

    BTW We have our own UTM fields now https://calderaforms.com/doc/utm-fields/

    BTW If the plugin author is reading this, consider that GPL code that you can use in your plugin. If you have a GitHub repo, I’ll put in a pull request.

    Thread Starter dmk23

    (@dmk23)

    Thank you, Josh

    We are not using the “UTM fields” because they don’t work right with one of the processors we need (Google Sheets). Besides, that HandL UTM Grabber helps persist utm params (and more) through the session which we see as critical functionality

    Additionally, we’ve extended your Gist to add a magic tag to support persisting / pre-populating any field from either the cookie or query string => {cookie:*}

    I’d think that all this functionality ought to be part of Caldera core, but from our perspective we have the issue fully resolved …

    Ok, that makes sense. I’m always interested to understand the use case for different plugins along with ours.

    BTW An add-on plugin or tutorial for adding {cookie:*} magic tags to Caldera Forms would be great ??

    Thread Starter dmk23

    (@dmk23)

    I’d be happy to contribute the code but still need to figure out how to publish a plugin to WP community ?? Just starting WP use/development after not touching anything PHP in a very very long time ??

    Bestway to start is to out the plugin on GitHub and ask for feedback. If it’s Caldera Forms related I’ll review it and share it ??

    Thread Starter dmk23

    (@dmk23)

    Will probably do this once we’ve finished a few other bits of functionality for a new site we are launching. We are considering releasing some marketing plugins as part of our offering, so publishing this little add-on first could be a nice practice ??

    Plugin Author Haktan Suren

    (@haktansuren)

    Hi @shelob9 and @dmk23

    I will include the above code in next release. Thanks for the permission.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Not all fields captured in Caldera Forms’ is closed to new replies.