schulz

BTW: Hopefully it is not throwing an error because I am not using all the input fields from my contact form in the mail form. Some fields don’t need to be emailed, such as the ‘honey pot’ or the CAPTCHA fields.

If that is the case maybe you should place that message as a footnote or warning on form submission and not as an error.

While writing this out I thought another possible error to look for is form tag mismatch (a tag in the mail form not used in the contact form), however I did not find any of those either.

I keep seeing “This contact form has 3 configuration errors.” yet I can’t figure out what is wrong?

I weeded out the obvious errors (like the ones mentioned above) and checked for the issues mentioned in the “How to Resolve Configuration Errors” page. However I can’t figure out what the problem is.

Your error message needs to at least give a clue like what rule am I breaking or if it is a syntax issue and state in the error message where the problem is. I’m hunting all over the contact form settings and not seeing any red text showing what and where the problem is. If it is a syntax issue, maybe highlight it red (like a spell-check) when you go to save it.

This is the current time format on the site:

g:i a T

Timezone: Thunder Bay (EST or UTC -5)

By removing the ‘T’ in the formatting seems to solve the problem, Thanks.

Maybe in the future there will be a time formatting selection/option for the plug-in that does not use the WordPress setting (just in case what works for the rest of the site does not work for your plug-in). I didn’t want the ‘EST’ showing up in the calendar anyway, however is preferred everywhere else.

so the problem does not affect the front any more, but just the export

No, the original problem is still ongoing. Your plugin still reporting and treating the time entered into it as UTC. I just dropped the ‘T’ in the Time format setting so it does not show the ‘UTC’.

Example: Time on my site says it is 6:41 am EST, time within your plugin says it is 6:41 am UTC

I have many WP sites to protect and this does not seem to be a very strait forward way to protect all my sites. Please implement a Block access to XML-RPC API system.multicall option in your WP Firewall Policies page as an option with the Block access to WordPress XML-RPC API set to NO.

I have emailed you screen shots of what is happening on my site with your plugin. Also I have re-enabled your log-in on my site so you can see for yourself what is going on and do some testing with your plugin on my site.

Updated to the latest version and could not find any difference?

Still shows 4 hours in advance as UTC. Is there something different I need to do?

I like the ‘Separate’ option, thank you.

However how do you set the plugin to use the website LOCAL time, not UTC? My WordPress is set to Thunder Bay Time (EDT – Eastern Daylight Time), yet your plugin is treating the date and time as UTC. UTC is four hours ahead and five hours ahead when we switch from Daylight time to Standard time in November.

Myself and my users are entering local time not UTC time when using the plugin, then your plugin treats it as UTC and displays it as if it is UTC causing confusion and having events start and end four to five hours ahead of schedule.

The free copy does not perform back-up automatically, you have to ‘manage it’ by going in and telling it to do the back-up.

Thank you, that worked.

I would not of figured that out on my own.

IMHO: I still think that restricting access to admins only for Contact Form 7 should be the default setting and use the ‘define capability’ thing when someone needs to open it up to other user roles.

And thanks to the developers for such a diverse plug-in.

Another problem with the new time picker…

It seems that it is using UTC time and not the local time, this has the potential to really confuse people. Like it did when my event set for the 13th said it starts tomorrow (today is the 11th).

I really like the plug-in, however your new changes are causing havoc on my site.

Why I said it is ‘messed up’ is because it is trying to insert the dashicons span inside the anchor title breaking both the dashicons span and the post title anchor.

Thank you for the suggestion on disabling the dashicons, it seemed to clean up the problem.

Event Settings -> Add icons for events in the loop : No

Your new Date/Time picker is still not behaving:

When I select 23:45 from the time picker it shows as 11:31?

Ok, after a long delay it decided to fix itself. I also noticed that it does not update the ‘end’ time (you can have the event end before it starts). Or maybe that also takes its time to fix itself (I haven’t waited long enough to see).

Your previous date and time picker worked so much better before you changed over to this new one, Why were you compelled to change it? (if it is not broken, don’t fix it)

Now working – Yes.

Better multisite sort – YES!

Thank you.

Working again – YES.

(oops, thought I was on my thread, sorry)

Thank you.