Forums

Hi,

First off. Chronoforms is AWESOME! Really nice work. Thank you!

I have an issue on a site where the font in the calendar date picker is way too big. It's so big you can't see the numbers on the days of the week. Here's a link to the site. Any ideas what's causing this? Or how to correct it? Thanks again for a wonderful component!

Cheers,
Randy

http://trosamoving.com/index.php?option=com_chronoforms&chronoform=Estimate

Hi Randy,

There's a template CSS file personal.css that has settings for .day and .title; if you remove or over-ride these then the calendar is OK again.

Bob

Many thanks! You rock, good sir!

Cheers,
Randy

Hi Again.

Thanks for your help with the date picker, but another issues has popped up. I'm trying to get the form to have the reply to email address be that of the person who submitted the form. It seems like I just needed to use the Dynamic tab of the Emails tab in the wizard, and put my field name for {email} in the Reply To address blank to have my forms arrive with the proper reply to address.

Unfortunately using the Dynamic From and Reply To with the {email} field name, just makes all forms appear to be coming from my email address, rather than the senders. Even though I do not have my address as either the static or dynamic From and Reply to address. I'm not sure what's happening. (I'm guessing it getting my email address from somewhere in the site because I'm the admin?) I totally confused. Please see the attached screen shot of my dynamic email settings. Thanks for your help.

Cheers,
Randy

Hi Randy,

Leave out the {}

Bob

Thanks for the help. That's fixed the issue. I just bought you a beer!

One last question. (I promise.) The form is now picking up the proper email address dynamically as the reply-to address. But it's also still using the global site's email address as another reply-to address. How can I stop the second address from being included as a reply-to? I just want the form to have the submitter's address only as the reply-to.

Thanks,
Randy

Hi Randy,

This has its roots in a change to the Joomla! code in 1.7 and the bug has been reported to Joomla! and partially fixed in 2.5.1 I think. There's at least a partial fix here

Bob