Uploaded image for project: 'Magnolia Resources Module'
  1. Magnolia Resources Module
  2. MGNLRES-208

Support author vs public resources

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Won't Do
    • Neutral
    • None
    • 2.4.1
    • resourceLoaders

    Description

      As reported in SUPPORT-5053 in Magnolia 5.3 we have different JCR-based configurations per Magnolia instance (author vs public). I think this quite a typical use case because often in our projects we have different configurations per Magnolia instance, not all of which we want to explicitly program in Java code in our version handlers.

      So therefore I think it would be nice if Magnolia would support 'instance-based configurations' for YAML-based configuration/resources so that when moving all to YAML at some time in the future this is also still possible.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              sang.ngo Sang Ngo Huu
              edgar Edgar Vonk
              Nucleus
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - Not Specified
                    Not Specified
                    Logged:
                    Time Spent - 0.25d
                    0.25d