[MGNLRES-237] Re-enable a user-interface for processed resources Created: 19/Oct/15  Updated: 29/Mar/22  Resolved: 17/Nov/15

Status: Closed
Project: Magnolia Resources Module
Component/s: app
Affects Version/s: 2.4.1
Fix Version/s: 2.4.3

Type: Story Priority: Critical
Reporter: Christopher Zimmermann Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3d 1h
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLRES-149 Concept for supporting processing res... Closed
causality
dependency
depends upon MGNLRES-239 Make "legacy resources" app work again Closed
relation
supersession
supersedes MGNLRES-233 Users should have a way to enable/dis... Closed
is superseded by PROCRES-1 Port the app codebase and resources f... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Sprint: Basel 20
Story Points: 5
Team: Nucleus

 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.


Generated at Mon Feb 12 06:48:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.