On Jul 7, 2008, at 3:20 AM, Allan, CJ (Chris) wrote:
Hi,
Thanks very much for the reply. I have managed to get a working
ModuleVersionHandler.
However, I'm still slightly confused. In my development environment
(which is Completely out of sync with the production environment)
the update all went fine. However, when I tried to install it in the
production environment I got the following error:
Could not perform installation: Error importing
config.modules.diamond.dialogs.diamond.siblingPages: a node with
uuid 64a29663-997e-4eb6-9d1f-16632185d066 already exists!
Performing a query against this uuid it returned: /modules/
templating/dialogs/paragraphList
(this is a custom dialog definition created a while back - it is not
encapsulated within any module, merely added manually to the config
repository).
This most likely is happening because you moved that node to your own
module before exporting it. Moving keeps the original uuid. Just copy
it or create a new one instead.
Also, looking at DMSModuleVersionHandler, it doesn't use any
importUUIDBehaviour. Is this just hoping that there won't already be
a node with a matching uuid, and leaving the problem for the user to
deal with if their is?
Except there is no valid reason for this to happen. We changed this in
3.5 to avoid ghost problems: sometimes, by accident, we also had moved
nodes around before exporting them in a new module for instance. What
then happened is that the original node suddenly disappeared without
warning from their original location, while what we really wanted was
to keep both. Blowing on uuid conflicts is the safest way of avoiding
these problems and forces the module developer to deal with them
properly.
-g
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
