vavroom

YOu ought to describe what the actual problem is…

Glad to be of service ??

If it’s a class, it would be
a.top:link
NOT
a:top:link

Bah, who cares about mods? Bunch of useless …

oh! Oooops, the moderators *are* reading this <grin>

I didn’t mean it ??

Seriously though, it’s good that it makes your life easier as well. Moderating is a tough and thankless job, particularly with users that are so irreverant all the time. ??

KUTGW

I’m sorry, I only use IE to test how the site looks, I only use Firefox as my browser. I’ve no idea why it’s not working for you in IE. FWIW, what version of IE are you using?

I’m sorry, I can’t suggest a theme for you, but the codex (see link to Docs above) has bunches of links to look through.

To get started making your own theme, often using an existing theme that you like is a good start.

Again, the codex is a good place to look. There’s a lot of information and tutorial about developing your own theme.

Above all, have fun ??

First thing you want to do is to validate your code against the W3C’s (x)html validator. there’s a few validation errors that may throw off your entire design. No point in trying to fix your css if the html code it’s been applied to is buggy.

For instance, in your header, you have an unclosed closing span tag…

Then, you may want to look at the relationship between your divs and your tables, and how you’ve assigned widths.

One possible problem is that your #wrapper div is set to 98% wide, with 10px margins and 1px borders. This means that you have you have 11px on each side, representing 1% on each side of available space. If your monitor resolution is anything less than 1100px wide (don’t forget the scrollbars), you’re likely to force horizontal scrolling.

If within that div you have things set at 100%, adding fixed margins and padding will also likely wreck havock.

FWIW, I’d also set the font sizes in EM or percentages rather than px, as that’s hard to resize for your visitors.

hope this helps

FWIW, at this point, i would not consider Joomla for any serious project. The latest release 1.0.11 is particularly buggy and has caused numerous servers to crash. The long awaited and upcoming 1.5 release doesn’t have a stable release date planned, and there is no upgrade path (so you won’t be able to go from 1.0.x to 1.5. Further, the 2.x releases will also not allow going from 1.0.x and 1.5.

Don’t get me wrong, joomla is a good system, I use it on several sites I run (heck, I used to be on the Core team). But for a new project of that span, I would not consider using Joomla at this point.

The fact is, any system selected for this project will need significant work done. For instance, joomla “as is” won’t let you do the image thing you want. Nor does WP, Mambo, Drupal or any number of others.

I do think that with relatively minimal work you can achieve a good result for your goal using WP, and I’d look at integrating Gallery2 as the photo gallery system. There is a plugin that does the integration for you. I haven’t used it but by all accounts it’s very solid.

You should be seeing a message that says “If your files were writable, you could do this” or some such. T

In your FTP software, or in your file manager through your host’s control panel, or in shell if you have shell access, which you probably don’t, you have to change permissions on the theme files.

This is often referred to as CHMOD.

Set the files at 777 before making edits. Return them to 644 afterwards (well, you don’t have to, but many people prefer to as it’s often deemed safer)

Beat? He said “beat”. I hope it was fun… bed? beat in bed?

Ohhh, shut up vavroom…

as spencer said, seeing what’s going now on your page would be helpful, as there are many ways to do what you want to achieve.

Something to consider, if you replace the text by an image completely, but don’t provide the text in text format in some way, you’re seriously reducing accessibility of your site, both for people with disabilities, but also those people accessing your site from mobile phones or handheld devices.

well, generally speaking, background images are actually good, if they are just “decoration”, in that you don’t really need to present them to non-sighted visitors, or those who surf without images.

However, I feel that at least your image that says “broken machines” with the logo actually does bring something. Though if you kept the image as a background image, and added a h1 that said “broken machines” or something like that, you’d be good to go I think.

The alternative is that instead of displaying the logo as a background image, you could display it as a regular image, which then allows you to use the alt text attribute of the img tag.

YOu may also want to run your site through the w3c’s validator, you have about a dozen errors ??

HTH

Nice simple site ?? Will gain from having more content ??

If you’re heading for standards compliance, you have still some work to do.

You dont’ have a h1, for starters… You ought to.

Some of your images really would gain by not being background images, and having some alternate text, though using background images + regular header might also do the trick.

As a visitor to the site, I think that having a photo of the band on the front page would be attractive.

You have a “login/register” function, but why should I, as a visitor, register to yet another site? What’s in it for me? make it clear ??

Just my two cents from looking at the site very very briefly.

Also if you have Skype installed and setup to automatically run on startup, it might be your problem as it uses port 80 as well, by default.

Interesting site. A few things.

It took *forever* to load (40++ seconds).

It’s not in English (which isnt’ a problem, but being warned ahead would have been nice)

I think that telling people which browsers/technologies they must use to view the site is something out of the mid 90’s, and totally passe. Sites should work on all platforms and browsers, and if you have flash, alternative content should be available.

my 2 cents.

If XAMPP and WAMP don’t work, it’s probably a problem with the local apache/php/mysql install rather than a problem with WP.