Thread Starter
Pete
(@peezey01)
I have tried updating the redirect URL. Didn’t work.
I’ve tried deleting and reinstalling the plugin. Didn’t work. And for some reason all of the previous settings were still there… don’t know if that tells you anything.
Thread Starter
Pete
(@peezey01)
The plugin might have possibly broken around the time that I activated Welcome Mat in SumoMe.
But I deactivated Welcome Mat, then reinstalled MailChimp For WordPress, and it still did not work.
I have now re-enabled Welcome Mat because people are trying to subscribe.
Hi there,
For some reason it seems that your site is returning a “500 internal server” error after hitting the submit button.
Do you have access to your PHP error log by any chance? It should show us what exactly went wrong so it’d be super helpful in debugging the issue.
Thread Starter
Pete
(@peezey01)
Hi Danny, thanks for responding. Where can I track down my PHP error log?
Thread Starter
Pete
(@peezey01)
Ok got it. This is the only thing that keeps popping up in my PHP error log:
[23-Mar-2016 01:19:07 America/Los_Angeles] PHP Warning: PHP Startup: Unable to load dynamic library ‘/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/homeloader.so’ – /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/homeloader.so: cannot open shared object file: No such file or directory in Unknown on line 0
Hi there,
That is weird, there should be something of a “Fatal Error” showing in your error log.
I noticed something else which is strange as well, basically it seems as if your site is not responding to any POST type request. Are you able to login to your WP Admin?
Your host will probably know more about this and he will be able to track down the error message for you. This is a bit hard to diagnose without that error as I haven’t seen any other cases like this come by, and I think it might not even be related to our plugin..
The following should give your host a general idea on what’s happening.
Every POST request to the site / server results in a 500 internal server error. It looks like submitting forms results in a fatal error somewhere, but the PHP error log I looked at isn’t showing the exact error message.
Hope that helps. If not, let me know!
Thread Starter
Pete
(@peezey01)
My mistake, there is one instance of this:
[22-Mar-2016 23:49:08 UTC] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 30720 bytes) in /home/magnet34/public_html/wp-admin/includes/plugin.php on line 786
Yeah I can log into WP Admin and do everything in there just fine.
I’ll wait for your response first, then ask my host if need be.
It seems that your server only allows 40MB of memory while it’s generally recommended to have at least 64MB available for WordPress & additional plugins. Especially if you have a ton of plugins this can be necessary.
There are two ways to go about this.
1. Ask your webhost to increase your memory limit or look at increasing it yourself (not always possible): https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
2. Deactivate plugins, especially the ones adding significant memory usage (hard to know, besides the one you activated before this error started occuring).
I recommend the first method, as you’ll run into this again eventually when choosing #2. 🙂
Hope that helps. If not, let me know!
Thread Starter
Pete
(@peezey01)
Hey Danny, I’ve upped the limit to 256MB. It looks like it worked (according to this: http://beardstrokings.com/phpinfoz.php)
But the issue remains 🙁
Hey,
Does your PHP error log state anything new this time?
Please note that the issue is not related to our plugin as I’m getting the same error by simply POST’ing anything to your site using the following command.
curl --verbose --data "foo=bar" http://beardstrokings.com/
This is just a sample POST request which sends a simple foo=bar value to your site. Your site then responds with a “500 Internal Server” error.
Your PHP error log should really tell us what went wrong exactly. Another debug method is to disable your plugins one by one to find the plugin that’s causing this error.
Thread Starter
Pete
(@peezey01)
3 other WP plugins just released updates, so I updated them and now it appears to be working again. I guess one of those plugins was messing shit up.
Yoast was one of the 3. Can’t remember what the other 2 were.
Thanks for your help 🙂
