Any advice would be greatly appreciated.
cheers, Michael
--
Michael C. Harris, School of CS&IT, RMIT University
http://twofishcreative.com/michael/blog
This should work for what you're trying to do on rev 1243.
Owen
And so it does! Thanks very much.
cheers, Michael
I was hoping to (or was hoping someone else to) write something more
comprehensive and configurable that could be included in core. I'm not
really sure how to approach the interface to such a thing though, since
the output can be so flexible.
Any ideas?
Owen
Yeah, that's a great idea. I'm still struggling with what that
interface looks like.
Does it not matter too much because it's an advanced feature? I don't
expect that everyone knows the difference between the match regex and
the build string and has the knowledge to build both. There's obviously
going to be different levels of this plugin -- A simple one that allows
a few standard changes, and a complex one that lets you edit directly.
Owen
:-)
-----Original Message-----
From: habar...@googlegroups.com [mailto:habar...@googlegroups.com] On
Behalf Of Owen Winkler
Sent: 5. januar 2008 21:16
To: habar...@googlegroups.com
Subject: [habari-dev] Re: Display page at /, blog at /news
>
> Christian Mohn wrote:
>> How about a rewrite manager in admin? Somewhere you can make your
>> own rules
>> and assign them to templates of your choice? Of course, redirecting
>> your
>> "front page" to a page and place your "blog" at some other location
>> would be
>> an option here?
>
> Yeah, that's a great idea. I'm still struggling with what that
> interface looks like.
Does it really matter what colour we paint the bikeshed? Wouldn't it
be nicer just to have a bikeshed in trunk, even if we paint it later?
--
Geoffrey Sneddon
<http://gsnedders.com/>
I think you've misunderstood this as a bikeshed issue.
In order to produce this page, I need to know what controls go on it and
what they allow you to change. As of right now, I'm not sure what level
of detail those controls operate at or how they work.
Where they appear on the page, what they look like, what color they
are... Those are bikeshed issues. But first we actually need controls.
Owen
Would it be sufficient to provide in core a simple rewrite generator
that only lets you map new addresses to existing ones? In this way,
the end user wouldn't need to know about match regexes or build
strings, and would simply say "I want this content provided at this
URL". Think Drupal aliases: map an existing page to a new address.
An advanced plugin (core or otherwise) could permit more complex
rewrite generation.
I think this function is a good idea, but I can't figure out how to use
it to remap dynamic URLs.
For example, the default rewrites put date-based listings at the URL
/{year}/{month}/{day} It's also a very complex regex that takes into
account URLs that don't include some of the parameters. I don't know
how to map a single new address to that dynamic URL without a regex.
In Drupal, everything assumes a strict hierarchy where the leftmost
portion of the URL is responsible for the primary detection of the URL.
It would be difficult in Drupal to, for example, move the "node" part
of "node/add/page" to make the URL "add/node/page", whereas this would
be possible in Habari because of the regexes.
Maybe it's enough to allow users to add prefixes to the existing URLs?
I think it would be neat to allow anything from "/{year}/{month}/{day}"
to "/archive.{year}-{month}-{day}" to "/{month}/{day}/{year}" but I
don't know where the line is drawn for what we can offer through a
limited interface. There are clearly limited options for users who do
not know how to assemble regular expressions, but I wonder if there is
some interface we can concoct that could give them more capability
without forcing them to learn too much.
Owen