Simple Share

@nguyenvanvinh1131992 Were you able to figure this out or do you still need assistance?

@venlatala Yes, that shouldn’t be an issue!

@404m, I have added this to the list of issues to address in our upcoming 8.2.4 release. Thank you for the report!

Closing as there doesn’t seem to be any further support needed.

@koehmstedt

I apologize for the wait!

I’ve had difficulty reproducing this issue so that I can fix it. If you could provide me with the following information, it would help me release a fix for this much more quickly:

– Your theme name and version.
– Your settings within the plugin (Classic or Advanced, anything else you can provide)
– Any other detail you feel is pertinent

Hi @chcw,

Yes — our plugin utilizes the Facebook SDK in order to facilitate some specific Facebook functionality where it’s needed.

However, if you determine it’s not needed (Facebook Share button probably doesn’t need it, for example), you can stop the sdk from loading altogether for simple Facebook Share by going into wp-admin -> Simple Share Buttons -> [Classic or Modern Share Buttons] -> Advanced -> Ignore FB SDK.

This would require testing on your site, of course, but it’s an available option.

Hope this helps you in your quest!

– Scott

@qbey This should be fixed in version 8.2.1 released last week.

@sarahm1978 Thanks for helping us improve our plugin. Can you send us a link to your site so we can identify the issue and get an update out to fix this behavior?

Hey sorry @aperunner can you send us a link to the page in question? Would love to help you out with your styling conflict.

Apologies for the delay @chcw. You can try dns-prefetch, preconnect, prefetch, and prerender to optimize the loading of these assets. Let me know if that works for you.

@jaroslawistok The GDPR database entry will only show up when you enable it. If it is already enabled then you should find the database entry in the “options” table in your site’s database.

If you want to find where in the code this database entry is added, it is in the “class-admin-bits.php” file on line 295 in the “updateGDPR” function.

Let me know if this helps!

• This reply was modified 3 years, 3 months ago by Simple Share.

@chcw Ah, ok got it. Go ahead and preload without it. That is just a cache busting param that is hardcoded. The preload should suffice without it. Go ahead and give that a shot and let me know if you have any issues.

Worst case scenario you can target the url WITH the param in it since we will not be changing that query string addition in the future anyways.

have you tried:

<link rel=”preload” href=”/blogs/wp-content/plugins/simple-share-buttons-adder/fonts/ssbp.eot” as=”font” crossorigin=”anonymous” />

<link rel=”preload” href=”/blogs/wp-content/plugins/simple-share-buttons-adder/fonts/ssbp.woff” as=”font” crossorigin=”anonymous” />

<link rel=”preload” href=”/blogs/wp-content/plugins/simple-share-buttons-adder/fonts/ssbp.ttf” as=”font” crossorigin=”anonymous” />

@chcw Sorry about the lack of communication! What is the problem you’re having exactly? I not sure I saw a question in your request.

Sorry for any confusion. The iframe is separate from the new GDPR tool and is used to check if the user has given or withdrawn consent from data collection under the general data protection regulation to ensure we respect the users privacy selections and therefore is not removable. Thank you for reaching out with your question.