When using imagecache profiles for display of profile image this warrning is always present

warning: Attempt to assign property of non-object in /srv/www/pribadaca/public_html/sites/all/modules/facebook_status/includes/views/handlers/facebook_status_views_handler_field_cross_pic.inc on line 80.

also in comments box, there are no images for user as some strange path is written and there is no image from imagecache, maybe this second is a bug in imagecache profile module.

<img class="imagecache imagecache-1" title="setup's picture" alt="setup's picture" src="sites/default/files/imagecache/1/pictures/picture-1.jpg">

Comments

Marko B’s picture

Marko B commented
Priority: Normal » Minor

Forget the last part of the post, no images were in comments as i didnt select it in
"Imagecache preset for user pictures in comments: " of Fbss module, but i still get this same warning message. I am using latest imagecache profiled dev module, maybe there is some incompatibilities.

icecreamyou’s picture

icecreamyou commented
Status: Active » Postponed (maintainer needs more info)

Well you'd only get that error if the current context failed to load a recipient, and that should only happen if you force the node, group, or taxonomy context to be active where it shouldn't be. Try using the FBSS dev though, this might already be fixed.

Marko B’s picture

Marko B commented
Version: 6.x-3.0 » 6.x-3.x-dev

I am in fact using DEV version, i just checked. Strange, this started to happen when i installed imagecache profiles and also if you check that line 80 is in fact calling imagecache_preset. I'll check contexts.

icecreamyou’s picture

icecreamyou commented

Was this ever resolved?

icecreamyou’s picture

icecreamyou commented
Status: Postponed (maintainer needs more info) » Fixed

Committed fix to dev.

This warning could have appeared if you had the General context active, which is probably not the configuration you want, but regardless it should be fixed now.

Marko B’s picture

Marko B commented

It stopped showing, but i really dont know why. :(

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.