When changing an avatar using JomSocial, the postback processing causes onAfterStoreUser() to be triggered in plugins/user/k2.php. On (or around) lines 95/96, there is a check for $file in K2's user plugin code.
K2 appears to be making the presumption that the data in $_POST is its data. It is not, it is JomSocial's postback. While it's fine for K2 to register for the onAfterStoreUser(), it seems wrong that it presumes that it might be the only component out there passing data back in $_POST for this event.
This causes K2's plugin to emit an error ("could not upload your image.") when no such error is present. The error is because there is no index for on $file in this case. K2 presumes there is, again, because it presumes that the data in $_POST is its own.
This is breaking JomSocial - bad form, K2!
Would a developer please comment on this and acknowledge the bug?
K2 appears to be making the presumption that the data in $_POST is its data. It is not, it is JomSocial's postback. While it's fine for K2 to register for the onAfterStoreUser(), it seems wrong that it presumes that it might be the only component out there passing data back in $_POST for this event.
This causes K2's plugin to emit an error ("could not upload your image.") when no such error is present. The error is because there is no index for on $file in this case. K2 presumes there is, again, because it presumes that the data in $_POST is its own.
This is breaking JomSocial - bad form, K2!
Would a developer please comment on this and acknowledge the bug?