This page (set up just so I could see how Blogger works) is a portal
to our adventures in food and drink, recipes, disasters, triumphs...


Please use the links below or go directly to the real blog from OUR kitchen



` ` `


29 May 2009

May 2009 blog entries

 
Friday, 29 May 2009
Yay! It's asparagus season
summary: pasta with asparagus, toasted pinenuts, caramelized onion, grainy mustard and goat cheese; why there are no photos in the post

Wednesday, 27 May 2009
Tying myself in knots OR to lard or not to lard (BBBwB)
summary: recipe for Italian knot bread made with active dry yeast; fresh and active dry yeast equivalents; Italian 00 flour equivalent(ish); YeastSpotting post; information on Bread Baking Babes; information about Breadline Africa's Worldwide Blogger Bake Off Challenge

Tuesday, 26 May 2009
I think I've fixed the sidebar!
summary: sidebar error messages on etherwork.net appear to be gone

Thursday, 21 May 2009
yes, I know... the sidebar display is messed up
summary: No idea why, when or if it will be resolved.

Tuesday, 19 May 2009
imported(?!!) dandelion greens (WHB#184: dandelion)
summary: recipe for dandelion greens in anchovy sauce with optional fried egg; information about dandelion for Weekend Herb Blogging;

Wednesday, 13 May 2009
spinach and baby artichoke spread (bookmarked recipe)
summary: recipe for spinach artichoke goat cheese spread; information about Bookmarked Recipes

Monday, 4 May 2009
exercises in futility are strangely rewarding
summary: blog recipe index; spinach artichoke dip tease

24 May 2009

internal server errors plaguing etherwork blog

I have no idea why the etherwork blog (my real blog) is suddenly plagued with internal server errors. For the most part, it seems to be only affecting the sidebar display (ie: sidebar is NOT displaying correctly) but it also seems to cause the page to not display at all if there is an attempt at commenting - there is a redirect to the internal server error page. This is quite trying, to say the least.

I have asked my webhost and it looks like it has something to do with my Wordpress installation. Because I'm using the "legacy" branch of wordpress, alas, it's up to me to fix the problem. My webhost cannot be troubleshooting their or my errors. RATS!

I'm not quite certain what I'm going to do about it: whether I'll upgrade to the latest wordpress or whether I'll switch to a different blogging platform like "live journal" or "movable type". Whatever I do, it's going to take time.

Rrrrrr. I loathe change!