Twitter Shortcode still doesn’t work
-
Please see https://wordpress.com/forums/topic/embedding-x-com-comments/ for details. I noticed this four months ago. Was surprised to see that this is not yet fixed. Any ETA on a fix please?
The blog I need help with is: (visible only to logged in users)
-
-
Hey there! Would you mind sharing an example of a page or a post where you have this problem?
-
see this post: https://ephemerid213andfriends.wordpress.com/2024/10/31/thursday-31st-october/comment-page-1/#comment-187544
there are also issues with twitter posts not embedding, whether they’re X or Twitter in the URL. See the same comment thread.
-
I can’t share a post because I would never publish a post with a broken shortcode!
Just try to use the Twitter short code with an x.com URL as described in the linked forum thread and you’ll see. All my posts use Twitter.com URLs to work around the problem.
-
Thanks! Both of the sites in question are using retired themes, themes that use the customizer, “Affinity” and “Twenty Eleven”. This embed issue is solved on up-to-date themes, such as block themes. I cannot provide an ETA or confirmation if this will be fixed for retired themes, but I would say it is unlikely that this will be done.
-
Can I just check I am understanding you correctly. Are you saying that you have fixed the Twitter shortcode but only for newer themes?
-
I’m skeptical that this is a solution. There is another site, that I’m an admin for (ovallyballs.sport.blog) has a block theme and if I post an x.com *or* twitter.com link, it’s not showing as embedded in the comment feed. However if I edit the comment, the twitter.com version shows the tweet in the preview – the x.com version doesn’t.
-
When using a block theme, you’ll want to make sure that Enable blocks in comments is enabled in your Discussion settings to make sure that users can take advantage of the recently-fixed embed block.
For our retired themes (that is, themes that are not available for new sites or maintained by our developers anymore), and themes as old as Twenty Eleven, I would not expect to see individual fixes deployed.
-
-
@honhonjaccuse from earlier forum threads by these users, they opted to use the simpler text comment box because their site visitors were having difficulties leaving comments with the block-based comment box.
Now it seems you’re saying that the text comment box does not support embeds any longer (images, videos, Gifs, etc.)?
-
The classic comment editor supports the same embeds that it always has (images and videos included), but has not been updated for
x.comlinks. The fix for automaticx.comlink embeds was implemented in the new comment editor. We may update our classic comment editor to add support forx.comembeds, but there are no current plans or ETA. -
I am unsure why there is so much discussion about comment editors in people’s explanations here. I am talking about the shortcode. I.e. you type in [tweet and then paste in a URL and the close the ]. This is not using any kind of block editor or any sort. I write all my blog posts with the classic editor directly in HTML.
it is the shortcode in that environment that doesn’t accept x.com URLs and you have to change then to twitter.com.
-
In context of the older forum post that you mentioned, the previous bug with
x.comembeds was fixed. However, regarding the classic editor, that has not been updating forx.comlinks. WordPress.com itself will not be fixing this issue, but it may be addressed in the future by the WordPress developer community here: https://make.wordpress.org/core/In general, I would expect much more development to go into the block editors, which have been the default way to build WordPress sites for a few years now. I highly recommend looking into switching to the block editor.
-
If you want a simple discussion blog, where people chat in the comments, the block version of the comment box is ridiculously over engineered and confusing for basic users.
-
Hi @honhonjaccuse,
I did try out the block editor before and utterly hated it, so went back to classic. Perhaps not a surprise really for someone who prefers to edit the raw HTML that an interface that removes all control from the user would not suit me.
I do feel that WordPress is not really catering to people like me any more, but it is surprising that it takes 4 months to not yet get around to adding x.com alongside twitter.com in the shortcode implementation. How difficult a fix is that to do?
At some point the lack of support and the increase in adverts covering the page so you can barely see your content will force me to move but it’s such a big task to take 12 years worth of content onto another platform that I’m putting it off in the short term.
Hopefully it will continue to hang together for a little while longer.
Cheers,
Morag
-
Thanks for your feedback! We at WordPress.com don’t have control over the wider community that contributes to the open-source WordPress project. However, many of the contributors also work here at Automattic and incorporate their experience with users of WordPress.com into their contributions. We do control some WordPress.com-specific features, primarily those that you’ll see when switching to the “Default view” as per this guide (though that is not the case across the board, our developers are in the process of revamping our platform to make some of this more clear and easier to navigate).
The request for
x.comembeds in the legacy comment form is reported, but I have no ETA on it and it may be a bit lower priority, due to the existence of other options that are higher priorities for development.Regarding ads, we specialize in providing the best high-performance managed web hosting for WordPress. It is a little bit unique in this space for us to offer an indefinite free version, so we do require WordPress.com ads on those free sites. Paid sites do not have ads. Those sites also receive direct support through our email and messaging channels.
I will mark this thread as resolved now. Thanks again for everyone’s feedback!
- The topic ‘Twitter Shortcode still doesn’t work’ is closed to new replies.
WordPress.com Forums 