paul-1

Thankfully, as kernelg says, the workaround does still work. Although it was frustrating yesterday having to apply it so many times – just as well it only takes a minute. It would be great to see this bug fixed in the next update … please.

Yes, I was glad to be able to use your work around still; had hoped that the issue would’ve been addressed in this release.

kernelg’s workaround looks like it’s working, thank you.

I changed $default_width from 640 to 500 in jetpack/modules/shortcodes/youtube.php – line 184

Same issue in 1.2.4 – had to revert back to 1.2.2 again. Might give kernelg’s workaround a go, if I can find where to make the change.

I’ve done the same as jayo, and downgraded to previous version to fix this problem with video width.

My webhosts have got me up and running again, thankfully. Not sure, yet, what I’m going to do about restoring the plugin — don’t want to break things again.

Thanks Mark.

Same problem here; had to go back to 2.1

Adding to the list of those experiencing this problem, and another one who relies on being able to schedule posts, for all sorts of reasons. I have been trying to reduce my dependency on plugins, but it looks like another is added to the mix now – thanks for sharing it bkushner.

I have the same issues with this. I assume it’s something to do with the new feature — being able to choose top or bottom of post for display. But may, of course, be way off on that assumption.

It looks as though one html page has been pasted inside another, including things like the “body” tag. And, what I think is throwing things off, there is an extra </html> towards the bottom of the source code.

#1 I use Viperbonds Scheduled Posts widget on the admin dashboard; that gives the actual dates rather than the relative dates. It’s a great help, and eliminates much of the need to go into the Edit Posts area.

https://www.ads-software.com/extend/plugins/dashboard-scheduled-posts/

#2 Nothing to offer, sorry.

It would appear from your source code that you’ve opened a <div> instead of a <p> before the “Read More” link in the last post written. That <div> won’t be closed, and that could very well be why the sidebar has dropped as it has. I’ve seen similar problems before.

There’s a topic a little further down the page with some pointers for this: https://www.ads-software.com/support/topic/166747?replies=13

There is information in the Codex about working with Plugins; this page, Managing Plugins, will be a good starting place.