Thanks Jan,
I added some lines to the start() method of a ModuleLifecycle class like this:
Content contentByUUID =
ContentUtil.getContentByUUID(ContentRepository.USERS,
"a7e7df3b-2547-47dd-942b-c57afdf02976");
Content parent = contentByUUID.getParent();
contentByUUID.delete();
parent.save();
And that worked beautifully. I let this here to run once of course.
Have a good weekend, Bert
> -----Original Message-----
> From: [email protected] [mailto:user-list-
> [email protected]] On Behalf Of Jan Haderka
> Sent: vrijdag 30 oktober 2009 14:23
> To: Magnolia User-List
> Subject: RE: [magnolia-user] import of public users does not work
>
>
>
> > Do you have a tip how to get rid of the unwanted nodes?
>
> Many different options, for example:
> - make the users workspace visible in jcr broswer (brace yourself, it
> will look weird w/ some nodes seemingly duplicated) and delete the
> copies of "public" you don't want
> - delete those nodes directly using BSH shell and shell module
> - write a custom class to delete those extra nodes
> - export whole users workspace, fix the export file, put it in the
> bootstrap folder, shutdown, delete users workspace, startup and hope
> for
> the best
>
> ... your pick ;)
>
> cheers,
> Jan
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
