mickmel

That’s not a great answer. What I’m hearing is: “Sorry we broke all of your sites, but it’s not our problem. Go use Mandrill instead.”

Is that about right?

Edwin — Sorry for the trouble you’re having. If you have a caching plugin installed, that might be part of the problem (and it essentially makes our plugin useless anyhow).

Did a bit more digging and can’t find much to go on. All four sites are on different hosts, different themes, and all have a fairly limited set of plugins (10ish).

There’s something else going on here. I have four sites (out of ~100) that are down with Jetpack 4.8. All four have the same problem:

— Renaming the plugin folder brings the site back up
— Uploading 4.8 fresh via FTP didn’t solve.
— Once disabled, I can’t activate 4.8 because “Plugin could not be activated because it triggered a fatal error.”
— WP-DEBUG simply hides the 500 message and gives a 100% (including source) blank screen. No other error messages found. Nothing in the server error logs either.
— Pushing 4.7.1 back up to the sites fixes it.

Setting a parent/child relationship via the page attributes doesn’t affect the menu. Typically, the only change you’ll see is with the URL (sitename.com/parent/child/), though some themes/plugins do a bit more with it.

Use the menu features to arrange them any way you’d like; that will often match your page attribute settings, but doesn’t need to.

Are you able to see the posts? Is she able to log in at all?

If you can edit your wp-config.php file (via FTP), change WP-DEBUG from “false” to “true”. Once that’s done, you may see other error messages on the screen that give you more info about what’s going on.

Yep, it works now. Thanks for the prompt fix!

Wow, that was it! (Settings –> Writing). I didn’t even know to check there. It seems to be a new checkbox with Jetpack 4.7; some of our sites had it checked after the update, and some didn’t. Weird.

Thanks for the help!

Any idea what the purpose of that box is? Why not just let the main Jetpack Markdown setting control what happens on the site?

Jeremy — I tested on four more sites that we manage; three of them have the same issue, but I’m unable to determine what the differing factor is. I thought perhaps it was related to SSL (which was a valid theory for that 3 out of 4), but I’ve tested further and SSL doesn’t seem to affect it.

I should add that it was a caching issue that caused the old version not to work. Downgrading to the previous version of Jetpack and then clearing the cache solves. For the other sites, I simply can’t get Markdown to work.

Sites where it is broken:
gearthblog.com (temporarily fixed by downgrading Jetpack)
greenmellenmedia.com
mickmel.com

It’s certainly something in Jetpack 4.7, but I can’t determine what…

I’m happy to reconsider, but need another option. The number of new “bad apples” is growing exponentially, and my current approach won’t scale quickly enough. This at least buys us some time and keeps the plugin to a reasonable size.

I’m completely in agreement that it’s not the best approach, but I can’t come up with a better way to handle it.

Thanks.

Yes, it’s in there now. Thanks!

I’ve not seen that issue before, but since it’s a legit URL I suspect you’re getting hit with ghosts. Have you set up block for that yet (details below)?

https://www.greenmellenmedia.com/blocking-ghost-referrals-in-google-analytics/

Thanks — we’ll check those out and add them to the list.

I’m having the same issues. Some thoughts and things I’ve tried:

— It doesn’t appear to be stretching the icons, per se. The icons are showing up huge behind the bubbles, which then stretch to fit the height of those big icons.
— I have virtually no WP Rocket settings enabled.
— I cleared the WP Rocket cache repeatedly.
— There are no server-level or other caches.
— I disabled Photon, as sometimes that can mess with it.
— I resaved the widget settings, in case that would force something good.
— I installed the SVG Support plugin.
— It’s a clean theme (Genesis) with only a dozen plugins; all are well-known, solid, seemingly unrelated plugins.

After all of that, it’s still not working right. I’m out of ideas. We have this on ~20 sites; half work great, and the other half are having this trouble.