kernelg

Same here in WordPress 3.7.1. I’ve tried many different variations of the above, but nothing happens when you visit the site using the first domain (which breaks things without some kind of multi-domain handling). Too bad, because this looked nice and simple.

I may just resort to Apache.htaccess redirects.

1.6.1 has removed the via. That works.

But it is still chopping the headline short as I noted above. Example, using the Twitter button on this page:

FXpansion Intros DCAM Dynamics with Fre… https://www.macosxaudio.com/front/2012/07/fxpansion-intros-dcam-dynamics-with-freecomp-on-the-house/

There are still 79 characters available in that Tweet, yet the code has chopped the headline off, (I believe) because it is taking the full length of the URL into account. Since Twitter automatically shortens all long links, that URL isn’t actually more than 19 characters (the t.co version that it becomes).

I can manually fix it for my sites, and it’s not a showstopper. Just incorrect. ??

Even better. Thank you, Matt!

I just noticed the same thing, if I’m understanding you correctly. For some reason, it’s picking up Home URL, stripping non-alphanumerics from it, and using that as the default ‘via’ username. This would rarely give a correct result.

If you’re comfortable editing the plugin files, you can fix this in jetpack/modules/sharedaddy/sharing-sources.php. On line 327, I commented out where it’s setting this default ‘via’ and added my site’s Twitter handle instead.

Another fix, while you’re in there: On line 373, it’s truncating the post title based on the full length of your link. Twitter now shortens links on its own, and no link will ever use more than 19 characters, so this chops far more than necessary. I removed the $post_link variable from inside the strlen and added a straight value of 19 to the calculation.

Jetpack 1.3.1, 1.3.2, 1.3.3 and 1.3.4 have not addressed this sizing bug, even though Chris F at Automattic successfully reproduced it on April 10. They must have a long to-do list. His advice was to turn Jetpack YouTube embeds off (and presumably use a different plugin for them).

The workaround above, however, still works.

Jetpack 1.3 has not addressed this issue, unfortunately. But the workaround still works. Around. ??

Same issue here. After upgrading to Jetpack 1.2.3, all of my YouTube embeds are 640 pixels wide and hanging over the right edge of posts. Settings / Media / Max embed size was always set to 580 wide to match my post content width, and still is (even refreshed the settings to be sure).

I was able to work around this by changing $default_width from 640 to 580 in jetpack/modules/shortcodes/youtube.php until an actual fix is in.

I just found my way here regarding the same issue with TEC 1.6.3 in WP 3.0. One of my clients has a performance tonight at 7pm, the end of a four-day run. When I checked at 2am it was no longer considered “upcoming” on both the widget and the events list. Final day, gone. We are in Pacific Time (UTC -7), as is our server. This is fairly important as it affects the promotion of paying gigs. If anything, I’d rather events linger too long versus disappearing too soon. Many thanks!