champlainmarketing

I just recently saw this error on one of the websites I host, and the fix is something simple (and hopefully permanent) that needed to be done on multiple sites. The chmod permissions for the file wp-admin/admin-ajax.php had, for some reason gotten screwed up and went to 000. It needs to be 644. Doing it via FTP didn’t work. I found that I needed to go through CPanel and File Manager to change the permissions on the file. Once I did that, the problem went away.

Would it work if I wrote a cron job that automatically deletes the files in the cache/css and cache/js directories that are a day old? I guess I’ll find out for myself…

I’m getting the same error. The DB user is the same on both DBs, though I can’t yet verify they have the same privileges on both DBs. If it’s the directory permissions, what number SHOULD it be, 777?

kay9 is the winner. I had been looking for a solution to this problem for a few hours, and this was one of the few suggestions that could be tried on a live site. Changing the theme is never really an option on a live site, at least not one that belongs to a client.

Adding this
define( 'WPCOM_API_KEY', 'abcd1234efgh' );
to the bottom of the wp-config.php file did the trick (obviously using my WP API key instead of abcd1234efgh).

Thanks Kay!