Andreas Hartmann wrote:
Jürgen Ragaller schrieb:
Am Sep 30, 2006 um 17:58 schrieb Jörn Nettingsmeier:
hi everyone!
i wonder: should we move the default publication to uuid storage?
we will lose a test case for the migration target, but it seems quite
odd to me that our example publication is in a deprecated format that
will not even work out-of-the-box.
What came to my mind regarding this:
Wouldn't it be better to integrate the migration target into the build?
Otherwise the exact same uuids will be found in the default publications
of many users all over the planet (not exactly the purpose of uuids...).
Good point.
Maybe an even cleaner way would be to
- implement XML import/export (use site structure as directory
structure, similar to the old content storage)
- provide the default content as "exported XML"
Then the user could import the initial content and new UUIDs would
be generated.
This would be a nice feature anyway. Perhaps this could be handled via
webDAV? I have been meaning to fix propfind to work with the new uuid
site structure (Last time I looked it was broken).
--Doug
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
