Footer turned into 'Sidebar" after theme update

Support
#1

Hello,

I recently (today) updated to the most recent version of the X theme. We’ve had a slightly modified (via child theme) version of X integrity running for years with little issue. After the update though, some of the pages have shifted their footer from a 100% width footer at the bottom of the page, to a right sidebar-looking section. The “break” appears to be after div entry-content and before the footer class x-colophon top.

The shift appears to happen only on pages where there is a form (by Formidable Forms) located inside an X accordion feature, as the last element on before the footer.

On pages where we have the exact same feature (form inside an accordion), but other elements below it, there is no issue.

Additionally, if you open the ‘broken’ pages in cornerstone, the page looks normal (footer at bottom).

Looking through the Chrome inspector, I see no obvious reason for this issue. But removing the formidable form from the accordion clears things up.

Whats changed in the X theme that would cause this issue?

Thanks.

#2

Hi There,

Thank you for the very detailed post information. This has nothing to do with the update. I have inspected the page and it turns out that you have inserted a contact form inside an accordion element. In this contact form there were broken and unclosed html <div> tag which messed up the whole layout.

Could you please check your contact form and make sure that all your html code especially the <div> tags is properly closed?

Hope this helps. Please let us know how it goes.

#3

Hi,

Thanks for your response and help! All fixed.

Funny, I had manually reviewed and also ran an automated div checker before I posted, both appeared to come up clean.

Additionally, we have several different forms, all styled the same but with slightly different fields, and inserted with shortcodes…so assumed all pages using them should be identical (in terms of code)…and this issue only presented itself on 2 (of 8 pages) with forms. Turns out just one form (used on both of those pages) had a single missing div.

Its odd it only started displaying after the update though, as the form code hasn’t changed in years.

Anyway, all fixed now. Thanks again!

#4

Glad to hear!