Home>Support>Jetpack Twitter Timeline Widget over filtered?

Jetpack Twitter Timeline Widget over filtered?

Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].

I’ve got a simple row with two columns, one of which contains a Jetpack Twitter Timeline widget. I say that it might be being aggressively filtered, because what I’m seeming appears like the JS isn’t loading (and, in fact, no Twitter JS is called in the page source).

What I get is just the widget title and the “My Tweets” link.

If I add the widget to a separate sidebar area that doesn’t use the SiteOrigin page builder at all, not only does the timeline render normally, but the one in the page builder row also works fine.

I haven’t dug into it in depth yet, but it really seems like you’re filtering out the JS sources inserted by the widget (maybe other things, too).

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 6 years, 10 months ago jalberts

    Interesting follow up. This might have to do with how (or when) sidebars are handled in Page Builder.

    I registered a new sidebar, dropped the Timeline widget into it, but didn’t actually display it anywhere on the site. I also don’t have the widget in any other normally registered sidebars. The Twitter Timeline within a Page Builder section will work in this scenario. Much like if I put it into a sidebar that actually does get displayed on the site/page.

  2. 6 years, 10 months ago jalberts

    Possibly a result of this:
    https://github.com/siteorigin/siteorigin-panels/issues/578

  3. 6 years, 10 months ago Alex S
    Hi, I Work Here

    Hi Jalberts,

    Do you have a public URL where we can take a look at your usage?

    I registered a new sidebar, dropped the Timeline widget into it, but didn’t actually display it anywhere on the site. I also don’t have the widget in any other normally registered sidebars. The Twitter Timeline within a Page Builder section will work in this scenario. Much like if I put it into a sidebar that actually does get displayed on the site/page.<

    That actually makes sense. Specifically, if the sidebar isn’t set up to show anywhere it won’t show anywhere. SiteOrigin Page Builder doesn’t actually rely on the sidebar functionality so it doesn’t need a dedicated sidebar set up for it to work or anything like that.

  4. 6 years, 9 months ago jalberts

    Sorry for the delay.

    I don’t have a public URL anywhere with it not working at the moment, nope.

    I think you may have misinterpreted that part you quoted from me. Let me see if I can explain it a bit better.

    With the timeline widget not placed into any normally registered sidebar, placing the timeline widget into a Page Builder section results in a timeline that doesn’t list recent tweets. It just links to “My Tweets”.

    Placing the timeline widget into a normally registered sidebar, even if that sidebar is not called in any code anywhere on the web site, results in the timeline widget in a Page Builder section to properly load a list of tweets.

    It’s been a bit since I looked at the code, but I think Jetpack’s timeline widget depends on sidebar activation to ensure it loads all of its resources (JavaScript especially). By not actually using the sidebar functions in Page Builder, the widget “breaks” (falls back to simple functionality) because its activation hook doesn’t get called.

  5. 6 years, 9 months ago Alex S
    Hi, I Work Here

    Hi Jalberts,

    Ah. My mistake. I’ve been able to replicate this issue and I’ve logged this as a bug (specifically, this is an issue with our sidebar emulation) in our issue tracker. We’ll investigate this as soon as possible and try come up with a fix.

  6. 6 years, 9 months ago jalberts

    No worries. Glad you were able to replicate it :D

    Thanks for the response and for logging the bug!

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More