Hi Magnolians, Based on your answer to Gorans question, I would really like to know what the thinking was behind producing an official release without the functionality to create new resources in JCR (and therefore being able to publish them)?
Clearly this completely breaks magnolia's beautiful separation of logic, content and design, and should (if at all) have only been released as a "alpha" or "pre-release" Version, and not an official release. For those of us using magnolia in production it is intensely frustrating that each new release seems to be either missing major functionality that was present before, has completely changed internal formats requiring complicated migrations or is just plain full of bugs... I think you need to look at your release and quality assurance process and find some way of producing "real" releases, separate from the ones you do now, where each "real" release is guaranteed to "just work" out of the box. No migrations, no bug-hunting and no missing features. Frustrated regards from Vienna, Richard > -----Ursprüngliche Nachricht----- > Von: user-list-ow...@magnolia-cms.com > [mailto:user-list-owner@magnolia- cms.com] Im Auftrag von Antti > Hietala (via Magnolia Forums) > Gesendet: Freitag, 30. Oktober 2015 10:52 > An: Magnolia User List > Betreff: [magnolia-user] Re: Problems with STK templates while > upgrading to > 5.4 > > Yes, you can create new templates without deploying. > > Option 1: Wait for Magnolia 5.4.3 > Magnolia 5.4.3 will ship an improved Resources app. You will be able > to create a new JCR resource file directly in the app and publish the > file to public instances. This avoids the need to deploy the Magnolia > webapp or your module. > > Currently this functionality exists in the Templates app but we will > phase out that app. The improved Resources app will have equivalent > functionality and should be considered a replacement. > > JIRA issues: > - Phase out in-place templating app in favor of Resources app > https://jira.magnolia-cms.com/browse/MGNLRES-184 > - Add create and delete actions for resources https://jira.magnolia- > cms.com/browse/MGNLRES-184 > > UI wireframes > - https://wiki.magnolia-cms.com/display/UX/The+Resource+files+app > > Option 2: Git pull files to your production instances Store your > template scripts in a local Git repository. Configure Magnolia to load > resource files from this repository using the magnolia.resource.dir > property. When you add a new file, commit and push it to Git. Then > "git pull" the file to your public instances. This mechanism is really neat > and operates outside of Magnolia. > > Docs: > - What is magnolia.resources.dir https://documentation.magnolia- > cms.com/display/DOCS/Configuration+management#Configurationmanage > ment-Definingproperties > - Example template script path using magnolia.resources.dir > https://documentation.magnolia- > cms.com/display/DOCS/Resources#Resources-2.Filesystem > - Example file-based module structure under magnolia.resources.dir > https://documentation.magnolia-cms.com/display/DOCS/Module+structure > > Watch this video where Atlassian explains how they use the mechanism. > They discuss Magnolia 5.3 where loading resources files from the file > system was not yet available but with 5.4.x it is possible and setting > up the mechanism is even more straightforward today. > https://www.youtube.com/watch?v=tvVRFSvOpSI > > This practice needs to be properly documented but I hope you get the idea. > > --Antti > > -- > Context is everything: http://forum.magnolia- > cms.com/forum/thread.html?threadId=faf63ada-ec7b-4597-a186- > 0dd92869638e > > > ---------------------------------------------------------------- > 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> > ---------------------------------------------------------------- ---------------------------------------------------------------- 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> ----------------------------------------------------------------
