Guys, this is unfortunately a wide-approach. Reason: Observation reloads immediately a module after a properties is set. But when module / bean reloads, no value has been added for that property, so.. NPE or other "uncontrolled" (untested, I would say..) situations.
Another case: try to configure cache config with a domain voter.. add a "pattern" property and then.. ok, done, Magnolia is lost, you have to programmatically delete that property. Stupid workaround: enter BEFORE the value, using a dummy property name, and then change property name to the right value. Solution: we need to test more our code (myself included, of course!!) HTH, Matteo -----Messaggio originale----- Da: [email protected] [mailto:[email protected]] Per conto di Nils Breunese Inviato: martedì 18 agosto 2015 16:12 A: Magnolia User-List <[email protected]> Oggetto: Re: [magnolia-user] Re: Kill your magnolia with 'downloadPath' property Thanks for adding that issue to JIRA. It's probably helpful to also set the affected version field, so Magnolia engineers know what version to check. Nils. > Op 18 aug. 2015, om 14:41 heeft Тимофей Самарский (via Magnolia Forums) > <[email protected]> het volgende geschreven: > > https://jira.magnolia-cms.com/browse/MGNLDAM-614 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
