NOTE: This bug report is for Confluence Cloud. Using Confluence Server? See the corresponding bug report.

      There appears to have been a change on the Twitter end of the connection so embedding Twitter feeds in the Widget Connector no longer works. When embedding a Twitter URL and clicking preview nothing is displayed, even though the instances had their whitelists disabled.

      This behaviour has been reproduced in Confluence v4.3.7, v5.1.3 and also on the EAC. When changing the embedded URL for a YouTube video the content was embedded as expected, which suggests this is Twitter specific.

      Related WC ticket: https://ecosystem.atlassian.net/browse/WC-61

            [CONFCLOUD-29639] Twitter feeds have stopped working in the Widget Connector

            +1 -please fix this asap. 

            Stephanie Ong added a comment - +1 -please fix this asap. 

            please fix... the widget connector macro is pretty useless right now.

            Paul Saunders added a comment - please fix... the widget connector macro is pretty useless right now.

            Oh no!  Thanks for pointing that, Steffen.  I think it was the habitual period at the end of a sentence, but it doesn't know that.   If you give it a try, can you post comments here?  I would like to hear how it works out.  I'm not the admin of my Confluence instance so any real world experience I can pass along with a recommendation would be very helpful.  Thanks again.

            Terry Gannon added a comment - Oh no!  Thanks for pointing that, Steffen.  I think it was the habitual period at the end of a sentence, but it doesn't know that.   If you give it a try, can you post comments here?  I would like to hear how it works out.  I'm not the admin of my Confluence instance so any real world experience I can pass along with a recommendation would be very helpful.  Thanks again.

            stcl added a comment -

            @Terry, you included the dot into the link. It should be https://marketplace.atlassian.com/plugins/io.extensi-confluence-plugin-twitter-connector/server/overview.

            But no, I haven't tried it (yet). Thanks for the hint.

            • Steffen

            stcl added a comment - @Terry, you included the dot into the link. It should be  https://marketplace.atlassian.com/plugins/io.extensi-confluence-plugin-twitter-connector/server/overview . But no, I haven't tried it (yet). Thanks for the hint. Steffen

            This appears to be a workaround: https://marketplace.atlassian.com/plugins/io.extensi-confluence-plugin-twitter-connector/server/overview.  Has anybody given this a try and can provide some feedback?

            Terry Gannon added a comment - This appears to be a workaround: https://marketplace.atlassian.com/plugins/io.extensi-confluence-plugin-twitter-connector/server/overview.   Has anybody given this a try and can provide some feedback?

            Great! Thanks, using the search -type widget it now works.

            Juha Martikainen added a comment - Great! Thanks, using the search -type widget it now works.

            Giles B added a comment -

            Hi juha.h.martikainen@aalto.fi, You're right that it looks like Twitter have changed this again, but I did manage to find out that you can create a "Search" Widget. It won't take you to the publish.twitter URL, and still has the required ID.

            Once you create the search widget, edit it and grab the ID from the URL. I'll update the doc to add the type of widget you need to create.

            Giles B added a comment - Hi juha.h.martikainen@aalto.fi , You're right that it looks like Twitter have changed this again, but I did manage to find out that you can create a "Search" Widget. It won't take you to the publish.twitter URL, and still has the required ID. Once you create the search widget, edit it and grab the ID from the URL. I'll update the doc to add the type of widget you need to create.

            There must be something I do differently, as when I go to create a widget I end up in publish.twitter.com. The address bar only shows publish.twitter.com/# the whole time, there is no save anywhere only a created link tag with style options and an http address to the user whos timeline it shows. (For example using my own it shows : <a class="twitter-timeline" href="https://twitter.com/Kuura">Tweets by Kuura</a> <script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script> "

            Juha Martikainen added a comment - There must be something I do differently, as when I go to create a widget I end up in publish.twitter.com. The address bar only shows publish.twitter.com/# the whole time, there is no save anywhere only a created link tag with style options and an http address to the user whos timeline it shows. (For example using my own it shows : <a class="twitter-timeline" href="https://twitter.com/Kuura">Tweets by Kuura</a> <script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script> "

            Giles B added a comment -

            Hi juha.h.martikainen@aalto.fi, I've just tested the process on this page and it seems to work fine for me. The ID is in the URL when you create or edit a widget, and within the script tags as the "data-widget-id".

            Giles B added a comment - Hi juha.h.martikainen@aalto.fi , I've just tested the process on this page and it seems to work fine for me. The ID is in the URL when you create or edit a widget, and within the script tags as the "data-widget-id".

            The documentation is no longer valid as Twitter widget doesn't give id for the widget anymore, just a script link.

            Juha Martikainen added a comment - The documentation is no longer valid as Twitter widget doesn't give id for the widget anymore, just a script link.

            Giles B added a comment -

            Hi adam201,

            That page is actually gone from our current documentation, as there were a number of issues with it. The best page and most current page to look at is for the Widget connector macro.

            I'll update the page in the 5.7 docs also though.

            Giles B added a comment - Hi adam201 , That page is actually gone from our current documentation, as there were a number of issues with it. The best page and most current page to look at is for the Widget connector macro . I'll update the page in the 5.7 docs also though.

            Perhaps the docs should be updated: https://confluence.atlassian.com/conf57/widget-connector-examples-701435122.html still lists Twitter as an option for the widget connector.

            Adam Parkin added a comment - Perhaps the docs should be updated: https://confluence.atlassian.com/conf57/widget-connector-examples-701435122.html still lists Twitter as an option for the widget connector.

            According to the information provided here, this is duplicated by https://ecosystem.atlassian.net/browse/WC-69 and has been fixed in Widget Connector 2.2.0 (which is compatible with Confluence >= 5.2.3).

            Stefan Hett added a comment - According to the information provided here, this is duplicated by https://ecosystem.atlassian.net/browse/WC-69 and has been fixed in Widget Connector 2.2.0 (which is compatible with Confluence >= 5.2.3).

            David Maye added a comment -

            For OnDemand customers (who can't use the HTML macro due to restricted access to third-party plugins):

            You'll need Widget Connector v2.1.7 or later:

            What you'll need to do is to create a widget in Twitter (done so here), then look at the HTML at the bottom. In the HTML, you'll see a snippet of HTML code like this:

            data-widget-id="376730504411611138"
            

            What you are looking for is the 18 character data widget ID number. In the example above, it is '376730504411611138' but yours will be different. Copy your widget id number to the clipboard or a text file. Afterwards, log back into Confluence, edit the page and then add (or re-edit) the Widget Connector. In the Web Site's Widget URL box, type this:

            https://twitter.com/settings/widgets/376730504411611138/edit
            

            But instead of using 376730504411611138 (which is from the example) use your ID string for your widget. Refresh the macro view and you should see your Twitter feed come up.

            David Maye added a comment - For OnDemand customers (who can't use the HTML macro due to restricted access to third-party plugins): You'll need Widget Connector v2.1.7 or later: What you'll need to do is to create a widget in Twitter ( done so here ), then look at the HTML at the bottom. In the HTML, you'll see a snippet of HTML code like this: data-widget-id= "376730504411611138" What you are looking for is the 18 character data widget ID number. In the example above, it is '376730504411611138' but yours will be different. Copy your widget id number to the clipboard or a text file. Afterwards, log back into Confluence, edit the page and then add (or re-edit) the Widget Connector. In the Web Site's Widget URL box, type this: https: //twitter.com/settings/widgets/376730504411611138/edit But instead of using 376730504411611138 (which is from the example) use your ID string for your widget. Refresh the macro view and you should see your Twitter feed come up.

            The workaround that we will use is to create a widget and then embed the HTML from that widget in a Confluence page with the {\html} macro.

            Hope that helps.

            Cheers,
            Nicholas Muldoon

            Nicholas Muldoon added a comment - The workaround that we will use is to create a widget and then embed the HTML from that widget in a Confluence page with the {\html} macro . Hope that helps. Cheers, Nicholas Muldoon

            TomTom added a comment -

            +1
            Same issue here on Confluence v4.3.7 using Widget Connector v2.1.6.

            TomTom added a comment - +1 Same issue here on Confluence v4.3.7 using Widget Connector v2.1.6.

            Hi John,

            Twitter have shut down their v1 API. From now on all calls needs to be authenticated. Our Twitter macro for Confluence is also affected by this: http://demo.refinedwiki.com/x/rYKgAQ

            Emil Sjödin [Refined] added a comment - Hi John, Twitter have shut down their v1 API. From now on all calls needs to be authenticated. Our Twitter macro for Confluence is also affected by this: http://demo.refinedwiki.com/x/rYKgAQ

              Unassigned Unassigned
              jinder John Inder [Atlassian] (Inactive)
              Affected customers:
              32 This affects my team
              Watchers:
              34 Start watching this issue

                Created:
                Updated: