deko

I use the same db for some blogs, which accomplishes what your’re trying to do. I have several wp installs with several domains hitting the same box. I have plenty of dbs, but some blogs share the same db/content, some cat specific. As far as users can tell, they are diff sites, diff blogs. custom headers link diff sytlesheets.

The transparency of wp’s code and flexibilty of php makes this relatively easy. mod-rewrite is tricky but worth the learning curve.

If you don’t want your blogs to share a db, you’ll need to roll your own mysql to pull the content in where you want it.

For one thing, I would not use percentage-based font sizes. Designating font sizes in px is the better way to go, despite what the “standards police” say. px will ensure your design is rendered properly.

Clearly you can’t police outside sites, that’s not what I was suggesting.

Whether or not it’s “part of the codex” is a subtle and debatable point.

The issue as I see it is one of protecting the WordPress name and reputation, and by association, webmasters who use the software on their sites.

My suggestion would be to clearly segregate (on a separate page) ALL “outside” links with a loud disclaimer and warning. This would keep open an avenue of contribution while distancing WP from the damage that can (and has already) result from links/submissions with questionable content.

I’ve done this. I’ve written a script that dynamically selects a category-specific header image as well.

If you’re comfortable with php, it’s a snap.

In any case, use the archive template with a loop that looks something like this:

<?php get_header(); ?>
<div id="content" class="narrowcolumn">
<?php if (have_posts()) : ?>
<?php $post = $posts[0]; // Hack. Set $post so that the_date() works. ?>
<?php if (is_category()) { ?><h2 class="red"><?php
if (!in_category(1)) { echo single_cat_title(); } }?></h2>
<div class="navigation">
<div class="alignleft"><?php next_posts_link('&laquo; Previous Entries') ?></div>
<div class="alignright"><?php previous_posts_link('Next Entries &raquo;') ?></div>
</div>
<?php while (have_posts()) : the_post(); ?>
<div class="post">
<h2 id="post-<?php the_ID(); ?>"><a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link to <?php the_title(); ?>"><?php the_title(); ?></a></h2>
<div class="entry">
<?php the_content() ?>
</div>
<p class="postmetadata">Posted in <?php the_category(', ') ?> | <?php edit_post_link('Edit', '', ' | '); ?>
<?php comments_popup_link('No Comments »', '1 Comment »', '% Comments »'); ?></p>
</div>
<?php endwhile; ?>

This is a bit OT, but does anyone know how to use rewrite rules to have 3 domains use the same server – with 3 index.php’s in 3 different subdirectories?

I tried this:

Options All -Indexes
RewriteCond %{HTTP_HOST} ^www.oldsite1.com$ [NC,OR]
RewriteCond %{HTTP_HOST} ^oldsite1.com$ [NC]
RewriteRule ^(.*)$ http: //newsite.com/oldsite1/index.php
RewriteCond %{HTTP_HOST} ^www.oldsite2.com$ [NC,OR]
RewriteCond %{HTTP_HOST} ^oldsite2.com$ [NC]
RewriteRule ^(.*)$ http: //newsite.com/oldsite2/index.php
[and so on for oldsite3, 4, etc.]

This does not get requests to the subdirectory…

Any suggestions appreciated!

I’ve heard PS is powerful. I can imagine PS adepts will find FW lightweight or inadequate.

When you say photo processing – what are you talking about? Do you mean adjusting color, removing red eye, stuff like that?

I can create various layers with FW, drop in and tweak text, add various effects, select transparencies, define a target size for the image, use editing and slicing tools, create rollovers (FW auto-generates JavaScript and HTML), etc. etc… along with all the usual drawing, airbrushes and editing tools. I especially like the “canvas” and the different ways that can be used.

I’m really curious what it is that PS does that FW cannot, and what PS is best at. Seems that PS is better for the heavy lifting of photo processing – whatever that is… ?