Hey Keiron,

Okay so in order to have different caches for different sites you need to differentiate the caches.

If it was me, I'd do something like this:

1) Change the method definition for GetTweets to this:

public static IEnumerable<TwitterStatusMessage> GetTweets(string consumerKey, string consumerSecret, string twitterUserName, int cacheTimeInMinutes, string cacheIdentifier)

Then instead of cache["tweets"] and cache.Set("tweets", ... do cache["tweets_" + cacheIdentifier] and cache.Set("tweets_" + cacheIdentifier, ...

This would turn the caches into unique entries assuming that cacheIdentifier is different.

So, then when you are calling GetTweets pass in something like Model.Site().GetKey().ToString("n") to pass in the root node Guid without the -'s

Does that make sense?

Nik

Thanks Nik, that makes sense I'll give it a try.

On another note, I've been looking into the best way to catch errors and validate things like the Twitter username.

Most of the stuff I've found on Our relates to Skybruds Umbraco package https://our.umbraco.com/packages/website-utilities/skybrudsocial-for-umbraco-7/

e.g. https://our.umbraco.com/packages/website-utilities/skybrudsocial-for-umbraco-7/general-discussion/74840-setting-up-a-twitter-feed

@using Skybrud.Social.Twitter
@using Skybrud.Social.Twitter.Objects
@using Skybrud.Social.Umbraco.Twitter.PropertyEditors.OAuth
@inherits Umbraco.Web.Mvc.UmbracoTemplatePage
@{
    Layout = "Master.cshtml";
}
@{

// Get the OAuth information stored in the property
TwitterOAuthData twitter = Model.Content.GetPropertyValue("twitterAuth") as TwitterOAuthData;


// Check whether the OAuth data is valid
if (twitter != null && twitter.IsValid) {

At the moment I've just got the latest SkyBrud.Social NuGet installed (not the Umbraco one) or am I better off using the Umbraco version to help with things like error catching?

Looking at the main SkyBrud API I can't find anything obvious for Twitter username validation / error catching.

Got this working, thanks for your help Nik!

Now fighting with catching authentication errors with caching enabled, it's almost there :)