Closed (fixed)
Project:
Meez Integration
Version:
5.x-1.0
Component:
Documentation
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Jun 2008 at 21:33 UTC
Updated:
31 Jul 2008 at 05:21 UTC
Jump to comment: Most recent file
Comments
Comment #1
zcferres commentedAttached is my remade readme.txt that is tested and works. It's really dumbed down though as for some reason the drupal theme_image api doesnt support remote/absolute links.
Comment #2
gregglesHi, thanks for the changes. The file had "DOS" line endings so it appeared to be changing more than it really was. I've attached a diff so we can discuss the individual changes.
I think that using THEMENAME_user_meez( is the appropriate thing rather than phptemplate. But you are definitely right that theme_user_meez doesn't really explain to the new themer that they will need to use their themename. How about THEMENAME instead.
The theme('image') call provides many benefits beyond just adding the img tags around it. According to the docs it should work with Either the path of the image file (relative to base_path()) or a full URL.. So, if there are difficulties using a full URL then that's a bug in core.
I wanted to use the core class for "picture" since that has some styling applied to it already on most sites. I think most people, if they need a specific class, will understand how to change that. I did clean up the quotes in that area.
Your idea to use global $user seems incorrect, though. Global $user will always be the user looking at the page. For a user avatar, we want to display the avatar of the account being reviewed.
I cleaned up a few other comments in the README as well.
Can you review this new patch?
Comment #3
gregglesComment #4
gregglesAnd applied - http://drupal.org/cvs?commit=125913
Comment #5
zcferres commentedGreat, everything you said makes sense.
This issue with the drupal image function is a known bug in core:
http://drupal.org/node/119003
Thanks!
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.