kickass

Anyone stealing design AND bandwidth is just asking for it. Bigtime.

And, if the response is done in such a way that the ripper’s actual server and site is not touched in any way, shape or form, that is just poetic justice- though I might have gotten a bit more creative about what to show on the ripper’s page, maybe even disgustingly creative *evil grin* In fact, if anyone needs some rather unbelievable images for the purpose, contact me. Heh!

With my hosting account I can only access and/or change .htaccess in the filemanager that comes with my cpanel for the account, so that’s probably right. And, if that .htaccess file is located in your domain’s root directory it isn’t the right one (unless that’s your main wordpress directory!). You have to MAKE another .htaccess file in your toplevel wordpress directory, and, if you do it like I did and edit it yourself, copy the .htaccess new info out of your wordpress admin area for the permalink structure and paste it into your newly created .htaccess in your wordpress directory.

Oh geez, been there, done that. Hope this helps!

Just a suggestion- if your site is image intensive, why not create thumbs for the gallery page, clickable to the larger images? I suggest a width of around 70 to 80k per thumb. If the whole image loses too much that way, make your thumb a PORTION of the image. Whether this works with the plugins you choose for your gallery I dunno, but there must be galleries out there that work with thumbs, I see ’em all over the place. The thumbs should be in the neighborhood of 6-8k apiece, so if there are 20 on a page it isn’t nearly as bandwidth intensive as 20 20k images.

It looks really good, but you need to validate it and correct the html errors. I believe you changed the doctype to html 4.0 (why?) yet the page seems to be written as xhtml 1.0 transitional. Since WP is designed to function as xhtml I’d start by changing the doctype in header.php (or wherever the head of your html document is located) to the xhtml 1.0 transitional doctype tag, then run it through the validator and correct any errors from there.

The css came up clean. That’s a good thing.

You might want to take a peek at this article, it will tell you what you did- and what you didn’t do.

http://www.urbangiraffe.com/2005/04/12/themeguide1/

Kubrick is a hard theme to start with since the css is in more than one place. It’s also, in some ways, a good theme to start with, since it has ALL the pieces you need, and is a complete theme.

This article will tell you what is NECESSARY in your theme, how it works, what the different parts do, and how to change things. And if all else fails, c’mon over and snag a kickass theme.

IMHO, the comments system is better than a forum and serves pretty much the same purpose. And if you want your blog “hooked” to a forum you can always add a link to one as a static link.

I just looked at your site, both the screenshot and the site itself. Oddly enough, the site shows a sans-serif font in FireFox, and a serif font in IE in the areas you’ve highlighted, which tells me IE is playing css inheritance tricks again.

I would try defining the sans serif font-family on the body element, then removing all mention of font-family everywhere else in the stylesheet. Once you’ve done that, you can selectively add back in changes for the areas you want to be serif font. This will eventually get you where you want to go. Check in ALL browsers for each step you take, and post to the support board for browser checks in systems/browsers you don’t have.

I thought I’d mention that your theme design doesn’t hold up very well when a user increases font size in any browser, which is something anyone can do, and which can screw up a design royally. Increased to “largest” in IE and three clicks on “increase” in FF it’s a fair bit messy with lots of overlapping. You might want to rethink that a bit.