Closed (cannot reproduce)
Project:
Janrain Social Login
Version:
6.x-2.3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Sep 2012 at 15:56 UTC
Updated:
16 Sep 2014 at 22:40 UTC
Jump to comment: Most recent
Comments
Comment #1
Jeremy-Bradbury commentedWe are unable to duplicate this. Perhaps it's caching? I'm gonna close this if you don't have any more information.
Comment #2
Jeremy-Bradbury commentedComment #3
iamcarrico commentedFrom what I remember (the direct project using this is long since over), the issue was that the buttons made pulled a CSS file from Janrain, but the image files it referenced did not exist on the server. I will try and find time to test this later with the current work.
On a similar note, this is touched upon in the patch for #1789330: Add in ability to add share button programmatically to individual pieces of content. . As is #1789232: Update theming of sign-on to use renderable arrays, to better enhance themability. and #1789218: Add in ability to change the text / icons for the social sharing widget..
Comment #4
westis commentedI also can't see these icons. Was this evern fixed?
Comment #5
funana commentedSame here. Exactly like described in https://drupal.org/node/1789218 .
Comment #6
Anonymous (not verified) commentedI have also encountered this with 6.x-2.3. The widget is built in "site/all/modules/rpx/rpx_widgets.module", and relies on sprite images stored in "site/all/modules/rpx/images". A likely cause may be the way the CSS is handled per browser. I know that Chrome treats the position attribute differently than IE & Firefox...
Comment #7
Tom Ash commentedI wonder if this might be related to the issue Icons/images for providers (FB, etc.) sometimes don't show in 'Sign in' box? Does it suggest any solutions to that issue?
Comment #8
byron-janrain commentedWe cannot reproduce this error at the url mentioned (effectivealtruismhub.com/user) on any platform with any browser, moreover Drupal 6 hasn't been supported in a year or more.
We'll continue to investigate in the 7.x branch in issue #2339569.