Apparently, the issue lies in some interaction with Jetpack (it and one other ‘essential’ plugin were the only ones I didn’t disable).
I’m still scratching my head on this.
Hi,
this might be js issue; maybe you can try to check if wp_head() or wp_footer() within your theme header.php and/or footer.php is properly used.
That’s my suspicion, too.
Maddeningly, after turning off Jetpack, it worked fine for a short while, then failed, again, without any changes to the production configuration.
I pulled all other plugins from the dev site and switched the theme to TwentyTwelve, without any resolution.
I have a feeling that it may be some remnants of WP-SuperCache, due to a generated comment tag, despite the fact that I’ve deleted the plugin and all the files I have permission to modify.
Unfortunately, my hands are partially bound — I had complete access and control over my old server, which suffered a hardware failure, two months ago. IT policy changes, since the old box went live, mean that I don’t have total access on the new dev box and zero access to the production install (aside from the WP Dashboard and a sync script). In addition, the old box was running SUSE and the new site is a different distro, so there are some differences in the overall configuration. (And I’m not even allowed access to the Apache/mySQL/PHP logs.)
It could also be WP 3.5.x; the site was upgraded from 3.4.x without my permission, due to a security scare with another WP install, on another box, run by another department, so I didn’t get a chance to test my custom theme against it and sort through any deprecated code.
Hm.
you may have a server error here… I get a problem when accessing:
https://ducis.jhfc.duke.edu/wp-admin/admin-ajax.php?callback=jQuery18300037906549405306578_1359989964693
which is what EM tries to access with ajax
Hm. I suspect its to do with the fact that the new server has /wp-admin/ .htaccess restrictions.
Thanks for that bit of info — now I have a specific place to point out to the OIT staff (since I can’t change that access rule, myself).
(This wouldn’t be the first time that their security paranoia has broken parts of the site; I’d move the site to an off-campus host, but we’re a provostial department and not allowed to do so.)
yup, big chance that’s the problem then.
Thanks, Marcus — I’ve been pulling my hair out over this — it’s also broken another plugin, which I’ve used to run a grants competition, that ends today.
