ssbl no button images showing?

Hi Julian,

The image src’s should be base-encoded images, so just strings.

Could you provide a link to an example please?

Thanks,

David

There is no icon on the site. Empty fields.
<img src=”” title=”Facebook” class=”ssbl ssbl-img” alt=”Share on Facebook”>

i use ssbl on domkonzerte-arlesheim.ch. works fine on pages but not with posts. only the first post displays the images when embedding shortcode [ssbl]. all other posts don’t show the images – what do i make wrong?

I’m also having the same issue. The site is currently not live right now, but basically when I look at “Inspect Element” in Chrome, I get this HTML code for where the images should be:

<img src title="Facebook" class="ssbl ssbl-img" alt="Share on Facebook">

So only the alt text is showing on my pages and posts.

I’m currently using WordPress 4.3.1.

Hello

I have the same issue. I have even tried updating to the latest wordpress but did not help. The images just show as alt text links and when I look to inspect element, the img src=””. How do I fix this please?

… and I also have the same issue. Only on some posts, not all of them.

Hi,

I started having the same problem recently and solution that worked for me is to edit a single line of code in simple-share-buttons-light/system/controllers/ssbl_buttons.php (line 140):

Instead of include_once:

$this->images = include_once SSBL_ROOT.'/buttons/'.$settings['image_set'].'.php';

You want to just call include:

$this->images = include SSBL_ROOT.'/buttons/'.$settings['image_set'].'.php';

The problem with include_once is that it returns true on any subsequent call instead of what is being returned from the included file, so if SSBL_Buttons constructor is called multiple times within a single request (for whatever reason), the $images property is being assigned a boolean value instead of array of image data…

Greetings,
?eslav

Can confirm the above fix working for me as well.
Thanks for the fix ?eslav!

If that works, I hope it gets included in a plugin update.
Thanks for figuring it out ??

Thank you ?eslav. That worked perfectly. I do hope that it gets included in the plugin update also.

I concur. Is coding error.
An update from author using “chesio’s” fix is required to fix this bug.