Thanks Sebastian, I believe I may have made a configuration change while trying to disable workflow that affected the command chain. User error :-/
> > Versioning shouldn't be workflow based. By default it's callen within > the command chain, which can be found under modules > adminInterface > > commands > website > activate > version. > > Sebastian > > VAUGHAN wrote: > > >Where in the process of activation does a new version get created for web > pages? I've tried looking at documentation, source, and mailing lists, > but I can't find exactly where BaseVersionManager.createVersion or > addVersion is called. The issue is that I keep getting "No VersionHistory > found for this node" messages whenever a page is activated, so it doesn't > seem to be creating versions for any pages. I have > "server/version/active" set to "true" and "server/version/maxVersionIndex" > set to "10". Is versioning dependent on having workflow enabled (because > I've disabled it on my instance)? > > > >Is there any documentation on how the Magnolia classes interact with one > another and the configuration settings for functionality such as > versioning and activation? > > > >Should I ask the dev-list for development docs? > > > >Dallas Vaughan > > No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 269.23.3/1393 - Release Date: 4/23/2008 8:12 AM ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
