Found the problem. Apparently this hack didn't declare any instance of WfsLists, so I did it for it.

In the avatars/main.php file, go to line 58 where there's a call to WfsLists::getarray(). Insert before this line:

$wfslistsx = new WfsLists;

Then change the call to getarray() as such:

$wfslistsx->getarray( XOOPS_ROOT_PATH . "/uploads/cache");

This fixed it for me.

-Rosencrantz

I found that the code in modules/wfsection/class/wfslists.php calls the getarray function of the object-type WfsLists, of which no instance had been created. So I added the line

$wfslistsx=new WfsLists;

and modified the call to getarray to read

$wfslistsx->getarray( XOOPS_ROOTR_PATH . "/uploads/cache");

Was this hack written for a different version of XOOPS perhaps? I'm using the latest (2.0.7.3)

That fixed that problem, but left me with another problem I had to work around. The module doesn't pull the information in user settings about limits when uploading avatars. It thinks the "avatar_maxsize" "avatar_width" and "avatar_height" values in $xoopsConfigUser are all null. Perhaps whatever function populates $xoopsConfigUser is not being called properly?

I was able to work around this by hardcoding my own limits to use but this is less than ideal. Any input?

-Rosencrantz

Does this hack for multiple avatars works with the new XOOPS 2.0.9.3 ?

not working for me