Seems like a similar problem to http://forum.bytesforall.com/showthread.php?t=18344, but I'm not using any cache plugins...

Page: http://www.todddawsondesign.com/test/angus/
ATA 3.7.9
WP 3.4.2

The home page and the News page (which will have posts on it) don't show the graphics I've loaded into a text widget in the right hand column. Any ideas?

To get rid of the default widgets there, I just opened the sidebar on the Widgets page and deleted the ones there... THEN I read JD's instructions on how to do it right... would that have any effect?

What images do you have in the sidebar and how are they placed there?

Some social media icons, which I originally posted to to the Atahualpa Images folder via ftp, but then tried adding them through the Media Library. Neither one works.

You need to put the full path... Not just /wp-content...

Any particular reason why relative links work on interior pages but not on "home" pages?

the path to an image can be thought as being made of three parts: The domain name, the directory and the filename.
http://yourdomain.com/wp-content/uploads/2012/10/ FaceBook_32x32.png

When using relative paths to an image, the key is how you start it.
If you start with ../ you are telling the browser to go up one directory level from the relative location you are currently at. The relative path is effected by your permalink structure

If you start with just / you are saying to the browser 'tack the domain name in front of this path' and that should work in all cases.

if you want to see this in action, set up a text widget with

Full Path
<img src='http://www.todddawsondesign.com/test/angus/wp-content/uploads/2012/10/FaceBook_32x32.png'>
path with ../ before wp-content
<img src='../wp-content/uploads/2012/10/FaceBook_32x32.png'>
just / before wp-content
<img src='/wp-content/uploads/2012/10/FaceBook_32x32.png'>
nothing before wp-content
<img src='wp-content/uploads/2012/10/FaceBook_32x32.png'>

and go to
1) the home page
2) a single post page
3) a page page
then change the permalink structure - use a custom one and test again
then use a custom one and add '/x' somewhere in the path and test again

Thank you SO much JD! That gave me a much clearer understanding of what the symbology does and means, and after testing found only one worked in all cases (the full url).

I confess I didn't do the permalinks change, since I have no clue what that's about (and in reading some of the info on it detected conflicting info, so didn't want to try). Plus, not being a programmer, I have no clue what a /x would do or why, or where it should go, or anything.

But I really appreciate the walk through, and the testing. Very helpful.