Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Just testing 'Shortest Route'-Block! The names are not shown at the bottom of the pictures (look at the attachment).
Hope anybody can tell me whats wrong here!
Also it could be good to make it possible that the avatar-pictures are resizeable with imagecache presets so that the shortest-route-block pictures get their own size.
For now i have to go to admin/user/settings and set the global size very small, like 80x80 to fit the shortest route to the theme!
greetings, t!
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | profile2.gif | 6.75 KB | telefunken |
| profile.gif | 5.66 KB | telefunken |
Comments
Comment #1
telefunken commentedComment #2
crizhi,
this should be a css issue. What browser did you use? Does the shortest route css file get loaded?
But you can change also the html output by theming theme_block_output() and do your complete own block layout.
If you want to use imagecache for userpics take al look at http://www.lullabot.com/articles/imagecache_example_user_profile_pictures. But for the shortest route block you would have to adopt the code a little bit, as the shortest route module isn't using theme_user_picture().
@nodestroy
What about using theme_user_picture() in shortest route module? Is there a disadvantage?
Comment #3
telefunken commentedthanks criz for your support! using firefox & opera. both the same result!
for testing i changed style.css to 10px (>>so yes it is loaded):
.buddy_api_shortestroute_image{
height: 10px;
width: 10px;
text-align: center;
}
and get the following result.
think something is wrong with the settings in style.css!
i'm wondering if i'am the only one
greetz, t!
Comment #4
telefunken commentedhmmm....the settings befor have been height and weight =100px by default.
strange
Comment #5
simon georges commentedThis version of BuddyList2 is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.