Hi Harold, Thanks for the suggestion but we don't actually use the DMS module, so that won't help us unfortunately :-( It could be an option to move to using that if that's the only way to solve the problem, but we would have to change a lot of site templates and re-upload a lot of documents, so it's something we really want to avoid doing if we can.
Simon On 09/08/07, Capitaine Harold <[email protected]> wrote: > Hi Simon, > > I experienced this many times too. > > Have you already tried to import the pdf document directly in the dms, > and then tried to activate it? > I'm not sure (based on facts of my memory), but you should be able to do so. > Can you confirm what I said? > > Regards, > > CAPITAINE Harold > > > Simon Goodchild a écrit : > > This does seem to be a wider problem for people than I had thought - I > > reported the same symptoms a few months back and didn't get and > > response so I guessed it was only happening to me. > > > > I get exactly the same errors, and use the same workaround to get rid > > of the broken pages. I've seen it many times though, not just on one > > page - I have maybe 30 broken pages in the 'trash' area of one site. I > > can also replicate the issue quite easily, by trying to attach certain > > PDF documents using the FCKeditor upload feature. I only get the > > problems on one of my systems, which is a 3.0.2/MySQL/Linux install, > > while everything is fine on my dev environment which is the same but > > on Windows. I've tried exporting the site, doing a complete reinstall > > of magnolia into a blank DB, and reimporting the site, but still get > > the issues. > > > > As a side note, the PDFs that seem to break the pages in the first > > place are all generated with Ghostscript. If I regenerate the same > > document in Acrobat Distiller and attach that instead then everything > > is fine. > > > > I don't know if this is a Magnolia or Jackrabbit issue, so not sure if > > it should be opened as a JIRA issue here or not. When I last checked > > JIRA and the mailing lists for both Magnolia and Jackrabbit I couldn't > > find any related reports. I don't know enough about the low-level JCR > > side to track the problem myself, but I'm happy to give the developers > > whatever info I can to help resolve this. I can also give access to > > the main site we have problems with so they can see it for themselves > > if that helps. > > > > Thanks, > > > > Simon > > > > On 09/08/07, Thomas Martin <[email protected]> wrote: > > > >> I'm currently facing the same issue here. > >> > >> mag 3.0.2 - tomcat - bdb > >> > >> one page just could not be updated any more. so I tried to delete it > >> and I got: > >> > >> ERROR info.magnolia.module.admininterface.AdminTreeMVCHandler > >> AdminTreeMVCHandler.java(delete:376) 09.08.2007 02:56:00 can't delete > >> javax.jcr.ItemNotFoundException: edf788b3-ecf5-42d5-ad40-e790d109348d > >> > >> I tried to go through jcr Browser but got the same I deleted > >> everything inside the page and got stuck with the > >> "mainColumnParagraphs" content item that just can't get deleted anymore. > >> > >> for now I moved the page inside a hidden "trash" page but I consider > >> this an ugly situatiotion. > >> > >> anyone else dealing with these issues? > >> any clues on how to get rid of the zombie? > >> > >> cheers, Thomas > >> > >> > >> On 26.07.2007, at 09:32, Zdenko P. wrote: > >> > >> > >>> Hi Robin, > >>> > >>> yes, I am using two databases. Each of them in a separate directory > >>> author -> webapps/authorInstance/repositories/workspaces/... > >>> public -> webapps/publicInstance/repositories/workspaces/... > >>> > >>> I don't think that there is a problem with the position of the > >>> databases. I have about 70 pages created and this problem is only > >>> with one node in a paragraph. > >>> Is there a possibility to delete only this node in repository > >>> (manually). > >>> > >>> > >>> Best regards > >>> Zdenko > >>> > >>> > >>> > >>> --------------------------------------------------------- > >>> Hi Zdenko, > >>> > >>> are you using the same database for public and author instance? > >>> (You can check it under > >>> weapps/mangoliaAuthor/repositories/workspaces/<workspace>/ > >>> workspace.xml > >>> , the same for the public instance. Although you described a problem > >>> within your website repository, > >>> check the other repositories too.) Be sure that they are using > >>> different databases. > >>> > >>> Best regards > >>> Robin > >>> > >>> > >>> > >>> > >>> --------------------------------------------------------- > >>> Hi, > >>> > >>>>> I have a problem with an existing node in a page. I can't delete it. > >>>>> In the logs I get following errors: > >>>>> > >>>>> ERROR info.magnolia.context.WebContextImpl > >>>>> 18.04.2007 09:36:03 -- the > >>>>> current jcr session has pending changes but shouldn't please set to > >>>>> debug level to see the dumped details ERROR > >>>>> > >>>>> > >>> info.magnolia.module.admininterface.AdminTreeMVCHandler > >>> > >>> > >>>>> 18.04.2007 09:36:43 -- can't delete > >>>>> javax.jcr.RepositoryException: /: unable to update > >>>>> item.: > >>>>> 3418f5eb-92ee-4939-a342-37417f716a12: > >>>>> 3418f5eb-92ee-4939-a342-37417f716a12 > >>>>> at > >>>>> > >>>>> > >>> org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1212) > >>> > >>> > >>>>> ... > >>>>> ... > >>>>> Caused by: > >>>>> > >>>>> > >>> org.apache.jackrabbit.core.state.NoSuchItemStateException: > >>> > >>> > >>>>> 3418f5eb-92ee-4939-a342-37417f716a12 > >>>>> at > >>>>> > >>>>> > >>> org.apache.jackrabbit.core.state.SharedItemStateManager.getNodeReferen > >>> ces > >>> > >>> > >>>>> (SharedItemStateManager.java:330 > >>>>> ... > >>>>> ... > >>>>> > >>>>> In the mailing list I didn't found some help. Does anybody know the > >>>>> problem and a solution? In magnolia I set in the author instance the > >>>>> subscriber to false and try to delete the node. But in the logs > >>>>> there was the same error. How can I remove this node without delete > >>>>> the whole repository? > >>>>> Could it be a problem with versioning and publishing? > >>>>> > >>>>> I use Magnolia 3.0.2 Community Edition without custom settings. > >>>>> > >>>>> Thank you for help. > >>>>> Zdenko > >>>>> > >>> ---------------------------------------------------------------- > >>> 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 > >> ---------------------------------------------------------------- > >> > >> > > > > ---------------------------------------------------------------- > > 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 > ---------------------------------------------------------------- > ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
