datepicker not showing on front end

Mary Anne Lavin
Home / MB Frontend Submission / datepicker not showing on front end

Custom Fields
Re-Envisioned › Support › MB Frontend Submission › datepicker not showing on front end

  • Creator
    Topic
  • August 9, 2019 at 6:20 AM #15651
    Resolved Mary Anne Lavin
    Participant

    I searched the forum and don't see this issue - which makes me believe it will turn out to be User Error. Nevertheless, I could use some help with this: the datepicker calendar doesn't open on the frontend. It looks great in the admin area. I tried a few themes, including 2017 and it still doesn't show. I am using the JQuery defaults in the 'date' custom field.

  • Creator
    Topic
Viewing 5 replies - 1 through 5 (of 5 total)
  • Author
    Replies
  • August 10, 2019 at 3:16 PM #15665
    Anh Tran
    Keymaster

    Hi Mary,

    Do you see any error in the browser console?

    August 11, 2019 at 11:11 PM #15670
    Mary Anne Lavin
    Participant

    Nothing is showing with DEBUG. Inspecting the input [], it says it is a text field. But the calendar shows up on the admin side.

    August 12, 2019 at 11:58 AM #15674
    Anh Tran
    Keymaster

    Hi Mary,

    I've just checked and couldn't replicate the error. I recorded a video here:

    Please take a look.

    If you still see the problem, please send me more details or a temporary admin account via the Contact form. I'll take a closer look to your site.

    August 13, 2019 at 1:59 AM #15678
    Mary Anne Lavin
    Participant

    Thanks for the video. I see the issue is with the shortcode I was using. But now I have a new problem. Adding "content" to the short code activates the datepicker and adds the page's content editor - I only want the custom fields for the custom post type(which does not support the content field)

    [mb_frontend_form id="name" post_fields="title, content"]

    August 13, 2019 at 11:09 AM #15685
    Anh Tran
    Keymaster

    I see. Removing the "content" from the shortcode breaks the date picker. I've just fixed it in this commit. Please try it. The new version is coming soon.

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