Joshua A. Andler wrote:
On Thu, 2005-03-10 at 20:02 +0000, Jonathan Leighton wrote:
I've been working on a prototype of the Inkscape news using
WordPress,
but am having trouble as URIs for archives come out like "/archives/2005/01/". Due to the relative paths used on the website,
the
browser then can't locate the stylesheets, and links point to the
wrong
place on those pages.
So... does it matter if I change to absolute paths? (Which, IMHO,
are
better anyway)
Well, before you do any changes, why don't you show us all what you
have
done so far. Absolute paths make testing the site difficult on other peoples machines. Also, then the site is not very portable. One of the reasons I'm not totally sold on CMS' or blog management systems is
that
aforementioned do these types of hard-path/absolute path which then won't allow developers to test wherever they like on their own
machine,
and then have dependency-laden code break without installing X, Y, and Z. However, maybe your work will prove me wrong ;)
Is this really going to be an issue? I ask because if Wordpress is only going to be used for the news, it doesn't affect things too much if it is an absolute path. I think it's not a problem specifically because if you want to add news, it's done on the site where you can preview it... it doesn't really require testing/previewing on anyone's system since it'll be done on the server.
Yes, it's an issue because it would mean making all the link that are common throughout the site (header, footer, sidebar) into absolute paths.
Jonathan, you have removed all commenting stuff and renamed the "post" file, correct? The only issue with Wordpress tends to be spam... and with those two things taken care of it will usually eliminate it.
Yeah, I deleted the files we don't need (comments, trackbacks, pingbacks etc). We can also set WordPress not to ping any sites when new posts are made (this isn't really needed). That said, I guess there may be a few persistent spammers trying to get us anyway, so maybe it'd be better to just have blank comment/trackback/pingback files to prevent 404s. I'll do that.
Even if, by some act of God, some spammer *did* manage to get some spam into the database, it wouldn't display because I haven't put the code in the template.