From the screenshot, it looks like the LinkedIn connection is disabled. This can happen when the connection is broken in some way. With no available connections the ‘Custom Message’ field is disabled too.
I have tried to remove it in the orignal post
Has the post already been shared? If so, then the controls will be disabled because it can’t be shared again from the classic editor.
You could try reconnecting LinkedIn https://cloud.jetpack.com/jetpack-social and then checking if you can edit the message on a new draft post.
I hope that helps, but let us know if you’re still having any issues.
Hi Paul,
Thanks for getting back to me. I did disconnect then reconnect Linkedin but it didn’t do anything.
Yes, the orignal post had been shared – that makes sense, thanks
The only way I could get rid of it was via the database, I cleared all occurances of it in the table and it worked. Probably not the ideal solution but it’s a fix.
Ragrds,
A
Hello @agizzie,
Thanks for the follow-up. It seems like you’re set for now, am I right?
I’m going to mark this thread as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!
After clearing all instances from the database and disconnecting Linkedin and re-connecting. New posts are posting to Linkedin with the same heading still.
I have no idea where it’s pulling from?!
Any suggestions?
If you have LinkedIn connected, than by default the post will be shared to LinkedIn on publish, and unless you edit the custom message, it will use the post title and excerpt. You can clear the checkbox next to the connection to prevent it being shared, there is also a filter you can use to disable the connections by default publicize_checkbox_default but I wouldn’t advise using that unless you are confident making changes to the code.
The only way I could get rid of it was via the database, I cleared all occurances of it in the table and it worked. Probably not the ideal solution but it’s a fix.
What are you removing from the database? You mentioned that helped solve the problem in your previous response. Knowing more details here may help to diagnose the problem. The information used to share the post is stored in the post meta, but removing this after the post is published is unlikely to make a difference, as the process will have already been run to share the post to LinkedIn.
Could something else be sharing the post to LinkedIn? Do you have any other automations on the site?
Hi Paul,
Thanks for your reply.
“…unless you edit the custom message, it will use the post title and excerpt.” < However, as I have already explained they are not, they are showing the custom message from an old post. The same ONE on ALL posts 🙁
“You can clear the checkbox next to the connection to prevent it being shared” < The sharing isn’t the issue, I want the posts to be shared.
All of the posts are scheduled, once the scheduled date and time arrive they are posted as expected. However, once they hit Linkedin they are given the title of the same old post, and not the given title as they should.
Looking at the posts which are yet to be posted ie those still scheduled to post in the future. As previously mentioned the custom message box is uneditable and greyed out.
“What are you removing from the database?” < I removed from the post meta in the database, all occurances of the special comment that all posts were grabbing from the old post. This removed the repeted custom message on wordpress. I thought this had fixed the problem. However, since then the posts that were scheduled after the event, when posted on Linkedin they had the same custom message as a title and not their title.
The only thing I can think off which is playing on my mind a bit is… these posts have been duplicated using EA duplicate and I’m editing the content of the post – BUT if it is a case of EA duplicate why then can I not edit the custom message when I edit the content of the post? So it may not be that. :-/
Ah if it’s the same title being used for all posts, and they were duplicated from that post, then it could indeed have something to do with it. We also have other meta values that ensure we don’t accidentally share posts twice. This also would cause the controls to be disabled, so my hunch would be that those meta values are being duplicated with the post.
On one of your scheduled posts where you can’t edit the message, if you could try looking for the meta value _wpas_done_all and if it exists, deleting it. I think that should help.
For a more permanent fix, maybe there is a hook which can be used to stop certain meta values from being duplicated, or there could be another post duplicator plugin which would allow this level of control.
I hope this helps!
Thanks Paul,
I’ve deleted the _wpas_done_all on this coming Monday’s post, so time will tell if it works. Will keep you posted.
A
Please do! The _wpas_done_all meta key will have been preventing you from editing the custom message, but the other post’s custom message may still be present an the duplicated one.
If possible, it would be good to edit the post scheduled for Monday and see if you can edit the custom message for it. You could also delete the _wpas_mess key for the post, and that will have it use the default message.
Hi Paul,
I’ve edited Monday’s post and can confirm I can edit the custom message. Fingers crossed we’ve cracked the problem – will know come Monday.
Thanks again for your help.
Regards,
A
Monday’s post has posted to linkedin this morning with the correct title!
Looks like we have craked it, thanks again for your help.
Regrads,
A
Great, it sounds like we’ve indeed cracked the problem, and I’m really happy we could work through this together!
Since we’ve reached a successful resolution, I’d be grateful if you’d consider leaving a review for Jetpack Social. Your feedback is incredibly valuable, not just to us, but also to others who may encounter similar issues. It would be a great way to share your experience and help the community.
You can leave your review here: https://wordpress.org/support/plugin/jetpack-social/reviews/#new-post
Thank you in advance! And if you have any other questions or issues in the future, feel free to reach out anytime.
No worries, all done for you
