With the new version 5.2 for Magnolia i noticed that also for the configuration 
app some kind of activation flow is used when deleting nodes/properties.

This really slows down creating/updating component by configuration as i now 
need a public instance running (i normally use just an author instance just for 
simplicity).

Is it possible to override this activation flow for the configuration app (like 
providing some kind of development mode)?

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=7af0abb6-e6b3-47c4-9218-6fb58953dbf3


----------------------------------------------------------------
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]>
----------------------------------------------------------------

Reply via email to