Home>Support>SiteOrigin elements width gone bad on Athemes Moesia…

SiteOrigin elements width gone bad on Athemes Moesia…

Updated an Athemes theme, Moesia, to a new version (1.41) and now SiteOrigin elements are full width of the page, though the native Moesia widgets/elements are having no issues and staying to the theme’s established width. Anybody else have this issue?

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, 6 months ago Alex S
    Hi, I Work Here

    Hi Michael,

    Do you have a public URL where we can take a look at what’s going on?

  2. 6 years, 6 months ago Michael Semer

    It’s http://www.michaelsemer.com.

    The theme devs (aThemes) had me insert the following code into the style.css in place of line 1934:

    .widget_moesia_services.container,
    .widget_moesia_action.container,
    .widget_moesia_clients.container,
    .widget_moesia_testimonials.container,
    .widget_moesia_employees.container,
    .widget_fp_social.container,
    .widget_moesia_latest_news.container,
    .widget_moesia_projects.container,
    .widget_moesia_facts.container,
    .widget_moesia_skills.container,
    .widget_moesia_blockquote.container {

    So that fixed the container width issue. But 2/3rds of my footer widgets have vanished and I can’t replace them for some reason.

    I do a lot of work on client sites in Avada/Fusion and never have these issues when an upgrade hits, I can attest.

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

    Hi Michael,

    Very sorry for the delay.

    it looks like you’ve managed to resolve the issue you’re having with your footer. Do you still need help with this? If not, I’m very sorry I wasn’t able to reply sooner.

    Please note that the icons (when clicking the above link) are showing up like a square because that’s what your browser uses to tell you it can’t render the font. It can’t render it due to a Cross-Origin Resource Sharing Policy (CORS) issue.

  4. 6 years, 5 months ago Michael Semer

    No, I haven’t. As I said, most of the widgets vanished – all of Footer A, half of Footer B, gone. The Appearance/Widgets menu is being balky, too. Took the better part of an hour to just restore my copyright line, and I can’t explain why it chose to start working for that single widget. Others won’t even save, and those that do save don’t display

  5. 6 years, 5 months ago Michael Semer

    And which icons do you mean? Don’t see any problems in Chrome or Safari…

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

    Hi Michael,

    Can you show me a screenshot of your widget set up for the missing footer widget area? Please note that we’re currently unable to process attachments at this time so you’ll need to use a third party image hosting service, such as Imgur or vgy.me. I suspect you’ll need to get help from aThemes to fix this issue you’re having as based on what you’ve stated and your general widget usage, you seem to be only really using the Moesia widgets (which are widgets made specifically for Moesia). Are you missing any SiteOrigin widgets?

    Regarding the icons, it’s not a browser issue I’m pointing – it’s a domain issue. Please open this link and scroll to the bottom. The social icons are displaying without issue. Now please open this link and check your footer, you’ll notice the icons display incorrectly now.

  7. 6 years, 5 months ago Michael Semer

    Here’s an Imgur link of how I wanted to set up the widgets. Neither SO or Moesia widgets will display in Footer A. It took repeated attempts to get the copyright line to display in Footer B. https://imgur.com/WzN8hot

    How do I fix the domain issue?

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

    Hi Michael,

    If you move those widgets to the second footer area, do they work? If so, that sadly suggests this is a general theme issue. Are you able to add a basic WordPress widget (such as the Archives widget) to the first footer column?

    How do I fix the domain issue?

    Unfortunately, this isn’t something we can directly assist with. I would recommend reaching out to your hosting provider or alternatively, follow the instructions outlined in the previously provided links.

  9. 6 years, 5 months ago Michael Semer

    Thanks…I’ve tried everything and nothing “sticks”. What’s notable is that when I leave or reload the Widgets menu in my theme’s (Athemes Moesia) WP sidebar, none of the changes I’ve made get saved. Though they seem to individually “save” when I drag-and-drop and save them when I’m inside that menu page, it doesn’t matter; when I return to the Widgets menu or reload it, none of my changes has been saved.

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

    Hi Michael,

    I would try running a plugin conflict test to see what’s preventing the changes from saving on your widgets page.

  11. 6 years, 5 months ago Michael Semer

    The entire Plugins menu has gone unresponsive. I updated one plugin, but now I can’t deactivate any to run a conflict test.

    The Site Origin Widgets menu under Plugins isn’t responding, either, though I just uploaded the Widgets Bundle update. Just doesn’t accept my changes when I try to deactivate or active widgets.

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

    Hi Michael,

    Are you sure that’s as a result of us? I ask because we honestly don’t make any real changes to the WordPress widgets page.
    Would it be possible for you to create a temporary admin account for us so we can log in and take a look?

  13. 6 years, 5 months ago Private Message - Alex S Hi, I Work Here

    This is a private message.

  14. 6 years, 5 months ago Private Message - WordPress

    This is a private message.

  15. 6 years, 5 months ago Michael Semer

    Done, and thanks in advance!

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

    Hi Michael,

    Can you please recreate the account? I ask because the emailed link wasn’t clicked in time and is now valid. Typically this is fine as we can reset the password later by filling out a form on your website but the CAPTCHA form on your website doesn’t appear to be valid – it rejects us regardless of whether the answer is right or not. I’m very sorry about this!

  17. 6 years, 5 months ago Private Message - WordPress

    This is a private message.

  18. 6 years, 5 months ago Michael Semer

    OK, did it again.

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

    Hi Michael,

    Thanks!
    Can you please disable your login Captcha? I ask because, unfortunately, no matter what we do it rejects our submissions (regardless of how valid they are or not).

  20. 6 years, 5 months ago Michael Semer

    I will literally have to delete Captcha, which apparently is no longer being updated…and I find I can’t deactivate it. Several plugins have gone bust of late.

  21. 6 years, 5 months ago Michael Semer

    There’s also a Really Simple Captcha plugin at work…try again and let me know, and I’ll delete it. I just had to delete Captcha. WP Jetpack bundle also become unresponsive so I deleted it. Still can’t deactivate from the plugins menu, so I need to delete them at the host.

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

    Hi Michael,

    Thanks. I’m able to log in now.

    Hm. That’s odd. Is this the only page where changes aren’t taking effect? If not, do you have any server side caching?
    If so, did you try using the widgets page with a different theme? If you did and that didn’t work, would it be possible for me to create a backup of your website for local testing?

  23. 6 years, 5 months ago Michael Semer

    Alex,

    I’d love to change the theme, but now I find I can’t do that, either. In Live Preview it says it’s publishing the theme change, but nothing happens; on the Themes page, the themes aren’t responsive at all to activation. So I’m stuck in Moesia.

    So go ahead and do a backup, with my blessings!

  24. 6 years, 5 months ago Michael Semer

    Spoke with my host support, who flushed my DNS cache and CloudFlare cache, fixed site files and folders permissions, increased site memory limit from 128 to 768mb and added the default WordPress .htaccess code in the .htaccess file. No change so far to any of the bugs.

  25. 6 years, 5 months ago Michael Semer

    Never mind. Database corruption; my host fixed it!

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