mesayre

Thanks Anders. Mmmm, that’s what I had, and it was not working for me. I might give it a try again later when I’ve got some time.

On a related note, I find it troubling that WordPress wasn’t presenting any kind of error info when this was happening, just a completely blank page. I don’t actually know enough about WP’s error mechanism to know if it’s possible to call sharing_display (or other plugin functions) in such a way that it will properly catch & report the error when it’s not there and/or gracefully resume with a warning. I assume it was somehow leading to a critical error that stopped PHP in its tracks. Had I not known to look in that one place because I just added that function, it would’ve taken me a long time to locate.

Thanks for this useful tip, however, there’s one problem with it.

I used this method successfully on a few blogs. But when I migrated, and Jetpack was not yet installed, any page with this filter call gets served as a blank page because the filter doesn’t exist. Not a problem as long as JetPack is installed. But if it gets deactivated, or the good folks at Automattic change something, this will blow up your blog.

I’m still looking for a safe way to do this. I tried wrapping it in “if (function_exists)…” but this doesn’t work either. Same behavior. I get an empty page without a spec of code. The exact same code works flawlessly on blogs that have JetPack. Anyone got any suggestions for making this safe & future-proof?