It's hard to tell from your example which is most important to the
client, the archive functionality or the short URLs. If they don't need
year/month/day archives, I'd say just dump the archive idea altogether.
You can still order the child pages by date, so there should be no
problem there.
Your 'archive' page, should you need it, could be a sibling or a child
of /blog, have some method of excluding it from the list if it's a child
(like the 'no_map' part for the sitemapper example), and use
<r:children:each:header> to generate the 'archive' list from /blog.
Sean
Nathaniel Talbott wrote:
On Thu, Jun 5, 2008 at 12:20 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote:
I think overriding Page#find_by_url for the /blog page would be the answer.
The main downside I see to this is that the pages will remain
accessible under the longer urls as well, which I know the client
won't like (this is all about SEO). Any good remedy for that?
One approach I'm considering is to just nest the pages directly under
the main blog page, and add an archive page to sit next to them
(probably with some custom tags). I think that would solve all my
issues, but I'm not sure.
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
