Ran into a few permissions problems with this over the weekend when I came to deploying it with ASP.NET
FlickrNet. It is not incredibly web friendly – you need to override where it looks to store its cache. In your root web.config, you need to add the following section to the configSections part, or if there is no configSection piece, add it to the top of the web.config, right after the configuration section starts:
<configSections>
<section name=”flickrNet” type=”FlickrNet.FlickrConfigurationManager,FlickrNet” />
</configSections>
And then add this line within the configuration section:
<flickrNet cacheLocation=”e:\domains\qgyen.net\temp” />
There are a few other issues. First, if you are running under medium trust, with the default configuration, you cannot define configuration sections. Second, if you are in medium trust, the cache location will need to be somewhere within your application’s directories. Medium trust often doesn’t let you read or write outside of the application. Third, you cannot use a string like “~/temp” you need to specify the full path.
12 May, 2008 at 8:31 pm |
Thanks for the post – very helpful!
12 May, 2008 at 8:36 pm |
A quick question, I run into the following error pretty frequently…
“Sorry, the Flickr API service is not currently available. (0)”
I can’t believe the API is down as frequently as I receive this error or else it would be completely useless. Any ideas why this is happening?
Thanks in advance.