Forums
(@thomashansen)
11 years, 10 months ago
Same error here!
It seems to be related to some change on Facebook API, does anybody have a patch to solve it?