Posted: February 17, 2018 at 5:52 pm
|
Hi There, I just spent quite some time trying to work out EE kept telling my my MailChimp API was invalid, when in fact I knew that it was valid and the same API key worked perfectly well in MailChimp for WP plugin on the same site….
Sifting through the EE Mailchimp plugin class files I found the issue. It uses CURL_EXEC to register the API key, and CURL_EXEC is in the list of disable_functions on my server. removing CURL_EXEC from the list immediately resolved the issue, however I don’t want to do that permanently as it potentially dangerous function. Noting that this makeRequest function checks if CURL_INIT exists and runs the else clause if not, I tried adding that to the disable_functions list but this did not work. It seems function_exists returns TRUE even if the function is disabled via disable_functions. I would suggest checking if this function exists and is enabled in this makeRequest function.
|
Hi there,
What version of PHP are you running? 5.2 would incorrectly return true for functions that are disabled, 5.3+ should not. function_exists will return false for
Would also fail because:
Although we are then checking if the function_exists, if its ignoring disabled_functions then it will make no difference as they will return true anyway. You can try changing the above conditional to the above so it explicitly checks for curl_exec but from the above, I don’t think it will work. Can I ask why you consider cURL dangerous? |
|
The support post ‘EE MailChimp – Disabled CURL Functions – API Key Registration’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.