Maybe you can use the groovyshell module and a groovy script to clean broken item states: http://lab.openmindonline.it/wiki/display/OPENUTILS/Repair+jcr+nodes+with+broken+item+states+with+openutils-mgnlgroovy
Manuel On Tue, Sep 22, 2009 at 2:51 PM, Zdenek Skodik < [email protected]> wrote: > > ...sorry. I forgot to mention that you have to > switch off the versioning command at > modules/admininterface/commands/website > > - > Best regards, > > Zdenek Skodik > Magnolia International Ltd. > > Magnolia® - Simple Open-Source Content Management > > > On Út, 2009-09-22 at 14:43 +0200, Zdenek Skodik wrote: > > > > yeah follow to Configuration/server/version/active -> false. > > > > - > > Best regards, > > > > Zdenek Skodik > > Magnolia International Ltd. > > > > Magnolia® - Simple Open-Source Content Management > > > > > > On Út, 2009-09-22 at 07:39 -0500, Thomas Duffey wrote: > > > > > > On Sep 22, 2009, at 3:11 AM, Zdenek Skodik wrote: > > > > > > > So in general you have two possibilities: > > > > * try to reactivate it with disabled versioning > > > > > > Is there an easy way to try this? > > > > > > Tom > > > > > > > On Po, 2009-09-21 at 14:52 -0500, Thomas Duffey wrote: > > > >> So here's a crappy situation. I have a site running Magnolia 4.1 w/ > > > >> the PostgreSQL bundle DB persistence manager. The server suffered > > > >> file system corruption leading to me having no choice but to delete > > > >> some rows from the "version_bundle" table. There is no good backup. > > > >> > > > >> Magnolia is running but now complains about version problems when I > > > >> try to activate some of the content, e.g., > > > >> > > > >> 2009-09-21 12:57:57,607 ERROR > > > >> info.magnolia.cms.core.version.BaseVersionManager : failed to copy > > > >> versionable node to version store, reverting all changes made in > this > > > >> session > > > >> 2009-09-21 12:57:57,607 ERROR > > > >> olia.module.admininterface.commands.VersionCommand: can't version > > > >> javax.jcr.RepositoryException: 5848fbd6-e5d9-4156-bc9d-7cc5fcfbc303: > > > >> 5848fbd6-e5d9-4156-bc9d-7cc5fcfbc303 > > > >> > > > >> org.apache.jackrabbit.core.state.ItemStateException: Unable to > > > >> resolve > > > >> path for item: 1b7820ec-e8b3-4ed3-939d-2698057c42d9/{ > http://www.jcp.org/jcr/1.0 > > > >> }successors > > > >> > > > >> 2009-09-21 12:53:42,933 ERROR > > > >> olia.module.admininterface.commands.VersionCommand: can't version > > > >> java.lang.IllegalArgumentException: Failed to create version {}1.1. > > > >> > > > >> etc. > > > >> > > > >> Grasping at straws here but does anyone have any suggestions for > > > >> cleaning this up? The approach I am taking now is to export all the > > > >> content since at least most of it still seems to be there into a > > > >> separate instance of Magnolia and then eventually move it all back > > > >> over. > > > > > > > > > ---------------------------------------------------------------- > > > 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]> > > ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > 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]> ----------------------------------------------------------------
