If I may add, we're not going to remove support for processed resources until we have a good alternative/replacement for it. So this is still supported, yet not encouraged for new projects.
Instead, we'll be favoring a new mechanism (maybe at resource servlet level), to support e.g. post-processing (Sass), minification, site-awareness. The intention is to benefit all resources (not only JCR) and eventually offer more flexibility than just freemarker rendering. Meanwhile, you may want to add the "resources-legacy" app to the applauncher config. In particular for those resources as subnodes. - Mind that the translations are mostly gone at present - Rename resources-legacy/subApps/browser/actions/editResource@appName to 'resources-legacy' Cheers, Mika -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=75f45a9e-fc23-451e-8c3f-4d89a0183dc8 ---------------------------------------------------------------- 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: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------