Hi,

I think it would be great if we had the possibility to customize Like Box using a css file. I am not able to find how to do it now. At configuracion page (../admin/settings/fb/social/likebox ) appears :

"Connections:
Note: To provide you with better performance, we cache your stylesheet. If you update your stylesheet, you should use a cachebreaker in the URL to the stylesheet, typically by appending a version number to the .CSS file extension, as in http://www.example.com/my.css?2 "

but I can't specify the css file. There is no field.

It would be great, to have the same field that exists at Comments Box (../admin/settings/fb/social/comments):

The URL to your own stylesheet.: "......"

Thanks!

Comments

ferdi’s picture

I dont think facebook allows users to provide their own css file for the like box (xhttp://developers.facebook.com/docs/reference/plugins/like-box)
What you describe above is wrong description of "connections" textfield which is fixed now (http://drupal.org/cvs?commit=397634)
thanks!

ramonphp’s picture

Ok

(what a pity!)

Thanks for your feedback.

ferdi’s picture

Status: Active » Closed (fixed)
t0b1’s picture

Facebook does not allow custom styles to the likebox any more (in earlier fan-box widget it was allowed).

But anyway: the mentioned field description text is wrong, as the field controls the number of displayed contacts, but is discribed as a stylesheet url:

 $form['widget_setings']['fb_social_likebox_connections'] = array(
   '#type' => 'textfield',
   '#title' => t('Connections'),
   '#description' => t('Note: To provide you with better performance, we cache your stylesheet. If you update your stylesheet, you should use a cachebreaker in the URL to the stylesheet, typically by appending a version number to the .CSS file extension, as in http://www.example.com/my.css?2'),
   '#default_value' => variable_get('fb_social_likebox_connections', 10),
 );

Should get fixed in next releases ;)

t0b1’s picture

Category: feature » bug

Category set to bug report

ferdi’s picture

this is fixed, I think. See #1
Thanks!