Thanks! This is exactly what I was looking for. I hadn't delved much
into the whole version handler stuff because our module is still in the
"old style" (extending AbstractAdminModule), due to the lack of
documentation on the custom modules for 3.5. But this seems to work
just fine even though our module isn't updated... and as a bonus I've
now figured out how to set several properties that we couldn't do with
XML files that we always had notes to manually set them by hand after
bootstrapping was done! :-)
Philippe Marschall wrote:
Is there any easy way that we can get our filter to bootstrap into the
proper order without having to manually move it?
In the version handler of your module add the following task:
new OrderNodeBeforeTask(
"Move Hibernate Filter",
"Moves the ourHibernateFilter before the cms filter",
ContentRepository.CONFIG,
"/server/filters/cms",
"ourHibernateFilter")
--
Miranda Jones
Objective Consulting, Inc.
http://www.spiders.com
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
