[MGNLDMS-86] activation of new documents / folders fails Created: 24/Jan/07  Updated: 03/Jul/14  Resolved: 14/Feb/07

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.1

Type: Bug Priority: Critical
Reporter: Sebastian Frick Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

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.



 Comments   
Comment by Philipp Bracher [ 25/Jan/07 ]

the problem is caused by an issue created by the versioning rules used in dms. A quick workaround will be to remove the version command in the activation chain. You can do this by following this instructions:

  • open config: modules/dms/commands/dms/activate
  • delete the version command
  • this change does NOT need a restart of magnolia

Now you should be able to activate again.

Comment by sebastian.frick [ 25/Jan/07 ]

thx for this workaround, which is a way more comfortable than ours offtopic question: is there also a general possibility to deactivate versioning in the website-repository?

Comment by sebastian.frick [ 25/Jan/07 ]

ok, i've already found out how to deactivate versioning in the cms. it seems to speed up the workflow very well. is there anything critical except you can't restore older versions anymore?

Comment by Philipp Bracher [ 25/Jan/07 ]

You can switch off versioning / workflow when ever you like

Comment by sebastian.frick [ 02/Feb/07 ]

it seems that you can't active a document (without versioning) under a parent that has been already activated (with versionioning). in this case you need to activate the parent including subnodes. so this possibly could / should also happen when you deactivate versioning in the cms?

Generated at Mon Feb 12 00:48:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.