Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter qubed

    (@qubed)

    Appears this was a permissions issue. Resolved.

    qubed, I think I’m experiencing the same issue. Could you tell me how you managed to solve it? Thanks!

    This error is pure dumbness. Don’t know what they did in the latest version but this is how it acts. The plugin thinks that the $tweet is actually a STD class, while it’s not.

    Anyway, the solution is even dumber than the actual bug (tested in many environments and it works):

    Open the file where you make the $tweet call and resave it. That’s it! It will work out of the blue.

    Plugin Author Storm Consultancy

    (@stormuk)

    Just about to release a fix to fix this properly.

    If you don’t get a cached load, the upstream OAuth library we were using started returning objects, rather than arrays!

    Sorry guys!

    Plugin Author Storm Consultancy

    (@stormuk)

    Version 2.2.1 fixes this issue.

    This wasn’t an issue when cached, as the json stored in the cache was decoded into arrays anyway, but when not cached, it was an object rather than an array, leading to that error.

    Thanks a lot for the update guys! It was the craziest error ever :))

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Breaks homepage’ is closed to new replies.