I had a similar problem when using derby, so I removed the
write-protection for the folder (and subfolder) e.g.
magnoliaAuthor\repositories\magnolia which enabled me deleting the node.
but due to not knowing about any further consequences of my "solution" i
set up a new repository later.
sebastian
Jean Pierre Malrieu wrote:
I am using Derby (and moving soon to Berkeley). Does your
recommendation apply in that case?
JPM
Le 25 avr. 07 à 21:11, Sebastian Frick a écrit :
if your repository is stored in the file system, you should set
read/write-access-rights for the whole repositoryfolder and try again.
greets,
sebastian
Jean Pierre Malrieu wrote:
I known the list has already dealt about this, but I could'nt find
the answer in previous posts.
What is the easiest way to get rid of a dammaged node?
It is a "content-files" subnode of a paragraph node that cannot be
deleted, even in jcr browser, because it is empty...
This is really a stopper because I can no longer export the whole
website to xml...
Thanks
JPM
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
