[#UP-1619] Content Subscriber channel does not display available pulled fragments for a group unless at least one pushed fragment is published to the group

uPortal

Content Subscriber channel does not display available pulled fragments for a group unless at least one pushed fragment is published to the group

Created: 07/Dec/06 06:54 PM Updated: 03/Jul/07 04:14 PM

Component/s:

Aggregated Layouts

Affects Version/s:

2.5.1 RC1, 2.5.1 RC2, 2.5.2 RC1, 2.5.1 RC3, 2.5.1 GA, 2.5.3 RC1, 2.5.2 GA, 2.5.3 RC2, 2.5.3 RC3, 2.5.3 GA

Fix Version/s:

2.6.0 M1, 2.5.4

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Environment:

« Hide

uPortal 2-5-patches
Tomcat 5.5.20
JDK 1.5.0_09

Issue Links:

Block

This issue is blocked by:
	~~UP-1421~~ CContentSubscriber does not display a...

Description

« Hide

The Content Subscriber channel does not display available pulled fragments for a group unless at least one pushed fragment is published to the group.

Steps to reproduce:
1. Create a new group 'TestGroup' under Everyone.
2. Create a new user 'testuser'
3. Login as 'testuser', then logout.
4. Login as the Admin user and assign 'testuser' only to the group 'TestGroup' (Remove any other group memberships such as Developers)
5. Create a pulled fragment named 'TestPulledFragment' with any content.
6. Publish 'TestPulledFragment' to the 'TestGroup' group.
7. Login as 'testuser' and navigate to the Content Subscriber channel (Preferences -> Add Content). The 'Fragments' category will be empty, even though 'TestPulledFragment' should be listed.
8. Login as the Admin user and create a pushed fragment named 'TestPushedFragment' with any content.
9. Publish 'TestPushedFragment' to the 'TestGroup' group.
10. Login as 'testuser' and navigate to the Content Subscriber channel. The 'TestPulledFragment' fragment will now be listed in the Fragments category.
Note - If you delete the 'TestPushedFragment' or stop publishing it to the 'TestGroup' group, then the 'TestPulledFragment' will no longer show up in the Fragments category.

All

Comments

Work Log

Change History

FishEye

Sort Order:

[ Permlink | « Hide ]

Brad Szabo [07/Dec/06 07:08 PM]

The patch attached to ~~UP-1421~~ is required for the fragments to be displayed at all, even when a pushed fragment is published to the group.

[ Permlink | « Hide ]

Brad Szabo [07/Dec/06 08:22 PM]

In AggregatedUserLayoutStore, when pushFragmentIds was null, the user's fragment query was unioned with an unconstrained fragment query. This resulted in all fragments being included in the user's layoutData. When the Content Subscriber
channel obtains the list of subscribable pulled fragments, it removes any that are already in the user's layout. Since all pulled fragments appeared to be in the layout, they were all removed from the list of those available, and therefore none were showing up for subscription.

Fixed this to only include the union statement if pushFragmentIds exist to constrain it.