Guys, 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? Imagine someone edits the value in AdminCentral and a global dialog box appears - the currently edited value would be saved (because the focus is lost) and the repo is hosed. Otherwise I'll open a JIRA issue with an enhancement request for fallback values of such sensible entries. Cheers, Jörg ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
