Hi @ravanh,
Thanks for sharing all the details — that definitely sounds like a confusing and frustrating issue.
From what I can tell, Jetpack wasn’t fully connected at the time the post content changes occurred, so unfortunately no activity could be recorded during that period. The connection appears to have been restored shortly after — but on the free plan, the Activity Log only shows the 20 most recent events, and anything from before the reconnection isn’t available.
That said, I took a look at the logs we do have access to. If the changes you mentioned happened around the time when Jetpack was reconnected, they may have coincided with:
- an update to MailPoet
- and the deactivation of a plugin called Optimize Database after Deleting Revisions
It’s hard to say for sure if either of those actions was directly related — but if that optimization plugin had been run just before being disabled, it might explain unexpected changes to post content.
Also worth noting: the Activity Log on paid plans includes more history and filtering options, which can be helpful in cases like this — but it would have needed to be active before the issue occurred to capture those earlier events.
I know that’s not a full explanation, but I hope it helps point in a possible direction.
Hi, thanks for looking further.
The Mailpoet update and deactivation of Optimise Database after Deleting Revisions were done today after discovering the issue. But as far as I can tell from looking through the daily DB backups, the issue occurred between the nightly backups of the 12th and 13th of June. So a while back already. I suppose there is no way to go that far back in the activity logs :/
Ever heard of such a thing happening? All post_content cells in the DB wp_posts table being replaced by their respective guid cells? Weird..
Anyway, I’ll recommend a paid plan to the client in question 🙂
Hi @ravanh –
This isn’t something that we have encountered here at Jetpack. If you happen to discover the cause, feel free to update us on the thread.
For now, I’m going to mark this thread as resolved since the Activity Log issue was resolved.
