If you have been getting script errors on your pages using blogfuel it's our fault! The problem only occurs with codes created prior to our update in May 2005. If you are affected simply recreate your code on our mainpages us version/uk version

Also textitles in your blogfuel boxes may have dissapeared for a while - sorry.

Heres a test to prove it is all working now..

As you probably noticed Blogfuel disappeared for a few days earlier this week. After a hosting dispute we have moved all our sites to a new server and sercurity settings that were default in the newest version of php caused us a few problems (for those that are interested it was the register globals setting being turned off in the ini file, which has resulted in us writing more secure code).

I should like to apologise for the break in service and thank those of you that had the patience to stay with us, or maybe you just didn't notice?

When posting to blogger with blogfuel code imbedded in your post the get a script tags not allowed message. Simply tick the "stop showing errors for this post" box and publish again and it works fine. Heres a blogfuel box to prove the point.

Its seems that following the changes at blogger script tags are no longer allowed in posts to blogspot hosted blogs, I will include a tag below to see if they are still permitted on remotely hosted blogs and get back to you about using them in templates at blogspot.

Our Google pank rank is upto six following the latest reshuffle, not amazing but good enough for me. The cache seems to be working fine now and blogfuel results seem, if anything to be feeding faster. There is still an issue with some amazon images having the wrong url, but this is something that affect the whole of amazon web services and not just blogfuel.

Amazon US Feed is back for the time being. I wil fine tune the cache a bit to try and minimise the impact of further outages.

The amazon.com web services feed is currently erratic at best and at worst non-existent. Unfortunately in an effort to discover the problem I deleted the cache which would normally protect against existing users noticing the fault - doh!

New section linking to blogfuel users added, if we haven't included your site email us

Yep I have finally got around to caching blogfuel results (even though it was a requirement from amazon from day one - oops!). What this means to end users is quite simply that everthing should work faster. The cache has a life of 24 hours, this is the maximum permitted by amazon. If anyone starts getting strange results let me know but it seems to all be working fine. Go ahead and cover your blogs with blogfuel results safe in the knowledge that they will no longer slow you down. If anyone is interested the script I used to implement the cache was Cache_lite it is really easy to use, get it here