Storm Consultancy

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.

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!

Hi Zack,

Awesome, glad I could help!

We have E_ALL on in dev mode to catch little things like this. It was appearing on every admin page that I looked at, not sure but it was probably on the front end as well. Because it wrote the warning to the browser, it breaks anything that needs to do a redirect as output has already been written.

Any idea when you’ll be putting out an updated version?

Cheers,
Adam

Hi,

It’s a completely custom theme on 3.7.1. We’re not using any translations.

I can reliably get the error to appear/disappear by adding/removing your plugin.

Looking at your code I see this on line 13:

load_plugin_textdomain($formilla_domain, 'wp-content/plugins/formilla-live-chat');

Lots of other plugins I have installed are calling it with 3 parameters like the codex page

load_plugin_textdomain( 'my-plugin', false, dirname( plugin_basename( __FILE__ ) ) );

I can get to the settings page fine – my client hasn’t actually given me account details to test with, so I’m not sure if the rest of the plugin works.

Cheers,
Adam

We’re really sorry about that! We spotted this bug last night and fixed it as soon as we did too – Just a tiny bug with the documentation that stopped wordpress being able to install it!

Please let us know if you have any other problems!