Forums

Hi

I had issues with the datepicker no longer working at all on Chronoforms v3, I guess after upgrading from Joomla 1.5/2.5 to 3, so I finally made the move to Chronoforms v6.

Besides being so big, that the form has to be quite big to proceed clipping, the calendar is popping up nicely after selecting the input field. However, I'm missing prev/next buttons for selecting years: if I want to use a calendar to get a birthday, it seems impossible to choose a year outside of 2011-2022 range.

After randomly smashing on my keyboard for some time, I found out that after pressing the up or down button 3 times, the selection changes by 10 years. But I don't think a regular user will get that far.

Any ideas please?

and a side question: I'm running into troubles because of the max_input_vars. I'm still awaiting my hoster to answer my request for incrementing it from the default 1000, but in the mean time: are there strategies to keep the used input_vars low? adding a single text input increases the counter by 63, which means that I can't even put 16 fields in a form right now.
Part of the high count seems to be originating by the extensive permissions options. I'm somewhat missing the point why each individual form-field has permissions by itself.

kind regards
Stijn

Hi Stijn,

There should be navigation arrows for the years, maybe they are hidden on your page, could you please post a link to the form ? or test it in the admin area using the "preview" button inside the form edit page.

Each element or function has permissions control, this is the default in v6 for full control over the form elements.

I will try to add a new setting to help with low max vars configs in the next update.

Best regards,
Max

Hi Max

In preview mode, the calendar isn't showing up at all.
you can take a look at the form here: http://dev.bvlb.be/index.php?option=com_chronoforms6&chronoform=test

thank you for looking into this

Stijn

Hi Max,

same problem here.

Is it fixed?

Regards,
Marc

Hi Marc,

Did you try the fix suggested ? that should be a temporarily workaround till the next official update.

Best regards,
Max