Error 500 when submitting form
Permalink Browser Info Environment
Hello,
Every time I submit my form, I'm greeted with this message:
The console indicates the following:
And Concrete5's logs show this:
[*] = full URL edited out.
The timestamp of this last error message does not correspond with the time at which the error is thrown, indeed it doesn't even appear every time I submit the form.
Any ideas as to why this happens?
Thanks
Every time I submit my form, I'm greeted with this message:
There was an error submitting this form. Please contact the administrator of this site.
The console indicates the following:
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
And Concrete5's logs show this:
Exception Occurred: [*]/packages/formify/controllers/api/records.php:327 Invalid argument supplied for foreach() (2)
[*] = full URL edited out.
The timestamp of this last error message does not correspond with the time at which the error is thrown, indeed it doesn't even appear every time I submit the form.
Any ideas as to why this happens?
Thanks
| Type: | Discussion |
|---|---|
| Status: | In Progress |
Quick update: I had the mailchimp integration set up. After deactivating it, the form seems to work again. My client specifically asked for this, so I'll have to re-activate it one way or another...
I just posted a new version which may address this bug (I had some similar issues in an environment I was testing in).
With regard to MailChimp - make sure you specify the config values (API keys and stuff) in the Integrations page of the form. If these are blank, you're likely to get errors.
With regard to MailChimp - make sure you specify the config values (API keys and stuff) in the Integrations page of the form. If these are blank, you're likely to get errors.
Thanks for your (very) quick response!
I dug a little deeper and found that (for context, see refused.jpg, attached):
I guess this is due to some firewall setting on the server's side. I guess I'll have a chat with the admin.
I however also found the following bug: accented letters (é, à, è, etc.) seem to cause another error (see egrave.jpg attached). The records get stored correctly nonetheless and display the accented letters, so I guess it's not really that big of a problem.
I dug a little deeper and found that (for context, see refused.jpg, attached):
API call to lists/subscribe failed: Failed connect to us14.api.mailchimp.com:443; Connection refused
I guess this is due to some firewall setting on the server's side. I guess I'll have a chat with the admin.
I however also found the following bug: accented letters (é, à, è, etc.) seem to cause another error (see egrave.jpg attached). The records get stored correctly nonetheless and display the accented letters, so I guess it's not really that big of a problem.
Well, after a chat with our admin, it turns out our organization is behind a proxy server that blocks such connections. I saw in formify's code that it's still using the mailchimp API v. 2.0, which seems to stumble upon this, unlike the v. 3 (https://github.com/pacely/mailchimp-api-v3#behind-proxy). Would it be huge trouble to upgrade Formify to mailchimp API v3?
Thanks a ton.
Thanks a ton.
Good call. I (incorrectly) assumed that MailChimp's official library (which I am using) would use the latest API, but alas it only uses v2.
I've added upgrading to v3 on the road map.
I've added upgrading to v3 on the road map.