EjiOsigwe

Thread inactive for over a week. Assumed resolved.

At the moment it isn’t possible. But I’ll look into adding into the next update, if possible.

Thanks,
Eji

It isn’t at the moment. That said, it is a good idea (not sure why I hadn’t thought of it in the first place).

I’ll definitely have a look at including such functionality in the next update.

Thanks

Really appreciate the feedback, guys.

Apologies for the delay but I’ve now released an update with a fix for the bug. I took your approach Braunson.

Again, thanks all!

Cheers Braunson,

I’ve taken a look and I can see the issue indeed. I’ll be applying an update soon.

Thanks!

Hey,

I’ve had a check and according to this Twitter API page, error code 89 means:

The access token used in the request is incorrect or has expired. Used in API v1.1

Essentially, you’ll need to go into the Twitter account that holds the Consumer/OAuth tokens that your feed runs on and either grab the new ones should they be different to the plugin’s or generate new ones and drop them in to the plugin.

Bear in mind that if the Twitter account OAuth tokens are used by any other apps they may come across similar trouble when you generate new ones, and you’ll need to update them.

Be sure to let us know if it works.

Thanks!

Hey

I’ve released an update that should resolve this issue. Update and be let me know if it has worked.

Which version of PHP are you using?

That line calls FILTER_SANITIZE_FULL_SPECIAL_CHARS, which is supported from PHP versions 5.3.3 and up.

I’ve conducted a few tests and I’m not getting that issue.

Potentially, it could be to do with the length of the tweet. If it’s quite near to the 140 mark Twitter will return it somewhat truncated and drop in the ellipses. I believe this may be because sometime other additional information comes with the tweet that means it can’t fit the entire tweet text in so it truncates it.

This is only a theory though, so if you notice otherwise or have any other info to send my way be sure to do so and I’ll look into as soon as I’m free.

You’ll need to customise the HTML of tweets, which is possible by building your own template tag.

If you’re familiar with PHP and have access to your theme files it shouldn’t be too difficult. Take a look in the assets folder of the plugin for the sample files and read through them.

If you’re having trouble with that (be sure to back up your files before you tinker) come back and let me know and I’ll see if I can help further.

I’ll have to take a look into this. There’s a part in the tweet building process that checks for links and manipulates them, so it may be that I need to check that the process can handle bit.ly links (and other links of that variety, in fact).

Thanks for bringing it to my attention! I’ll try and work in a fix before the next update.

Thanks for this, and apologies for the late reply.

I did notice this a short while back and found that the smilies weren’t being encoded when cached which buckled the caching procedure. Thus, any load of the cache version would show correctly up to the point of the first smiley.

To fix the issue the output is now encoded appropriately directly before caching, and then decoded as and when called from the cache.

I’m aiming to roll out the update with this fix in the next day or two.

Your input was much appreciated!
Thanks

Hi and thanks for using the plugin.

That’s actually a bug in the code that seems to mix up the search term and the username. I’m currently working on an update that should fix this issue and a few others so keep an eye our for it, I’m hoping to roll it out in the next few days.

Thanks!

Unfortunately I don’t have an immediate fix for it at the moment. But having looked into it I may be able to work a fix into the next update.

Sorry I couldn’t be of further help.

Apologies but I’ve been unable to replicate your issue, making it difficult to pinpoint a fix. I have come across this once in the past, though, and it turned out to be content within the tweet itself interfering with the HTML.

That said, I’ve had another glimpse of your site and it looks like the bug has been resolved. Did you find a fix? If so would you mind sharing it?

Thanks