Hi, I just committed a filter that can be used to automatically remove the mix:versionable mixin while loading xml bootstrap files (or during activation from magnolia 3.5 to magnolia 3.6). I wasn't sure about enabling this by default, but if we know that there isn't anything marked as versionable in magnolia 3.6 this could be done.
Philipp, could you have a look at this to understand if it could be a replacement for the info.magnolia.setup.for3_6.CleanBootstrapFiles you wrote? fabrizio ---------- Forwarded message ---------- From: <[EMAIL PROTECTED]> Date: Mon, Jun 16, 2008 at 9:30 PM Subject: [magnolia-svn] [15867] A new "RemoveMixversionableFilter" for an easier transition to magnolia 3.6 + some refactoring/ generalization of an existing filter To: [EMAIL PROTECTED] Revision 15867 Author fgiust Date 2008-06-16 21:30:00 +0200 (Mon, 16 Jun 2008) Log Message A new "RemoveMixversionableFilter" for an easier transition to magnolia 3.6 + some refactoring/generalization of an existing filter Modified Paths magnolia/trunk/magnolia-core/src/main/java/info/magnolia/cms/core/ie/DataTransporter.java magnolia/trunk/magnolia-core/src/main/java/info/magnolia/cms/core/ie/filters/UselessNameFilter.java Added Paths magnolia/trunk/magnolia-core/src/main/java/info/magnolia/cms/core/ie/filters/RemoveMixversionableFilter.java magnolia/trunk/magnolia-core/src/main/java/info/magnolia/cms/core/ie/filters/SkipNodePropertyFilter.java ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
