EjiOsigwe

Hi Mariette,

The plugin doesn’t handle dynamic content using JavaScript which means that caching plugins are, unfortunately, going to cache it even if you’ve set DevBuddy Twitter Feed to not cache.

If you’re familiar with JavaScript and the WordPress code infrastructure the best workaround that comes to mind would be to use AJAX to make a call to the template tag. Otherwise, there are no options to prevent the feed from being cached by caching plugins.

Apologies if this makes the feed incompatible with your setup. It’s definitely something I’ll fix in the next update.

Thanks,
Eji

It does have to do with the retrieve_feed_data() method. When you opt to exclude tweets Twitter first gets the requested number of tweets and then removes any replies and retweets. Because of this users may find that the number of tweets retrieved doesn’t stack up to what’s expected.

In a best effort attempt to honour the user’s tweet count wish, if the number retrieved is less than what they asked for the plugin retrieves more. Three was mostly arbitrary, admittedly.

It may very well be reworked. What springs to mind now is to simply get more than the requested number of tweets and hope that if the number returned is trimmed down it’s still closer, if not more than the requested number.

I must apologise guys.

I do occasionally look through the support tickets but I rarely have time to look into things.

The plugin is still in development, though, and I’ve got it booked in to release another update around March, taking into account the various issues that have been brought up in support as well as getting one or two shiny new features in.

Again, apologies for the lack of support and, also, thanks for using the plugin.

Hey,

The option to load everything over HTTPS exists from version 3.2.0 and up of the plugin.

To turn HTTPS loading on add https="yes" to your shortcode, or add 'https' => 'yes' to the options array of your template tag. The setting can also be turned set via the plugin’s settings page.

Thanks

It’s difficult to say without being able to see what you’re inputting. But I wouldn’t advise posting such code here because of the sensitive info.

Have you tried un-installing the plugin and re-installing it via WordPress. Un-installing via WordPress removes the settings from the database, so when re-installing you know you won’t be using old data.

See if that works.

Otherwise, make sure you’re not mixing up the Consumer Key with Consumer Secret, and OAuth Access Token with OAuth Secret.

Eji

Hello and thanks for using the plugin!

Just having a look and it appears that all that would be necessary is to replace the “normal” text in profile image URL with “bigger”, or remove it altogether to get the image in its original size.

More info here: https://dev.twitter.com/overview/general/user-profile-images-and-banners

A short-term fix would be to perform a string replace on the image URL on the fly. In the longer term I’ll look at implementing some native functionality to accommodate this and roll out an update.

Thanks for bringing it to my attention.
Eji

That error code does simply mean that the authentication credentials you’ve provided aren’t valid.

Have you made sure you’re entering the right codes to the right options?

Are you inputting the auth data in the settings page or directly to the shorcode?

Thanks

The shortcode simply calls the template tag so it should work as expected.

(Sorry for the late reply.)

Hey,

I would point you in the direction of this thread.

Basically, it’s just a couple of ways for you to replace the HTML in a specific part of a tweet.

I’m hoping to internationalise the plugin and release it as an update in the next couple of weeks. It’s long overdue.

Let us know if that works out for you.

Thanks,
Eji

To enable images in the feed, then, the full code should be:
[db_twitter_feed show_images="yes"]

Bear in mind that in some cases on the Twitter website, Twitter will read certain links (I think imgur or bit.ly links or something similar) and convert them to images but then not send the image information to feeds. No idea why, though.

As for the image sizes I’ve left that to the person using the plugin to customise. The default behaviour is to simply render the images as received and let the current website control how they display. If you have access to the CSS of the site and know how to code such you can change the image to be displayed however you please.

Would you be able to post the entire shortcode or template tag for me to see?

Hey

I’ve just released an update which sees the plugin support loading embedded images so update and check it out. You may need to spply some new styling to accommodate the images.

Thanks,
Eji

It should be fine. Your current settings will remain and the new features will be added on top.

Thanks,
Eji

Hey Tom,

I can think of two ways you could approach this, both require creating your own template tag:

1: This is the quickest. You can take the line you quoted and replace $the_feed->html->tweet_intents() part with the HTML you wish have instead.

2: This is the most thorough. $the_feed->html is an instance of the DB_Twitter_HTML class. In your theme, you can create a class to overwrite this i.e. My_Twitter_HTML extends DB_Twitter_HTML and within this class add your own version of the tweet_intents() function.

Once you’ve done this, assign your newly created class to the feed object by adding the following directly under $the_feed = new DB_Twitter_Feed( $feed_config );:

$url_data = array(
	'tw'     => $the_feed->tw,
	'search' => $the_feed->search,
	'intent' => $the_feed->intent
);

$the_feed->html = new My_Twitter_HTML( $the_feed->options, $url_data );

In both cases make sure to update any existing instances of the template tag to your new one.

To explain the second option you’re extending the original HTML class and overriding only the intents method with your own HTML (feel free to customise other HTML parts too). Then, in the template tag, you’re overwriting the original instance of the HTML object with your own instance which will have the lovely new HTML to drafted.

None of this has been tested, it’s all impromptu, so you may need to play around with it.

Let us know if it works,
Eji

Closing thread.