You can specify the location of images within the .php theme files by using the following tag, bloginfo(‘template_directory’) . You could use it like this,

[img src="[?php bloginfo('template_directory'); ?/]/images/example.png” alt=”Image” /]

So you would need to place the ‘example.png’ image in a folder /images/ within /sandbox/, i.e.,

../wp-content/themes/sandbox/images/example.png

Within the CSS files, you can just specify the directory relative to the .css file. Look at the CSS files in the /skins / directory to see how they call the style.css file in the parent folder.

@Adam: I tried your suggestion, but unfortunately each line in footer.php has it’s own paragraph tags. It applies 50px of padding to the top of each line, thus running the text off of the footer and extending the whole page an extra 100px. I could edit footer.php, but that gets me back to my original problem where I didn’t want to have to touch the core K2 files.

This is what I currently have in my skin’s CSS (the last line offsets the core style.css padding):

#footer {
background: url('footer.png') no-repeat;
height: 100px;
padding: 0px 0 !important;
}


anyway, i posted in that thread, i don’t know if you saw it. you should be able to add padding to the contents of #footer (without padding #footer), by using #footer * { padding-top: 50px; } (the star means “all elements inside of”

I really like Sandbox so far. I might just work on it instead of fixing this theme in K2 (svn-323 also has support for multiple columns built-in…further complicating anything I do).

About the only thing that bothers me about Sandbox is kind of minor. It appears that you have to put your skin’s CSS and Screenshot in the wp-admin/themes/sandbox/skins folder. From an organizational standpoint it would seem more logical to me to have Sandbox read subfolders for skins (e.g., themes/sandbox/skins/k2, ..skins/cutline, etc.).

Oh, and after working with Sandbox I can’t live without a “wrapper” div. It’s priceless.

I suppose there’s more than one way to skin a cat, though…and it was easier to see the solution in Sandbox: If I set the wrapper div to be 10px wider (780px) and put the background there, rather than on the body (and try to line things up), then it displays correctly in FF and IE7. I just have to push the padding in on the left and right of the wrapper to compensate for the extra width. I can’t use a horizontally repeating image for the header and footer (have to create a 780px wide background for those), but I guess it’s a small price to pay for squashing the bug.

I still think that (considering browser incompatabilities) moving the stylesheet code out of the header is a mistake (that is, if I’m understanding this change correctly…and there isn’t a way of still dealing with it in the header).