[MGNLRSSAGG-18] Activation in RssTree does not activate subnodes Created: 23/Jun/09  Updated: 09/Feb/15  Resolved: 09/Jul/09

Status: Closed
Project: Magnolia RSS Aggregator Module
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.0.1

Type: Bug Priority: Major
Reporter: Sebastian Frick Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

mgnl 4.0, data 1.3,


Attachments: Text File RssAggregatorTree.java     Text File RssAggregatorTreeConfig.java    
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When activating a Rss Aggregator via the data module RSS-Tree,
none of the subnodes will be activated. Thus all feeds and filters are
missing on the publish instance.

Workaround: Activate the rss aggregators with the jcr browser

The issue is caused by the data structure RSSAggregator uses. It's a
bug. Please report it in Jira.
Thanks,
Jan



 Comments   
Comment by wolf bubenik [ 23/Jun/09 ]

A simple Patch:

  • a RssAggregatorTree using a specialized TreeConfig that provides a recursive activate command
  • The Tree class must be set as class for the RssAggregator tree in the data module: modules.data.trees.RssAggregator.class=info.magnolia.module.rssaggregator.trees.RssAggregatorTree

We choose to change the behaviour of the activate command instead of adding the activateInclSubs command to the rss tree item because in this tree the subnotes are hidden from the users.

Comment by Jan Haderka [ 09/Jul/09 ]

Changed sub nodes types to dataItemNode. Also added update task to change existing feeds automatically.
Done as of r26717.

Generated at Mon Feb 12 07:04:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.