[ http://jira.magnolia.info/browse/MGNLDMS-86?page=comments#action_13243 ] Philipp Bracher commented on MGNLDMS-86: ----------------------------------------
You can switch off versioning / workflow when ever you like ;-) > activation of new documents / folders fails > ------------------------------------------- > > Key: MGNLDMS-86 > URL: http://jira.magnolia.info/browse/MGNLDMS-86 > Project: Magnolia DMS > Issue Type: Bug > Reporter: sebastian frick > Assigned To: Philipp Bracher > Priority: Critical > > split from http://jira.magnolia.info/browse/MGNLDMS-30 > we have the same problem as already reported by matthew schmidt in that older > issue, so i just quote his description. we're using magnolia (3.0) > "We're seeing a similar issue related to activating documents in the DMS. > When we make new folders (pre-existing ones are fine) and then try to > activate those folders or files in those folders we get the following error: > ERROR info.magnolia.cms.core.version.BaseVersionManager > BaseVersionManager.java(addVersion:129) 04.12.2006 14:29:43 failed to copy > versionable node to version store, reverting all changes made in this session > ERROR info.magnolia.module.admininterface.commands.VersionCommand > VersionCommand.java(execute:62) 04.12.2006 14:29:43 can't version > javax.jcr.ItemNotFoundException: failed to build path of > fc7f8677-c8be-4178-8789-edaaa082843b: cafebabe-cafe-babe-cafe-babecafebabe > has no child entry for fc7f8677-c8be-4178-8789-edaaa082843b" > our current workaround is to activate a copy of a new document, which seems > to work by now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
