Plugin Contributor
Nick C
(@modernnerd)
On further review, it appears this may be a bug in the plugin. It can be fixed for now by:
1. Editing wp-content/plugins/genesis-simple-faq/genesis-simple-faq.php using an FTP application or via Plugins → Editor if available.
2. Changing this line:
public $plugin_version = '0.9.0';
To this:
public $plugin_version = '0.9.1';
The site should then load the latest version of the plugin’s JavaScript, and the FAQs will appear closed by default.
I have reported this to the StudioPress plugin team.
Plugin Contributor
Nick C
(@modernnerd)
Hi @vasilisvj.
Thanks for this report.
I just posted a reply to a similar issue here that may be helpful:
https://wordpress.org/support/topic/all-faqs-appear-open/
In short, the issue can be caused by:
– A site serving an old copy of the jquery.genesis-simple-faq.min.js file.
– Another plugin removing the js class from the body tag.
Clearing all plugin, server-side, and browser caches may fix this. If that does not help, it’s worth disabling other plugins temporarily.
You are also welcome to share a link to the affected page if you’d like me to review this further.
Plugin Contributor
Nick C
(@modernnerd)
Hi, @avenirthinking.
Does your site include the ‘js’ class in your body tag when viewing it in your browser’s inspector?
It normally looks like this:
If that’s missing, the FAQs will appear open and uncloseable by default. The plugin usually adds the js class for you. If it’s missing you could try:
– Clearing all site and browser caches to make sure the latest version of plugins/genesis-simple-faq/assets/js/min/jquery.genesis-simple-faq.min.js is being loaded. (Version 0.9.1 of that file contains the string addClass("js").)
– Disabling other plugins temporarily (minification and caching plugins in particular could cause this).
– Double-checking that version 0.9.1 of the plugin is installed and active.
I tested Genesis Simple FAQ 0.9.1 with Academy Pro just in case; the js body class is present, and all FAQs appear closed by default and will open:
Plugin Support
Nick C
(@modernnerd)
Thanks for your report, @tr1nity2.
I checked this and only see jQuery loading once in my tests with Genesis Responsive Slider.
Genesis Responsive Slider loads jQuery once by default, and only if it’s not already loaded by another plugin or theme. It uses the wp_enqueue_script function and does not include jQuery directly.
If a site uses a theme or another plugin that adds jQuery directly without using wp_enqueue_script, that would explain why jQuery might appear more than once.
Plugin Support
Nick C
(@modernnerd)
Hi @leslieannetd.
SEO Data Transporter does not support The SEO framework / Autodescription plugin, which is why it’s not in the list. Supported plugins and themes are listed here:
https://wordpress.org/plugins/seo-data-transporter/#description-header
(You would choose either a supported theme with SEO features or a supported SEO plugin from the list — you don’t need to choose both a theme and a plugin.)
If you’re comfortable editing code, you could modify this plugin to support The SEO Framework. (You would need to add its name and the fields it stores data in to plugins/seo-data-transporter/seo-data-transporter.php.)
Or, if you’ve purchased Yoast Premium, you could approach their support team for other suggestions to migrate your existing SEO data: https://kb.yoast.com/kb/support/#premium
Plugin Support
Nick C
(@modernnerd)
Hi, Cyndi.
You can use this format to get “© Copyright 1998 – 2018 Your Company Name”.
[footer_copyright before="© " copyright="Copyright" first="1998" after=" Your Company Name"].
Hi, @pansotdev.
For me the icons appear with Genesis 2.6.0:
Some things you can try:
– Review your settings at Genesis → Simple Share to make sure buttons are set to appear on the pages you expect.
– Disable all other plugins.
– Check your browser’s JavaScript console for errors on the page where you expect buttons to appear.
If this does not solve the issue, feel free to share a screenshot of your Simple Share settings page (you can host the screenshot on a service such as https://imgur.com/), and a link to the page where this issue is visible.
Plugin Support
Nick C
(@modernnerd)
Great — thanks for letting us know you figured it out!
Plugin Contributor
Nick C
(@modernnerd)
@dwsmart Most screen readers will provide further context. For example in VoiceOver on Mac, the icon is read as: “Link, Image, Behance”.
This also gets repeated as you tab through the icons. (“Link, Image, Twitter”, “Link, Image, Facebook”…).
So longer labels are not necessarily better — it might be tedious to hear, “Link, Image, Go to my twitter profile”, “Link, Image, Go to my Behance profile”, “Link, Image, Go to my Facebook page”…
If there’s some other context you would expect to hear on each button to enhance accessibility, though, please feel free to share more.
Plugin Contributor
Nick C
(@modernnerd)
Hi @dwsmart.
The title tags inside the SVGs are there for accessibility to help screen readers: https://css-tricks.com/accessible-svgs/#article-header-id-6
Search engines will also be able to read the text, but should only present it if it’s deemed relevant to the search term, or if there’s not much other text on the page.
Plugin Support
Nick C
(@modernnerd)
Plugin Support
Nick C
(@modernnerd)
Sorry for the delay, @eventermom.
One way to display the hierarchy in the search widget is to edit each location with a parent term and add a dash before the name:
If you apply this to all child terms like this…
…you’ll then see the hierarchy reflected in the search widget:
If you prefer not to relabel your terms in this way, you could look at modifying the labels with a filter or with CSS. I don’t have ready-made code for this, but you could try asking the StudioPress community in case someone else has made the same change: https://my.studiopress.com/community/
Plugin Contributor
Nick C
(@modernnerd)
Thank you for this report, @raffywpg.
I filed an issue at https://github.com/copyblogger/genesis-connect-woocommerce/issues/23 so the templates can be adjusted in a future release.
For now, removing the schema markup in the plugin template manually is worth considering for this error.
Plugin Support
Nick C
(@modernnerd)
Many thanks for this report, Victor.
We have an open issue at https://github.com/copyblogger/genesis-simple-hooks/issues/16 and will address this there.
