I don't know where exactly it is happening in your app, but in 3.1 at
least I know I came across a special way that magnolia would store links
to pages/documents that it contained. I believe it is within paragraphs
that have content edited in FCKEditor and paragraphs created using the
UUIDLink control (there may be other ways but those are the two I'm
currently aware of). The link format is
${link:{uuid:{005cb600-8d4b-46e5-bf21-2f9136237834},repository:{dms},han
dle:{/untitled/callas1},nodeData:{},extension:{jpg}}} (This one might
not actually work in the latest release of magnolia 3.1, I did some
hacking to get it to work with the dms and image types and don't recall
right now which things I had to tweak). It is pretty self-explanatory
what is going on in the link, uuid: is the uuid of the node referenced
by the link, repository: is the repository the node is contained within,
handle: is the url or unique path of the node referenced, and extension:
is the file extension of the node referenced (I don't remember if I've
ever seen the nodeData used for anything, but don't recall what it is
for).
The thing I like about these links is that they help ensure portability.
I don't recall right now the order of trying the uuid and the handle but
I believe if it isn't able to find the link then it tries the uuid and
vice versa. If I remember the UUIDLink code correctly, UUIDLink spits
out the error you're seeing when it is unable to generate a web-friendly
link from the magnolia link via the uuid and is letting you know that it
will try to use the handle instead to generate the link. This is
significant because if you moved the node in magnolia the uuid will
remain constant but the handle would change. It can go the other way,
where if you deleted a node but added a new node that had the exact
handle as the deleted node it would then be able to reference the link
via that.
Just as a side note, if the latter case happens where the uuid is
outdated, if I remember correctly, you just need to open up the
paragraph that has the old uuid in it (but with the correct handle) and
save it. I think that updates the uuid (maybe someone from the magnolia
team can confirm or reject that if I'm remembering incorrectly). It is
probably good to do if your site has a tendency to replace pages/files
frequently and move things around.
Hope that helps,
Tom
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 20, 2007 7:34 AM
> To: [email protected]
> Subject: [magnolia-user] can't get node with uuid
>
> Hello
>
>
> I was wondering if anyone has experienced a following
> warnings in their Magnolia logs:
>
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [c7f9ae9d-a4d4-4b2a-8dd7-c3220ed273c1] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [5776c47e-7530-4665-85b3-7680cbd13eb4] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [bb2aa22e-8041-47a5-a1af-8cac724e92b0] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [9f3a05a0-9355-4545-acb2-c9b0db08d1fe] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [59322f3f-7111-4652-af30-744ff17b8d98] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [2d35abae-978e-40e2-9b29-0e8acfa611ae] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [0ae4cc52-cc8f-40d2-9964-cea6181af6fd] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [b6483b81-ef45-4c0e-8940-98d4c66fca31] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [a8ac6102-5dd1-4c24-a0c9-56ed2c816b7c] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [38766c81-4cc7-4e33-9594-8cf3b16223e1] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [1f2f4f30-a1da-4e62-9612-2d44170f9ce0] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [4725690b-9e65-4a4f-aab7-c2532b716ab6] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [9f328353-cb47-4bd7-b8a0-9b0ac0aa0d9e] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [1a9e16af-858e-4708-b9b4-06fb9d1a38cd] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [5e6d216e-5f65-4e03-97b7-d43cb5924134] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [5e6d216e-5f65-4e03-97b7-d43cb5924134] will try stored handle [null]
> WARN info.magnolia.cms.link.UUIDLink 20.09.2007 09:23:06 --
> can't get node with uuid
> [1a9e16af-858e-4708-b9b4-06fb9d1a38cd] will try stored handle [null]
>
>
> I would very much like to find out which page is trying to
> access these nodes so I can go that page and fix it.
> Is there a way to do this?
>
>
> Any information that would help determining the page that
> reffers to these unkonwn UUIDS without a handle would help
>
>
>
> Regards
> Amir
>
>
> ----------------------------------------------------------------
> for list details see
> http://documentation.magnolia.info/docs/en/editor/stayupdated.html
> ----------------------------------------------------------------
>
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
