Deleting and sys:archived aspect

[lista]

Hi,

I've noticed this on 3.4c.

Basically if I have a "test1" space node, and a "test2" content node inside of it (it's child), and if I proceed to delete the "test1" node, the following is true:

- by looking at deleted items, you only have one node there, "test1"
- "test2" is not visible there, even though it is deleted (you can find it by browsing "archive" store)
- "test1" got a shiny new "sys:archived" aspect, while "test2" didn't

Has anybody looked into this before, maybe this is a wanted behavior because of something I don't understand, but to me it looks like a bug?

Thanks!

[afaust]

Hello,

this is wanted behavior. Only the element that you have actually deleted as a user will get the aspect and will get listed in "deleted items".

Regards
Axel

[lista]

Thanks!

The problem was I used the aspect to check for deleted items (just like Alfresco Explorer does, for example) in a custom app, and this wasn't good enough for me. Another approach is to look at the store of the node and use that information to determine if something is deleted (archived) or not.

Once again, thanks!