Currently I started implementing something like this, having the idea:
- Generate a localized URL Segment from Title using the path utility
(Path. getValidatedLabel()) with the title and fallback to the name which
is done using Content.getTitle().
- extending the Default I18n-Support, overriding the toI18nURI(path,
locale) ONLY
- Having virtual URI path-segments and mappings generated on
a) startup bootstrapping-task
b) saving a Page and
c) Custom Command which also is used from boostrapping task.
- The URL part for a page is created while saving the page properties by
custom control implementation according to the page title
- the virtual URI mappings then should also get updated directly
on saving the control value.
IMO my approach is way too complicated, still. Much redundancy and
instability, hard to debug. Proof of concept is still not achieved, yet.
Now there seem to be problems resolving the resources (CSS/JS) first,
since the (EE) site-support now somehow prefixes all /resource/.. URLs
with the site-mapping which is '/home' (maybe need to put all to the
website-repo root instead to make it work?) Admin central still looks well
at least.
So basically I would most likely prefer a much simpler approach, say a
simple jcr-query for resolving a localized URL, which could directly
matching the request-URI (prefixed with the locale) based on the titles
over the whole page hierarchy. Then caching the path as virtualURIMapping
to map the default-i18n-content support and so on, since the virtualURI
mapping filter is preceding the i18n-filter.
I expect an hourly task for re-generating the mappings could also be
feasible, maybe started on publishing or changing content in the website
repository.
Currently I'm kind of stuck and will probably start-over the whole
concept, since I don't see that I can make it work simply by following my
current approach from above.
Any hints of experiences developing something like this are appreciated.
Regards
--
15 Years of Excellence - http://netcetera.com
Marco Glur | [email protected]
T +41 44 247 79 20
Netcetera AG | 8040 Zurich | Switzerland | http://netcetera.com
>-----Original Message-----
>From: [email protected] [mailto:user-list-
>[email protected]] On Behalf Of Marvin Kerkhoff
>Sent: Donnerstag, 30. Juni 2011 10:43
>To: Magnolia User-List
>Subject: AW: [magnolia-user] SEO localized URLs
>
>
>It is possible to make a clean summary of the solutions and fill it in
the
>Administration Manual? I've already had the same questions.
>
>Thanks
>Marvin
>
>-----Ursprüngliche Nachricht-----
>Von: [email protected] [mailto:user-list-owner@magnolia-
>cms.com] Im Auftrag von Christian Menzel
>Gesendet: Mittwoch, 29. Juni 2011 11:18
>An: [email protected]
>Betreff: Re: [magnolia-user] SEO localized URLs
>
>
>Of course not. We use nested maps to hold a dictionary for each level.
>This directory is populated on startup and page updates with page name
and
>translations.
>
>Christian
>
>On Mi, 2011-06-29 at 10:42 +0200, Will Scheidegger wrote:
>> How did you solve the URIMapping part exactly? You did not create the
>mappings manually, did you?
>>
>> -will
>>
>> On 29.06.2011, at 10:30, Marco Glur wrote:
>>
>> >
>> >> For suedtirol.info where the content also is held in a single tree
>> >> this was done with a LinkTransformer to generate localized URLs and
>> >> a URIMapping to map the generated URLs back to Magnolia content.
>> >
>> > Now, this sounds like a simple and efficient way to do this.
>> > Thanks for the hint. I guess that is exactly what we need.
>> > Best regards,
>> > Marco
>
>
>
>
>----------------------------------------------------------------
>For list details see
>http://www.magnolia-cms.com/community/mailing-lists.html
>To unsubscribe, E-mail to: <[email protected]>
>----------------------------------------------------------------
>
>
>
>----------------------------------------------------------------
>For list details see
>http://www.magnolia-cms.com/community/mailing-lists.html
>To unsubscribe, E-mail to: <[email protected]>
>----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
