Jörg Schaible wrote: > yesterday I wanted to change the I18nContentSupport implemenattion by setting > a new value for Configuration/server/i18n/content/class. However, I made a > typo and the result was fatal, because Magnolia simply crashed with each > request and was afterwards no longer able to start up. > > Fortunately I use a filesystem-based repository where I could fix the problem > with a hex editor. Nevertheless, would there have been any other possibility > to fix this value?
We've also managed to hose a break a Magnolia instance on multiple occasions. Luckily most of the times we've been able to use the Groovy Rescue Servlet to fix things: http://documentation.magnolia-cms.com/modules/groovy.html#Rescueservlet Nils. ------------------------------------------------------------------------ VPRO www.vpro.nl ------------------------------------------------------------------------ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
