Liam Gladdy

No worries! Hope you got it sorted ??

Not sure why a WordPress upgrade will break this – but i’ll get it fixed – we should be validating that is an array anyway in any example output!

Hey there!

This is weird – i’d expect you to get some kind of output. If you have a staging location, you could try editing the plugin to add some debug output.

I want to add a debug option to the plugin in the coming weeks to try and help debug this kind of thing, so stay tuned for an update!

Hey,

This will be because you’re using another plugin that already declares OAuth libraries.

We’ll solve this issue shortly and get an update released to make this more compatible with other plugins!

Thanks,
Liam

Hey Johannes,

Sorry for the delay – we’ve been really busy and neglected the plugin a bit! But we’re going to make some changes soon and absolutely want to make this more inclusive.

If you’re interested, you can edit our code on github and submit a merge request if you want to help out! https://github.com/stormuk/storm-twitter

But stay tuned, and we’ll get this stuff sorted in the coming weeks ??

Thanks,
Liam

Had this issue too – well close to it, a different SSL error!

This ought to be included in an update really!

Hey, sorry for the delay.

I just released version 2 which adds support for custom parameters to twitter, so you can now call:

getTweets(20, $username, array(‘include_rts’=>true));

$username can be false if you want to use the one defined in the plugin settings!

As for the rate limit – yes, still prone to them, but you get 180 calls an hour, so the caching should handle it for most people ??

Hey!

This is now available!

You can pass in twitter handle as the second parameter of getTweets() as of version 2.0 ??

Hey!

This is now available! Just set the cache time to 0, or 1 in the configuration options for version 2.0.3 of the plugin ??