Hello n00bster,

Sorry for late reply to this,
I have checked your site and already put our CSS hack in this file: joomlafolder/templates/silverfuchs/styles/foxality/css/layout.css, you can always find the code at the bottom of the source code as below:

#eblog-wrapper .socialbutton-vertical {

vertical-align: inherit;

}



#eblog-wrapper .social-button-large.pinterest {

padding: 0px 0px !important;

}



#socialbutton.alignleft.width-full .social-button {

width: inherit;

}

Remember clear your browser cache and see the social button is it display nicely already? Please have a check

Hi!

I have the same problem here. I am using the standard protostar template from Joomla 3.2
The buttons are placed in line, the space between is good apart from the printerest button that is to high.
I am using inside easyblog the elegancewhite (?) theme.

Best regards,
Volker

Hello Volker,

Could you mind provide us with a temporary access to your Joomla backend (as admin) and an FTP access so we can check that issue and see where the problem is coming from? Please advise.

I recognized it here: http://www.glienke.de/artikel/easyblog-kat-de/entry/txt-myreport
I enter the site info and the account details in this article.

Hello Volder,

Sorry for the late reply as it's the weekends. I have added a fix for in the the template.css file of your template Please check it out. Hope this helps.

Thanks!

Hello Adelene!

This works fine with the big buttons, switching to small buttons creates a new problem. The twitter bubble is cut off at the right side. This happens in the category list (all blogs of a category) and in every blog itself. Even putting them under the blog shows this behaviour. Perhabs you need to fix the integration of the buttons into the standard protostar template in the next version. :-)

Regards, Volker

Hello Volker,

Sorry for late reply to this,
I have applied some CSS hack in your file, so the twitter social button work fine now before your clear your browser cache and Joomla cache. ( http://screencast.com/t/Yn4ttVuuCXzf )
Thanks for you suggestion, we will add this fixes in next release version.