-
-
HI,
I’d love to use the codeles function ‘FAQ’ with the advantage to manage the FAQs in separate posts.But, unlike the templates in WPBakery, I have only two icons (‘simple’ and ‘with circle in left’) with the Codeless FAQ elements.
Additionally, the first item always opens when the FAQ page is accessed.Therefore specifically my questions:
– Where can I set that the FAQ entries respectively the first entry on the page are displayed closed (or all opened)? Possibly also via code or CSS changes.
– Is there a way to set up other icons and resize them, as is possible with WPBakery FAQ elements?Any chance to help?
-
This topic was modified 3 years, 4 months ago by
reutli.
-
This topic was modified 3 years, 4 months ago by
-
-
If you’d provide the code to be customized I’d like to try it. Where has the code to be altered? If in the theme may be this could be done via cild theme?!
A first step would be helpful to get the first entry closed by default.
Any help is appreciated!
Thanks in advance.
-
Hi,
Now, the first entry of faq is closed by default.
P.S This is not theme customization. This customization is done within the plugin “Specular WPBakery Addons & Backward Compatibility”.Thanks,
-
Hi,
cool, thank you.
Can you please provide the code you’ve changed and where exactly, due to documentation.Thanks a lot in advance.
-
-
-
-
-
-
Hi,
Both are correct paths. The path that I mentioned is from Wp-admin dashboard. While the path you mentioned is from file manager or FTP.Thanks,
-
-
hey cool, learned something new! I was not knowing the way to change files via “plugin editor” ;o)
So I should save this file to be sure in case of an update, right?
Thanks for supporting.
May be there’s hint for changing symbols or an suggestion for the next version for Dev Team to make this adjustable in backend (i.e. adjusting toggling {all open, all closed}, {change symbols}, etc.)?
Both would be great.
-
Hi,
Yeah sure :)
I hope dev team will also add this in our upcoming theme/plugin update.Thanks for your suggestion :)
-
-
You must be logged in to reply to this topic.