Things like this aren't a quick fix. You need to trace the code back to what called it and see what the intention was, and whether the data being passed is wrong because of bad data in the database, or something wrong with the form data being output to the screen and then submitted back to the script when the page is submitted, or whether there's a bug in the code that's doing the calling of the function that's discovering the bad data, etc.
VERY SELDOM is it appropriate to just "comment out" a line that's reporting a problem. That's a very bad approach to troubleshooting.
This is ONLY a guess based on a hunch, as I've not studied the addon in extensive detail: Maybe change this line:
Code:
if(!is_array($attributes)) return false;//is qty by attrib, but no attrib specified, so "no".
to this:
Code:
if(!is_array($attributes) || sizeof($attributes) == 0) return false;//is qty by attrib, but no attrib specified, so "no".
That may get rid of the error condition, but I've no idea if that's actually going to accomplish the correct end result for the case you're encountering. USE AT OWN RISK.