Hi rgallagher30,
Hope you’re having a nice day as well 🙂 How are you editing your FAQs, manually, using a page builder, etc. ?
It appears that either an extra opening or closing <div> may be present in the code. This could be because you’ve added an extra <div> HTML tag in one of your FAQs, probably unintentionally.
Kevin and I work together. The FAQ page is being built in the block editor in Gutenberg. The other services pages are built with Avia Layout Builder and we use shortcode to implement the FAQ.
This is the example of the first problem:
What it should look like: https://justmind.org/faq/
What happens after adding more than 2 exclude categories: http://williamasch.staging.wpengine.com/faq/
The plugin is also not allowing us to list multiple include categories without making everything disappear.
Hi again,
If you enter in the standard [ultimate-faqs] shortcode on http://williamasch.staging.wpengine.com/faq/ (not with Gutenberg blocks, rather just with the plain [ultimate-faqs] text pasted in), does the page display normally? If so, then, can you please try adding the exclude_category attribute to the shortcode? I just tested and it works fine with one, two or three different categories excluded. For example:
[ultimate-faqs exclude_category=”cars,bikes,trains”]
No. It does it either way. I also talked with our theme developer and they said the FAQ block is placed outside container and that is breaking the layout.
Hi again,
The div structure of the FAQs is correct. The FAQ block showing outside of the div it’s supposed to is because something is closing the div prematurely. That’s why I was asking you to check the FAQs to make sure there is no HTML directly in an FAQ that could be causing the issue.
If you’re certain you’ve checked all FAQs for any potential stray HTML, then you’ll need to find out what else in your WordPress install is causing the conflict. As a test, you could deactivate all your plugins, except for UFAQ, and see if that makes a difference. From there, you could reactivate your plugins, one at a time, until the issue reoccurs.
Another test would be to temporarily switch to the default Twenty Nineteen WordPress theme and see if that makes a difference.