Home>Support>Widgets Bundle v. 1.17 Full-Width Problem

Widgets Bundle v. 1.17 Full-Width Problem

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].

Hello all! Has anyone had any issues with full-width widgets not working on the front page in version 1.17? I was able to roll back to version 1.16.1 and the problem is fixed. For some reason [on front page only] full-width banners and posts carousel do not occupy the full width of the page.

Non Site-Origin objects work full-width no problem and again it only seems to happen on the front page.

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

  1. 5 years, 7 days ago Andrew Misplon
    Hi, I Work Here

    Hi Chapman

    Thanks for reaching out.

    We aren’t currently aware of any full-width issues. Please, send a link to a page displaying the problem and we’ll take a look.

  2. 5 years, 7 days ago Chapman Hosier

    Hi Andrew, thank you so much for the response! lorisarvisandassociates.com/

    I am only experiencing this issue on the front page – all other pages are fine. The widgets affected are the banners in green (No matter your unique situation…, etc.) and the post carousel towards the bottom of the page.

    Currently they are displaying correctly as I have rolled back to the previous version, but if you’d like me to update so you can see it – just let me know.

    I really, really appreciate the help!

  3. 5 years, 7 days ago Andrew Misplon
    Hi, I Work Here

    Sure, no problem. If you could update so we can see the issue, that would be helpful.

  4. 5 years, 7 days ago Chapman Hosier

    Thank you Andrew – I just updated. Issue can be seen at lorisarvisandassociates.com/

  5. 5 years, 7 days ago Andrew Misplon
    Hi, I Work Here

    Thanks. Try to establish a working baseline. Temporarily deactivate all plugins not authored by SiteOrigin, does the issue resolve in that state? If not, temporarily switch to a default theme like Twenty Nineteen, does the issue resolve?

  6. 5 years, 7 days ago Andrew Misplon
    Hi, I Work Here

    If any caching plugins are in use, they should be cleared before the first step, thanks.

  7. 5 years, 7 days ago Chapman Hosier

    Andrew, I can solve the issue by rolling back to the previous version of widgets bundle. I’ve been using page builder with this theme for 3+ years and never had an issue until the 1.17 update.

  8. 5 years, 6 days ago Andrew Misplon
    Hi, I Work Here

    Hi, thanks for your feedback. The tests outlined should only take a minute or two, they’re quite quick, we’re just seeking a working baseline at this stage.

    If you open the browser console, you’ll see two JS errors. One of the errors relates to a dependency for the carousel widget. The carousel was recently updated. It’s hard to say why the dependency isn’t loading. It could be a caching issue or it could be a plugin or theme conflict.

    The other error is a JavaScript error being produced by the theme. I can’t say at this stage why the theme is producing this error. This error could potentially interfere with other JavaScript actions on the page like the full width stretched functionality.

    It’s possible to take a more targetted troubleshooting approach but it’s also more technical and time-consuming. A quick plugin and theme conflict test will establish if a working baseline is available to facilitate further testing.

    Here is what the console errors look like and here is how to open the console if you’d like to take a look https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis.

  9. 5 years, 1 day ago Chapman Hosier

    Hi Andrew,

    Understood – thank you for the response. I disabled all non-Site Origin plugins and the issue persisted, however temporarily applying the Twenty Twenty theme did fix it.

    Obviously the theme is not a Site Origin product and therefore not your problem but, if I may be so bold as to ask – would you happen to have any suggestions for possible next steps for me?

    I really appreciate your time and help on this.
    Chapman

  10. 5 years, 21 hours ago Andrew Misplon
    Hi, I Work Here

    Thanks for testing.

    SiteOrigin plugins aside, it would be best to resolve the JS errors being produced by the theme.

    jquery.spasticNav.js?ver=5.4.2&time=1594847195:22 Uncaught TypeError: Cannot read property 'left' of undefined

    Resolving the theme’s JS issues should resolve the issues impacting SiteOrigin plugins.

    Here is how to use the console to check for errors in red text: https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis. You could ask theme support to lend a hand resolving theme produced JS errors. If that isn’t possible, a third-party developer would need to lend a hand. Codeable.io is an option to hire one if you don’t know of any.

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