Rodrigo

That’s what I thought, @lapzor. I had a little hope that maybe the endpoint could work somewhere I control, such as the /wp-content/.

Thanks for your attention!

Ops, sorry about that, @jdembowski

That’s good to hear, @sterndata! I can’t access the Slack channel, but I hope fixing that bug is near on WP’s roadmap. Thanks!

Thanks, @jeherve!

Thanks, Lisa! Since .com’s Business plan is more or less like a self-hosted/.org WP install, I thought maybe other people could be dealing with the same issue.

I opened a topic on this issue in .com support forum.

Ok. Thanks! (And have a good first day at the new job! ?)

Any chance to WP YouTube Lyte to play nice with Jetpack’s Markdown?

Thanks for your reply! I was thinking and there are two possible culprits:

1. Jetpack’s Markdown editor.
2. A functions.php snippet that removes visual/WYSIWYG editor from Classic Editor — it’s HTML-only.

I guess, since HTML editor exists anyway even without the snippet, that it’s probably some issue with Jetpack.

Oh, interesting. I wasn’t aware. Actually, I got a warning from PageSpeed Insights that an imagem from WP YouTube Lyte was lacking loading="lazy", but can’t reproduce anymore. Maybe I got confused.

Thanks!

Unfortunately, the staging site doesn’t reproduce the PHP warning error.

Here: https://wordpress.com/site-logs

Thanks, @macmanx!

I installed Health Check and just reactivated Jetpack plugin, since that error log is generated by one of its modules. I noticed that errors are triggered by new content — posts or comments —, and they appear even when troubleshooting mode is activated.

I’m not sure, however, if troubleshooting mode works with this error log, since it appears on wordpress.com dashboard, not in my site’s WP dashboard. (I guess you’re familiar, but Business tier in WP.com allows you to have full WP, plugins and custom themes included, kinda merged with WP.com stuff.)

I’ll try to reproduce this issue in a staging site.

There’s a huge difference between taking the responsibility and costs of a project and destroying it with advertisement, bloatware, and who knows what else.

This negative rating is a warning for other people regarding what to expect for this plugin — that’s why a rating system existis, I guess.

Awesome! Thanks, @deryck!

Awesome! Thanks, @deryck