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.

Datepicker - JavaScript/Css

  1. ConnP
    Member

    hi all,

    I enqued the lines Kevin mentioned in this post (http://www.gravityhelp.com/forums/topic/date-picker-not-working-1), and the form disappeared (lol). After some tests, I realized that the form disappears after loading conditional_logic.js. If I skip the conditional_logic.js line, the form works ok, but without the datepicker. Any hints?

    Extra info: when I click preview in the backend, the datepicker works fine. My best guess is some kind of css conflict, not js. Just trying to find the right place to dig. =/
    Jquery is loading ok since i implemented the "clearit" (http://rkt.gs/clearit) feature succesfully.

    Just upgraded to 1.6 hoping that datepicker would show up. Everything else is fine except this. =/

    link to form - http://www.interlakenoperadora.com.br/site/index.php/formulario/

    tks

    Posted 13 years ago on Thursday October 6, 2011 | Permalink
  2. 1. I am seeing this in the page now:
    [gravityform id=1 title=false description=false ajax=false]

    The shortcode is not being processed. Is that what you're talking about?

    2. Are you enqueuing the conditional_logic.js now?

    Posted 13 years ago on Thursday October 6, 2011 | Permalink
  3. ConnP
    Member

    Hi Chris,
    ty for your reply. Answering your questions:

    1. the shortcode in the "Informações sobre o pacote" field is a hook that i still have to build. That's ok.

    2. I'm not enqueuing conditional_logic.js. If i do that the whole form disappears. The big issue is the date picker in the "Data de nascimento" fields. they are not showing @ all.

    Posted 13 years ago on Thursday October 6, 2011 | Permalink
  4. The form disappears after enqueuing conditional_logic.js because your form is using conditional logic and there is likely a javascript error preventing it from unhiding the fields that should be visible. So it sounds like you have a few things going on.

    If your form uses conditional logic you muse enqueue the conditional_logic.js. But really in Gravity Forms v1.5+ you shouldn't be enqueuing individual scripts yourself. You should be using the Gravity Forms enqueue function to handle the enqueue and it will enqueue any scripts that specific form needs. It is documented here:

    http://www.gravityhelp.com/documentation/page/Gravity_form_enqueue_scripts

    Also make sure your theme has the wp_footer() function call in the footer.php because I believe the datepicker script is enqueued int he footer.

    Also make sure you use the function above to handle the enqueue.

    Posted 13 years ago on Thursday October 6, 2011 | Permalink
  5. ConnP
    Member

    Guys,

    ty a lot for the hints, we are making good progress. Used the gravity_form_enqueue_scripts function and now i get the picker. Although its broken, as you can see here.

    Ideas?

    Thanks again for the quick and awesome tips!

    Posted 13 years ago on Thursday October 6, 2011 | Permalink
  6. Have you checked for theme and plugin conflicts to see if either your theme or another plugin is causing a script conflict of some sort? If not I would suggest doing so as that is what this looks like. You can follow the directions here:

    http://rkt.gs/testing

    Posted 13 years ago on Thursday October 6, 2011 | Permalink
  7. ConnP
    Member

    Just disabled all plugins and the picker looks the same.

    Posted 13 years ago on Friday October 7, 2011 | Permalink
  8. ConnP
    Member

    Guys,
    just found the problem. It was not related to the picker @ all. Just disabled a few js's in the form page and everything is fine now.

    thanks for helping

    Posted 13 years ago on Friday October 7, 2011 | Permalink
  9. Thanks for the update. Glad you got it working.

    Posted 13 years ago on Friday October 7, 2011 | Permalink

This topic has been resolved and has been closed to new replies.