ChrisBAshton

PS: I should say I was on version 2.4.0, and this may now have been fixed in version 2.4.1. (“Minor bugs fixed” in the changenotes).

Thanks for reporting this, @carlyjcais – just writing to say I had the same issue.

My posts to Twitter were missing the permalink, even though I had {PERMALINK} in the body.

Setting ‘SMAP’ to 280 fixed the issue (mine was blank too).

I suggest the plugin should default to 280 rather than making us specify in future.

But thanks for the great plugin!

That’s great news, thanks for the fast response.

Thanks so much for your review! It’s lovely to hear this plugin is being used by somebody and is useful.

It hasn’t been updated in a while but I should release a patch version soon just to reassure that it works with the latest version of WordPress.

That appears to have fixed it – thanks for jumping on it so quickly!

I had this same problem and I was tearing my hair out – no console errors, not much to go on. My problem was with a custom plugin I’d written, which adds a custom meta box to posts and lets you attach different images to the post (in this case, ‘app icon’, which we wanted to keep separate from Featured Image). This plugin contains some JS which hijacks the ‘Insert Into Post’ target.

Offending code:

window.send_to_editor = function (html) {		
  var imgurl = $('img', html).attr('src');		
  updateImageField(imgurl);		
  tb_remove();		
}

So now I make sure I make a copy of the state and revert back to it once I’m done.

breakAddMediaBehaviour();
window.send_to_editor = function (html) {		
  var imgurl = $('img', html).attr('src');		
  updateImageField(imgurl);		
  tb_remove();		
}

// then a bit later:
restoreAddMediaBehaviour();

// here's where the 'magic' happens:

function breakAddMediaBehaviour() {
  window.prev_send_to_editor = window.send_to_editor;
  window.prev_imageFieldToUpdate = window.imageFieldToUpdate;
}

function restoreAddMediaBehaviour() {
  window.send_to_editor = window.prev_send_to_editor;
  window.imageFieldToUpdate = window.prev_imageFieldToUpdate;
}

Thought I’d share in case it’s useful to anyone else.

Hi Umesh – the fix appears to have worked. Thanks!

Hi – thanks for your response – this is still an issue for me, now affecting 5 of my websites! At the moment I’m manually fixing it by adding the following line just before the return statement in the do_smushit function in wp-smush.php:

chmod($file_path, 0644);

If your developer could add that one line in, I’d be very grateful!

Best regards,

Chris