Nick C
Forum Replies Created
-
Forum: Plugins
In reply to: [Simple Social Icons] Removing title tag from icon SVG’s@withacause It would be worth reporting the error to the developer of the SEO site checker tool as a possible bug.
While multiple title tags in the head could be a sign of an issue, title tags elsewhere on the page in SVGs are valid and designed to improve accessibility as referenced above.
It sounds like the tool may be flagging these title tags without cause. I would not expect them to negatively affect SEO.
Forum: Plugins
In reply to: [Genesis Simple Hooks] Fatal errorHi, Maria!
Please could you update the Genesis framework to the latest version? (Currently 2.6.1.)
You should find this clears the error.
Details on how to update if you need them are here: https://wordpress.org/support/topic/genesis-2-2-1-breaks-the-genesis-simple-hooks-page/#post-10171238
Hi, @swilliams2207!
I checked the homepage at https://kitchenswagger.com/ and see the icons in black within the site’s header and footer. (I tried Chrome, Firefox, and Safari.)
If you’re still seeing this on multiple devices, please feel free to share browser/OS info.
Forum: Plugins
In reply to: [Genesis Simple Hooks] Execute PHP goneHi, @roldyclark.
I recommend checking that the WordPress user you’re logged in as is either an Administrator or a role with the ‘unfiltered_html’ capability.
For non-admin users, you can use a plugin such as User Role Editor to check capabilities for each role. (After installing that plugin, visit Users → User Role Editor, then select the role, such as “Editor”, and make sure “unfiltered_html” is ticked. Note that this will change the capability for all user with that role.)
The “Execute PHP on this hook” option in Genesis Simple Hooks will only appear if you have the “unfiltered_html” capability. It sounds like installing and uninstalling the Unfiltered MU plugin you mention has removed the capability for your user.
Forum: Plugins
In reply to: [Genesis Simple Hooks] Genesis 2.2.1 Breaks the Genesis Simple Hooks PageThank you for sharing these error logs, @ktbrothers and @cinghaman.
Please could you try updating the Genesis framework to version 2.5.0 or higher? (The latest is 2.6.1, available from your StudioPress account area or WordPress updates page if “check for updates” is enabled at Genesis → Theme Settings.)
The “Call to undefined function genesis_scripts()” message could appear if you’re running a version of Genesis before 2.5, which is when
genesis_scripts()was added.Hi, @jeff9661, and thanks for the report.
It’s worth also trying this with 0.9.10:
– Saving WooCommerce shop page settings again even if the pages appear set correctly.
– Recreating and reassigning the shop/cart/checkout pages.
Forum: Plugins
In reply to: [Simple Social Icons] Facebook and Twitter CountHi, @amblogdesign.
The site’s blog posts such as this one are using an old version of the share button markup: https://maunelegacy.com/bacon-egg-avocado-bake/
They should look more like the buttons presented in the theme developer’s demo site here: https://studiomommy.com/ellie-jane/sample-post-for-emma-blake/ (note Google+ and Twitter share counts are no longer available, so those buttons have no counts).
You could try:
1. Clearing any caching plugins or services in use.
2. Removing and reinstalling the plugin from the Genesis Simple Share page: https://wordpress.org/plugins/genesis-simple-share/
3. Approaching the theme developer for their thoughts as to why your site differs from their demo: https://studiomommy.com/submit-a-support-ticket/.Once the button markup has updated you may find the counts are restored.
(This was posted in the Simple Social Icons forum, by the way. I think it was meant for Genesis Simple Share: https://wordpress.org/support/plugin/genesis-simple-share. If you need further help, please feel free to follow up there.)
Forum: Plugins
In reply to: [SEO Data Transporter] Tarnsfer from the SEO Framework to YOAST PremiumHi @leslieannetd.
‘Records ignored’ means SEO Data Transporter found data for fields using your new SEO plugin’s field names. These don’t need to be converted so there’s no further action to take here.
Thank you also for mentioning that The SEO Framework uses the same SEO field names as Genesis — that’s good to know, and I’m glad it worked out!
Forum: Plugins
In reply to: [Genesis Simple Hooks] Genesis 2.2.1 Breaks the Genesis Simple Hooks PageOne other thing you can try is to take a backup, remove all content on the Simple Hooks page while using 2.2.0, and then update to 2.2.1.
If the error is not visible in 2.2.1 with no content in any of the hooks fields, the issue relates to custom code in the hook fields. In this case you can review the logs as above for errors relating to PHP in hook field content.
Forum: Plugins
In reply to: [Genesis Simple Hooks] Genesis 2.2.1 Breaks the Genesis Simple Hooks PageHi, @ktbrothers.
Thank you for this report.
The “Error Rendering Page” message is a generic error specific to Pagely. If you follow these instructions, Pagely will present the logs showing the actual PHP error causing them to display their error page:
https://support.pagely.com/hc/en-us/articles/204357740-Debugging-Errors-on-WordPress-Viewing-Logs
If you’re able to share a copy of the PHP error log with us it may prove helpful in solving this and taking action as you request. You could use a staging site or contact Pagely support if you do not wish to update to Genesis Simple Hooks 2.2.1 on your live site.
If you prefer not to post the error log here, you can contact us at https://my.studiopress.com/help/ or
support [at] studiopress [dot] comwith a copy of the logs and a link to this forum topic.Forum: Plugins
In reply to: [Genesis Connect for WooCommerce] UpdateGlad the CSS helped, @bamideleayo!
For your other questions, please could you submit a ticket to https://my.studiopress.com/help/ with more information about what colours you expect to see and a link to the affected pages?
It sounds like these are not related to Genesis Connect, but the StudioPress support team can review the issue in more detail for you.
Forum: Plugins
In reply to: [Genesis Connect for WooCommerce] UpdateThank you for this reply.
Genesis Connect does not style any element of WooCommerce, including checkout forms and coupon boxes, as it’s not possible to adjust form styling for all themes.
If the box appears too small by default, you could add custom CSS to Executive Pro’s stylesheet or to Appearance → Customizer → Additional CSS to increase the size of the box.
The CSS you use can depend on the version of your theme and what other plugins you have active, but usually looks something like this:
.woocommerce-cart .woocommerce table.cart td.actions .coupon .input-text { width: 200px; }Adjusting the 200px value there will control the width of the coupon input area. You may need to clear caching plugins and your browser cache if you do not see changes reflected immediately.
Hi, Åsa.
I replied to the email support request you submitted, but please feel free to follow up there if you need further help with this.
For others reading this with the same issue, there is a prerelease version of the plugin with a potential fix for the issue in this thread: https://wordpress.org/support/topic/product-category-pages-have-lost-their-titles/#post-10132688
The fix there covers all product archive types.
You are welcome to try it and submit feedback.
Forum: Plugins
In reply to: [Genesis Connect for WooCommerce] UpdateHi, @bamideleayo.
The plugin is tested and working with 4.9.4 and the latest WooCommerce, and the ‘tested with’ version on the plugin page will be updated to reflect this with the next version.
If there’s a particular issue you’re seeing, though, please let us know.
Forum: Plugins
In reply to: [Genesis Simple FAQ] All FAQs appear openOn 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.phpusing 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.