-
Notifications
You must be signed in to change notification settings - Fork 799
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publicize Custom Message Doesn't Show In Twitter #11752
Comments
Thanks a bunch for the report! We'll be looking into it. |
Hey @tyxla ! Is there an update we should share with the user on this one? |
Hey @xpurichan! Unfortunately, I haven't been able to reproduce this one. Perhaps we can ask whether the user can reproduce it consistently? |
Hmm I was also able to reproduce this on my test site simple site. Will ask the user if they notice it happening consistently. |
The user confirmed that they have tested this twice and both times produced the same result. |
I've been able to reproduce when featured image is specified. Seems like this is a race condition again, @enejb since you recently worked on a similar fix, do you have an idea why this might be happening? |
Just adding a note here as the original request popped back up in 1630181-zen . Putting it back on hold for now. |
Hey @tyxla ! I was just checking to see if we had an update for the user? |
I'm adding a note because the request popped up again in 1630181-zen . Are there any updates? Putting it back on hold for now. |
@ccwalburn no updates yet. |
Let me know if when there is an update do that I can inform the user 1630181-zen. I've closed their ticket but would like to let them know when we have a fix. |
I have another user with this issue. 1858342-zen. Are there any updates? |
New report on 1814025-zen. They also had some interesting input to share based on some testing they have performed:
|
Should we remove the |
I can't seem to reproduce on my end right now. If I add a custom message to the Publicize custom message input field, that custom message is used on Twitter. Here is an example with a Jetpack site: https://twitter.com/jeherve/status/1110503318672101376 And here is an example with a WordPress.com simple site: In both cases, I was using the Block editor. Noting that I tested with Twitter, as per the issue's title. I did not test with LinkedIn. I am mentioning this since one of the screenshots above was a LinkedIn profile page. @gwensmithx Can you still reproduce the issue? If so, could you make a screenshot of your custom Publicize message before you publish your post? Thank you! |
Another report of this in #1959253-zen I asked for specifics on the posts that were affected, because the behavior was also inconsistent on the user's site. |
Another report of a user encountering this where instead of the excerpt text appearing, it was just the title of the post with the link to the post. The instance where the user published post with excerpt text and it shows just the title of the post and link to the post - https://cld.wthms.co/OSb7Tp Excerpt text from post here - https://cld.wthms.co/8cPIxp Follow up ticket 1986944-zen |
@susanjanec Do you happen to know which editor the author used to publish their post? |
@jeherve They were using the Block editor. |
Sorry, I should have been clearer with my question. Was this the editor in Calypso or the one in wp-admin? |
Maybe related, for WP.com simple sites Workaround suggested helped. |
Another report in 3140379-zen |
Another case in 3156201-zen. Provided the workaround above. |
Another case 3187472-zen. Provided the workaround above. |
related or possibly duplicate issues: |
Another one 3310080-zen |
User reported this in 3329751-zen, provided a screen recording detailing how the custom message was not used when creating a new post. Shared the workaround mentioned in this thread. |
I found another case here: #11752 |
@supernovia 11752 is this issue? Copy/paste error? |
I found another one here 3390585-zen. Provided the workaround above. |
Also reported by a site owner in the WordPress.com forums, I gave the suggested workaround |
I also experience this issue from time to time. It just uses the title of the post instead of my custom message. I will try the workaround to first save a draft with the custom message, waiting for confirmation and then publish the post. |
This is enough, thank you! You'll get notifications as soon as we start working on this. |
Thanks! I hope it will be fixed soon. It would save some time for performing the additional steps. |
anther report here 13852883-hc |
Also, 23579779-hc |
Another issue 3480592-hc |
Noting that https://core.trac.wordpress.org/changeset/49172 may help us fix this, at least for our users who use WordPress 5.6. Maybe we can update Sync accordingly. Related: #14269 |
This should be fixed in Jetpack 9.2 for folks using WordPress 5.6 (scheduled to be released on December 8): #17838 |
I didn't see this issue in the related issues so I decided to post. I hope I'm posting in the correct spot! I was trying to replicate an issue a customer had with displaying the Custom Message in Twitter from the new Publicize feature in Gutenberg. The custom message was not showing, but the rest of the post was posted to Twitter successfully.
Steps to reproduce
Starting at URL: https://gwentestsite733700880.wordpress.com/2018/12/09/test-post-title/
^ This is my test site. I installed the theme TheFour and used my Premium Plan.
Create a new blog post using Gutenberg editor.
Add in featured image and content. Clicked JP Icon to publicize and connected my Twitter account (@Nvision_WebDev) and put in my custom message.
Clicked "Publish" post - looked everything over (JP was connected - message was in), confirmed Publishing.
Checked my twitter account to see post. Post was posted with my featured image and snippet of content but no custom message.
What I expected:
I expected to see the Custom Message from Publicize in my Twitter Post.
What happened instead:
The post was posted without the Custom Message.
Browser / OS version:
Mozilla Firefox Quantum - Windows 10
Temporary Workaround
Steps shared (h/t: @marutim):
The text was updated successfully, but these errors were encountered: