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

Re-enable a user-interface for processed resources

    XMLWordPrintable

Details

    • Story
    • Resolution: Fixed
    • Critical
    • 2.4.3
    • 2.4.1
    • app
    • None
    • Basel 20
    • 5

    Description

      Remove the legacy resources app from the resources module. Create a new module which contains everything needed for the old resources app which supports the processed resources UX (the bootstrap files, i18n files, version handler, etc.)
      In this way - those who require the UX to work with processed resources will make the conscious decision to add the app to their project, while those that do not will not be confused by an overlapping interface.
      ("magnolia-processed-resources" "magnolia-resources-app-legacy"?)

      Somewhere in the legacy app the following information should be displayed, since the working of this app are contrary to the documentation of resources. (Possibly in the description (or a static field) of the edit dialog.)

      • Resources are only processed when accessed via the /resources path.
      • Only resources stored in JCR are processed.
      • The bypass flag causes resources to be loaded from the classpath, but not the filesystem.

      Context:
      With 5.4 we created a new Resources app. The new app does not have features that were used for working with processed resources:

      • Ability to set a model
      • Ability to set a type
      • Ability to nest resources (for resource concatenation).
        However the mechanism to actually process the resources is still working and is performed on resources accessed through the /resources path.

      As the new resources servlet does not yet handle resource processing, and resource processing is not yet supported on all origin types (like filesystem, classpath) - the UX should be separated from the normal resources app. We provide the UX specified in this ticket for those who are using the feature on existing projects - or those that explicitly want to use this feature, even with its limitations as compared to the /.resources servlet.

      Providing this app as an available add-on, makes 5.4 already compatible with 5.3 projects with no migration. In the future we plan to enable a similar resource processing on resources served from any origin via the /.resources servlet. https://jira.magnolia-cms.com/browse/MGNLRES-149

      UPD:
      As the linked concept suggests - the new module for the app is going to be created on Forge.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                apchelintcev Aleksandr Pchelintcev
                czimmermann Christopher Zimmermann
                Nucleus
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD

                    Time Tracking

                      Estimated:
                      Original Estimate - Not Specified
                      Not Specified
                      Remaining:
                      Remaining Estimate - 0d
                      0d
                      Logged:
                      Time Spent - 3d 1h
                      3d 1h