Wow, let me know who your hosting provider is so that I can never recommend them. All the quoted error means is that a custom 500 error page could not be found, which obviously happens immediately after the 500 error is recorded. The 500 error happens, the server records it in the server error log, it then looks for a custom 500 error page to display, but it can’t find it, so it records that fact in the server error log, and then it displays the generic 500 error. It has nothing to do with malware.
A 500 error is nothing more than a “Internal Server Error”. We will never be able to know what the actual error is without knowing what was recorded in the internal server error log.
I hate to sound like an ad, but if this was my host, you’d at least have full access to the server error log. If you needed help understanding it, their support department would gladly help you. And, if it was a slow day in the support department, they’d even fix the problem for you.
I don’t know what else to say, but we really can’t help without knowing what the actual internal server error was. Sometimes, plugins can conflict this way, but it’s very rare. Try disabling all plugins. If that resolves the issue, reactivate each individually until you find the cause. If a plugin is causing the problem, we still won’t be able to fix it without knowing what the error was. You’ll just have to stop using it.
Thank you soooo much for all of your help!
I use Pappashop and since I am using their store admin for my website at Green and Chic I will have to see if its even possible to move it. I will definitely ask them!
In terms of now, even without knowing what the actual problem is, is it possible for someone to be able to fix it – if I hired someone on the outside? I sure hope this isnt a lost cause!
Thanks again!!
Carla
I may be able to fix it, but I would need access to your WordPress admin area, your hosting account’s control panel, and FTP access. If I can fix it, I’ll have to charge for time too. Please contact me if you’re interested.
After further investigation, an overzealous security script or a misconfigured server was preventing the completion of “POST” commands containing the word “from”.
Unfortunately, since WordPress saves and publishes posts via the “POST” command, absolutely no posts containing the word “from” could be saved or published.
This issue was temporarily resolved by finding creative replacements for all occurrences of the word “from” in the post.
The issue is now in the hands of the hosting provider, and I hope that they figure out what is wrong with their server.
The issue has been officially resolved. mod_security was identifying the post as a MySQL injection attack. The hosting provider adjusted the mod_security rules, and that appears to have solved the problem.
