Joern Nettingsmeier schrieb:
> Andreas Hartmann wrote:
>> Joern Nettingsmeier schrieb:
>>> iirc there was consensus to get rid of the area concept in future
>>> developments, so we should not add more area-handling code now if
>>> possible...
>>
>> Agreed. So maybe we should add a small workaround to the
>> uuid2url transformer.
>>
>>> anyways, why does the transformer have to rewrite what it thinks is the
>>> "area" part of the URL at all?
>>
>> /*
>> * This is legacy code. It rewrites links to
>> * non-document images (in resources/shared). These
>> * images shouldn't be referenced in documents since
>> * this violates the separation between content and
>> * layout.
>> */
>>
>> The URLs have to be rewritten, e.g., when publishing a document.
>> We could just match for "authoring" here, that should do for the
>> moment.
>
> i see. yes, a commented hack that's local to the rewriter is probably best.
Done.
>>>>> /{pub}/{area}/modules/{module}/...
>>>>> /{pub}/{area}/lenya-modules/{module}/...
>>>>>
>>>>> The former is less verbose, but more likely to cause URL clashes. The
>>>>> latter is probably quite safe.
>>>>>
>>>>> OTOH, some people might not want external URLs to contain the name
>>>>> of the CMS. Should we make this configurable?
>>> i'd very much prefer convention over configuration in such matters.
>>> and for the reason you stated, i prefer "modules".
>>
>> Is this sufficient re. forward compatibility, or should we use
>> "lenya/modules", in case there are other CMS-related URL spaces
>> to come?
>
> good point.
> but i think in the future we should keep out of the uri space as far as
> possible. and everything should be a module. so reserving "module" is
> sufficient imho, and it imposes some discipline on us wrt uri space :)
Sounds reasonable. IIUC, that would mean
/{pub}/{area}/modules/{module}/...
Should we remove support for the following URL syntax?
/{pub}/modules/{module}/...
IMO yes - when we get rid the area-in-url concept, everything goes
just one level up.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
