PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Gravity Forms 1.5 Beta2 bug?

Gravity Support Forums » Plugin Support » Gravity Forms

  1. divydovy
    Member

    Hi, think I've found a bug.

    I got:

    Uncaught TypeError: Cannot call method 'split' of undefined
    gf_get_valueconditional_logic.js:67
    gf_is_value_selectedconditional_logic.js:59
    gf_get_field_actionconditional_logic.js:37
    gf_apply_field_ruleconditional_logic.js:18
    gf_apply_rulesconditional_logic.js:4
    windowsign-up-the-details:208
    c.extend.readyjquery.js:26
    Ljquery.js:33

    When loading a form - resulting in the form not showing up as the display:none CSS declaration is still in the element style - I assume b/c the javascript errored before finishing.

    I *think* the cause is that I deleted a field (drop-down) that was set to populate dynamically from the form. The fieldid still appears in the JS on-page, but that field is no longer part of the form - i.e. there is no field with that id on the page any more.

    Let me know if you need any more info...

    Cheers,

    divydovy

    Posted 13 years ago on Thursday December 9, 2010 | Permalink

  2. Carl Hancock
    Administrator

    If you have custom JS that referenced a fieldid that no longer exists, and your JS is throwing an error because of it then it would cause the conditional logic to break because of a JS error existing on the page.

    Can you verify this is the issue by removing your JS?

    Also be sure to download the latest beta release as Beta 2 is not the latest beta release, a newer version is available on the Downloads page.

    Posted 13 years ago on Thursday December 9, 2010 | Permalink

  3. divydovy
    Member

    Hi Carl,

    I can confirm I had NO custom JS associated with that form/field.

    I now have beta 3 - but thought it was worth posting the error in case it hasn't been found before.

    Cheers

    Posted 13 years ago on Thursday December 9, 2010 | Permalink

  4. Carl Hancock
    Administrator

    @divydovy It hasn't been reported before and we can't recreate it locally. Is the error still happening? If so can you post a link to a page where we can see the error so we can debug and see why it is happening?

    Posted 13 years ago on Thursday December 9, 2010 | Permalink