Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I think that it can be a good idea to let the core Image module to be the handler that manages image styles on Statuses. Better because not depending in other modules. Is not an urgent issue but it can be a possibility to be this feature working in the 7.x.2 release of this module.
There are some problems with the Imagecache Profiles module that you can see here Not resizing in views.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | imageProfiles.jpg | 155.79 KB | eidoscom |
| #2 | imageProfiles2.jpg | 168.82 KB | eidoscom |
Comments
Comment #1
IceCreamYou CreditAttribution: IceCreamYou commentedIn order to do this, Statuses would just be copying code straight out of Imagecache Profiles anyway. It's not a big module and chances are if you want to display avatars at different sizes for Statuses you will want to display them at different sizes in other places too.
I'm pretty sure that the issue you linked to wouldn't affect the profile pictures that Statuses displays at all.
Comment #2
eidoscomAs you say, it doesn't affect the Statuses pictures displays, but is affecting the whole site user pictures. There are a problem with Imagecache profiles that it don't manages the pictures presets on views... So, we can assign a image preset to Statuses, but this preset is aplying to the whole site where user pictures are displaying.
In my case, I have a FB like profile (see attached image) where a user picture is displaying in a block at left side with a preset "X", and in the same page I have a statuses stream with user images with a preset "Y". Before installing the Imagecache Profiles, the block on the left side is showing the correct preset "X" assigned through views interface, but after installing the module I can't change the display of the picture through views anymore. If I change through Imagecache profiles, the preset affects the whole site displaying, including Statuses (see attached image 2).
I think it is a basic feature that can handle with the normal views interface using the core Image module on D7 that is not present in D6. Perhaps on D6 it was necessary to handle the user pictures styles through the Imagecache profiles module, but in D7 we are now depending on the "health" of other module to do a basic feature.
Moreover, and as a thought that I have as working with Statuses, the performance of the site is going down combining with a lot of other modules like UR, Heartbeat, Flag, OG, ... More modules means more tables on the DB, more top processing before showing the pages, etc.
I think that is not so urgent, or a must but I think that should be considered.
Comment #3
IceCreamYou CreditAttribution: IceCreamYou commentedHmm, well you should be able to set a different preset for the avatar that Statuses displays by editing the settings for the Sender Picture field in the view. I'm not sure I understand what the problem is, though I don't have a test site set up with Imagecache Profiles to test it out right now.
In terms of performance, obviously if you add lots of large modules your site will get slower. Statuses itself is fast. There's not much I can do about the performance of any other modules. All the modules you listed are providing features that are very different than what Statuses itself provides.
Comment #4
eidoscomOps! so It must be something wrong because changing the sender pic field in the view has no results... The sender pic on Statuses only responds to the general settings of "Account settings"
I supose that it will be a mistake in the Image Cache profiles module as I think Statuses is working well ... You know the code so you can determine if Statuses code are fine tuned ;) This point us at the beginning that Imagecache profiles is not working at all ;(
Comment #5
IceCreamYou CreditAttribution: IceCreamYou commentedIf it's not working, let's consider this a bug. There is probably something we can do on the Statuses side to avoid it. I have not personally had time to test or investigate this but from just looking at the Imagecache Profiles code it is not obvious what the problem might be.
Comment #6
eidoscomJust find that the problems mentioned here are caused with some incompatibility with Drupal for Facebook or Facebook connect modules. Uninstalling these modules stops the unpredictable results of managing The user pictures format through views...
It works just fine!
Comment #7
IceCreamYou CreditAttribution: IceCreamYou commentedGreat. Moving this back to feature request then.
Comment #8
IceCreamYou CreditAttribution: IceCreamYou commentedOne approach here is to make user picture classes extend views_handler_field_user_picture. That probably makes sense for the sender_pic and recipient_pic classes but not so much for the cross_pic class.
Another option is to mark this feature request "won't fix" since it is basically the entire reason for the existence of the Imagecache Profiles module (and practically the only thing it does). In this case we should probably document more clearly that Imagecache Profiles is required for this feature.
And a third option is to wait until #1021564: Allow to set image style when using theme('user_picture') lands (or work on that issue instead).
Thoughts?
Comment #9
rikose CreditAttribution: rikose commentedI achieved picture with an intended size by disabling user pictures. I rather added a new image field to user profiles(People>Account settings>Manage fields).
I changed the fields to be shown in views(statuses_stream). I removed sender's picture and adding two relationships(user: content authored and (nodes)content:author) I made the user image field to appear on the fields to be shown((author)field:image). This image_field works well with imagestyles on views. Simply choose which image style you want.
PS:Relationship adding order is important, first get user:content authored.