Hi gyz,
As for them not being hidden, just make sure you don’t have FAQ Category Toggle enabled (in the Basic area of the Settings page).
If you don’t want category headings to display, then you don’t have to group them by category. Just make sure “Group FAQs by Category” is disabled (in the Ordering area of the Settings page).
Thread Starter
gyzhor
(@gyzhor)
@jaysupport
I was hoping to find a solution that wouldn’t involve global settings, because I have two different FAQ pages with two different layouts.
I’ll see what I can do if and when we can solve the other two issues I’ve submitted.
Thanks again for all your help!
~gyz
There is no way to disable the category toggle for just one category or one instance of the shortcode.
If you wanted to hide the category headings for just one instance of the shortcode, what you could do is just wrap the shortcode in a div with a unique ID. For example:
<div id="my-new-div">
[ultimate-faqs]
</div>
And then add CSS that targets only that div. For example:
#my-new-div .ewd-ufaq-faq-category-title {
display: none;
}
Of course, if doing that, you’d want to make sure to have the category toggle disabled, as there will be no headings to click on to open the category.
Thread Starter
gyzhor
(@gyzhor)
@jaysupport
Hm. There’s probably a script I could use to trigger the category click onLoad, but that feels like a sloppy work-around.
So there’s no way to use multiple IDs like [select-faq faq_id='4076,3129'] without defaulting to a category header, and no way to call each FAQ separately, like
[select-faq faq_id='3129']
[select-faq faq_id='4076']
[select-faq faq_id='2196']
and have them not default to open?
As for the script, it might be possible, but that would be getting in to customizing the plugin to do something different than it is currently designed/coded to do, and, unfortunately, customization goes beyond the scope of our support.
While not suggested, you can call as many different shortcodes as you want, if you want. But they will start opened and show the category headings, unless you use the built-in filters (mentioned in the changelog entry for version 2.0.5) to bypass this.
-
This reply was modified 5 years ago by
jaysupport.
