Brian Gernhardt wrote:
> The Alias Page I wrote is amazingly simple and useful. If the core
> team decides that it's fundamentally flawed in some method that
> requires me to change it, I understand. But I simply used it as an
> example near to my heart. Changing Radiant to have "One True URL"
> for pages limits the power of virtual pages and extensions, and
> that's all I wish to speak against.
Hi Brian,
That is reasonable. I don't suggest to force an entirely different URL
onto something that was addressed via an alias, virtual or other
abstract page. However, if you have a virtual page or an alias page, I
don't think it is too much to ask for what its canonical URL should be.
Something similar is already done with the Archive page, that generates
URLs that are not only composed of the slug of the page and the slugs of
the page's ancestors. All I am suggesting is to redirect if
clean_url(Page#url) != request url [1]. The model can then decide how to
compute the URL. I suspect your alias page model's url method already
computes /other_site/alias_page instead of /first_site/source_page.
Cheers,
Oliver
[1] I believe clean_url currently adds a trailing slash, which has to be
fixed and left up to the model to do if necessary.
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
