Plugin Contributor
Nick C
(@modernnerd)
Hi, @melmcdonald2!
The most common cause of this is a caching plugin or caching service (such as CloudFlare) holding onto an old copy of the plugin’s stylesheet. If you update the plugin and clear all caching plugins and other caches, it will often fix the issue. If you don’t think you’re using caching plugins or services, it is often worth asking your web host too.
If that doesn’t solve things for you, the next most common cause is modifications applied to your theme that need to be rewritten or removed to be compatible with the updated version of the plugin. If you haven’t made changes yourself, you may need to contact your developer or the theme’s developer to check that your theme is compatible with the new version of the plugin. StudioPress blogged about the changes here, so any developers who have customised the icon style should be aware of the issue.
If you’re able to link to a staging site where the issue is visible, I’d be happy to take a look to see what the cause is likely to be in your case.
-
This reply was modified 9 years, 4 months ago by Nick C.
-
This reply was modified 9 years, 4 months ago by Nick C.
Plugin Contributor
Nick C
(@modernnerd)
Hi, @apfotos
Thanks for your report! Do you have a page or staging site you can link to where this issue is visible, please?
Plugin Contributor
Nick C
(@modernnerd)
Hi, @xdynx. The most likely cause of this is a caching issue or CSS conflict. I replied to your support request at https://wordpress.org/support/topic/is-not-possible-to-change-color-of-the-icon-is-black/. If we can help further with this, please let us know there.
Plugin Contributor
Nick C
(@modernnerd)
Hi @xdynx
Do you still require help with this? If so, please could you share a link to your site, and a screenshot of your widget settings? Thanks!
Plugin Support
Nick C
(@modernnerd)
Hi, @thenerdynurse!
From what you describe, there are at least a couple of possibilities:
- The hooks missing from the admin area have been removed from the database, but your edits still appear on your pages due to page caching.
- The hooks are still present in your site database but are not appearing in the admin area due to a syntax error in one of the hooks, or a plugin conflict preventing the admin page from loading fully.
To solve this, you could first find out if the hooks are still present in your database. You’d need to look at the contents of the ‘simplehooks-settings’ option_name in the wp_options table using phpMyAdmin or a similar tool:
You should check that content to find code you recognise.
If you don’t find any HTML or PHP you recognise and the hooks are missing from your database, you can either restore them from a backup or recreate them from scratch on the Genesis → Simple Hooks page.
If the hooks are still present in your database, you could:
- Check for PHP errors in your server logs.
- Disable other plugins to see if the hooks load correctly in your admin area.
- Take a full site backup first, and then attempt to add the hooks again to the Genesis → Simple Hooks page one at a time, using the saved
simplehooks-settings contents from your database backup as a guide. If the hooks disappear after editing one of them, there may be a syntax error in the code you just added.
-
This reply was modified 9 years, 4 months ago by Nick C.
-
This reply was modified 9 years, 4 months ago by Nick C.
Plugin Support
Nick C
(@modernnerd)
Hi, @spooky1!
Could you share a link to a page where this issue is visible, please?
Plugin Support
Nick C
(@modernnerd)
Hi, @talontedigits
As a starting point, you could:
If you need further help setting up the theme after this, it’s worth posting in the theme developer’s support forum here: https://support.prettydarncute.com/start-here/
Plugin Contributor
Nick C
(@modernnerd)
Thanks for the update, @theresathomson – sounds like a caching issue. Glad it is working for you now.
~~~
For anyone else with this issue, you can try:
- Clearing all browser and server caches. This includes WordPress caching plugins, caching features that your web host provides, and third-party caching services such as CloudFlare
- Looking for custom styles in your theme’s stylesheet (they will likely include the
.simple-social-icons class name). These may need to be adjusted to work with the new version of the plugin.
- Looking for custom icon filters in your theme’s PHP files (most likely in
functions.php). These may also need to be adjusted to work with the new version of the plugin. The snippets for reordering icons and adding additional icons may help.
If you need help adapting any icon styles or filters you’ve added previously to work with the new version of Simple Social Icons, please feel free to start a new topic. You’ll need to include a link to your site, together with the filters or CSS code you had in place for the old version of the plugin.
Plugin Contributor
Nick C
(@modernnerd)
@theresathomson I see a tiny icon in your footer widgets:
You can control the size of this in the widget settings by changing the ‘icon size’ value.
Plugin Contributor
Nick C
(@modernnerd)
@kdunham You can still reorder and add icons, as mentioned in the 2.0 update post that Brian linked to.
The plugin’s wiki here features some code to help with this:
For those still experiencing issues with icons appearing as squares, the most common reasons are customisations applied under 1.0.13 that have not been rewritten in the 2.0 style, or caching. If you’ve ruled those things out please feel free to start your own post – am happy to take a look on a site-by-site basis.
Plugin Contributor
Nick C
(@modernnerd)
Thanks for these reports, and I’m sorry for my late reply – notification gremlins in the forums here…
As @chris_c mentioned, it’s permitted to use titles in SVGs; it’s even recommended as a best practice in SVG accessibility guidelines: https://css-tricks.com/accessible-svgs/#article-header-id-9.
The W3 validator does not complain about additional titles in SVGs, but if other validators or SEO tools are throwing errors, it’s worth reporting them as potential bugs to the validator maintainers.
The xmlns attribute only needs to be added for files served with the SVG or XML mime types, and StudioPress already includes it for the symbol-defs.svg file itself: https://raw.githubusercontent.com/copyblogger/simple-social-icons/7adae99b7b4b5e18fe4893bd889c35ef2ddd168d/symbol-defs.svg
SVG content served inline with the rest of the HTML using the text/html mime type does not require the xmlns attribute: http://stackoverflow.com/questions/18467982/are-svg-parameters-such-as-xmlns-and-version-needed#18468348
You’re welcome! Good luck with the domain migration, and I’m sure you’ll rebuild those counts soon enough. 🙂
-
This reply was modified 9 years, 6 months ago by Nick C.
Hi, @xonet.
Thanks for your report. The StudioPress development team is aware of an issue that can affect the Customizer if Genesis Featured Post widgets are used, and hope to patch this in a future update.
For now, you could edit the plugin as follows:
Change line 138 of the file at wp-content/plugins/genesis-simple-share/lib/front-end.php from this:
if( $this->is_archive() ) {
wp_enqueue_script( 'genesis-simple-share-waypoint-js' );
}
To this:
if( $this->is_archive() || is_customize_preview() ) {
wp_enqueue_script( 'genesis-simple-share-waypoint-js' );
}
After saving your change and refreshing the Customizer, you should find this allows you to continue editing widget content there.
-
This reply was modified 9 years, 6 months ago by Nick C.
Unfortunately it’s not possible to transfer likes between domains – social networks don’t offer tools to do this yet.
You can 301 redirect your old URL to your new one so that old links point to the correct posts, but the social counts themselves are linked to your domain and reset once you change it.
Hi, @mrlennyman.
Your counts are stored with each social network, rather than with your plugins. Genesis Simple Share retrieves the count from each network directly. Counts should only reset to zero if you change your domain, switch to or from HTTPS, or alter your permalinks.
If that doesn’t help to explain what’s happened, you’re welcome to link to a post where you now see a zero count – I’d be happy to take a look for you.
