the_tim

Okay, I just did these exact steps:

1. click “New Post”
2. type a post title and some body content, choose a category, enter some tags
3. click “Save Draft”
4. make further edits, safe draft a few more times, etc.
5. click “Edit Details” in the Publicize section of the Publish box
6. tweak the Custom Message to this: “On the blog: Quill Leaves NWMLS, Dramatically Slashes Listing Cost http://wp.me/pe2Bv-7YP” (Note that the wp.me link was already in there when I clicked “Edit Details,” I just edited the text before it.)
7. click “Hide”
8. click “Save Draft”
9. preview the post one more time to make sure it looks good
10. click “Publish”

Here’s the tweet that resulted: https://twitter.com/SeattleBubble/status/603972097581293568

Once again, it has both the wp.me link and the full link.

Never mind, I found the answer here: Comment submit button disappeared after 4.2 update

Adding the two lines below to functions.php inside here:

function oxygen_commentform_args( $args ) {
[...]
$args = array(

did the trick for me.

'submit_button'        => '<input name="%1$s" type="submit" id="%2$s" class="%3$s" value="%4$s" />',
'submit_field'         => '<p class="form-submit">%1$s %2$s</p>',

Okay I tweaked the settings of the other SEO plugins to get rid of the error that the Facebook Debugger was throwing. This morning’s post worked.

Again though, I’m 99% certain that things only broke with the latest update to Jetpack and/or WordPress, and I’ve noticed a lot of other threads in this forum from people with similarly-timed breaks in Facebook publishing, so it still seems to me like something was changed that broke things.

Anyway, thanks much for helping me get it working again. The Facebook Debugger link was a big help.

Yes I turned off the plugin as described, cleared all site caches, and posted. When it failed to fix the problem, I re-enabled the plugin half an hour later.

I will give that a try with the next post I make tomorrow.

Version 1.2.1 does indeed work again (front end and back end). Thanks, it looks like whatever was causing the problem has been resolved.

I tried both. Same thing in both places. No effect at all.