Eric Mann

The alternative is to set the page template directly in the database itself. This is tricky, can cause a lot of problems if done incorrectly, and requires you to be somewhat adept at working directly with the WP database through phpMyAdmin.

If you’re up to that, let me know and I’ll give you pointers.

First, don’t put your function in header.php. Functions belong in functions.php.

Second, the correct function is:

function fotogalerija($povezava, $slika)
{
echo '<tr><td class=galerija_slika><a href="http://galerija.smucka.com/categories.php?cat_id='.$povezava.'"><img src="/foto/'.$slika.'/prva_s.jpg" width=340 height=120></a>
</td></tr></table>';
}

This will give you a function you can call on your page templates. Unfortunately, you cannot call the function directly in post or page content. You need to edit the page template (the code that generates the page) in order to use a function like this. If you want to execute php code in the content section of a post or page, you need to install the following plugin:
http://wordpress.org/extend/plugins/exec-php/

This will allow you to execute php code directly.

Gary,

Please post a link or reference some screenshots so we can diagnose the problem.

1. Yes, this is safe to do.
2. See above.
3. You’ll need a little bit of custom coding to make this work …

It’s possible to have multiple sites run off the same database (pulling the same content from the same tables) without having to copy anything back and forth. The problem comes when you want different themes for each site. The blog theme is actually set in the wp_options table, so if your sites are all pulling from the same database they will all use the same theme.

There are several theme-switching plugins available already that you can look into using. That would be the easiest solution for you assuming you don’t want to spend any time or budget on developing custom functionality.

Here are a couple of theme switching plugins:

1. http://wordpress.org/extend/plugins/nkthemeswitch/
2. http://wordpress.org/extend/plugins/theme-switcher/

The alternative is to use a modification of a system like WP Hive. This plugin allows you to install multiple blogs on the same database using different tables – the plugin actually handles which blog points to which table. This could be modified to give you a separate options table for each blog while leaving the rest of the tables alone. This would require a significant amount of custom coding, so I recommend either contacting a developer (I can recommend a few) or dropping a request on http://jobs.wordpress.net. In either case, this route would probably cost you money.

4. The maximum number of blogs depends entirely on your server setup and traffic. I run 10 blogs off the same database with no trouble at all.

If it is meant to be beneath the footer text (“Our Green Friends,” “Navigation,” etc) do the following:

Add “clear:both;” to the CSS definition for #footerbg

That should fix any problems you’re having. If that’s not the behavior you want, let me know here.

A fix that I’ve used is more of a workaround. I create a transparent GIF alternative (it’s lower quality, but I live with it) and add a couple of lines in my CSS file to override the PNG.

So if you have:

#headbg {
	background:transparent url(images/logo.png) no-repeat scroll center right;
}

Then you add this immediately below that line:

* html #headbg {
	background:transparent url(images/logo.gif) no-repeat scroll center right;
}

The * html at the beginning of the line is only read by IE, all modern “nice” browsers will ignore this, but for IE6 it will replace the PNG image with the GIF. IE6 plays nice with transparent GIFs, so this shouldn’t cause any issues.

See it in action here: http://www.ghcnews.org (the logo on the right-hand side of the top banner).

I found this issue as well, thanks for letting me know which core file to tweak to fix it. I did some more research, though, and it looks like “role” will be a valid attribute in XHTML 2. Since we can’t even validate XHTML 2 yet, though, I’m wondering if there’s a better way to fix this in the short run …