[MGNLCDEP-81] Show content dependencies from action in browser app Created: 29/Apr/15  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Content Dependencies
Component/s: None
Affects Version/s: 1.4.2
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Frank Sommer Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Date of First Response:

 Description   

It is awkward to open first the page in edit mode and then open the page properties dialog, before I can see the content dependencies of this page. It would be nice if Magnolia could provide the list of the content dependencies by an action of the pages browser sub app.



 Comments   
Comment by OLD Chris Jennings (Malleus) (Inactive) [ 28/Feb/16 ]

Hi Frank.
I have recently been thinking about the same issue and have built a fix.
I need to speak to someone about integrating with an enterprise module but if you are interested in using it straight away, it is available here:

https://github.com/malleusconsulting/extended-dependencies/tree/extended-dependencies-module-1.0

I need to write documentation ASAP but it uses the Dependencies module (so no need to reconfigure anything) and adds new actions to Pages and DAM-App. This gives you an instant dialog with your dependencies shown.

I have only tested it on the latest Magnolia releases. If you need to change this, would you please let me know which versions you have used? I will then update it.

Please let me know of any questions/problems,

Chris.

Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 00:12:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.