[#UP-721] All publish groups lost when you try and publish a fragment to a specific user.

uPortal

All publish groups lost when you try and publish a fragment to a specific user.

Created: 27/Oct/04 12:43 PM Updated: 03/Jul/07 04:10 PM

Component/s:

Aggregated Layouts

Affects Version/s:

2.4, 2.4.1, 2.4.2, 2.5.0 M1, 2.5.1 RC1, 2.5.0 RC1, 2.5.0 RC3, 2.5.0 RC2, 2.5.0 GA, 2.5.1 RC2

Fix Version/s:

2.5.2 RC1

Original Estimate:	3 weeks	Remaining Estimate:	3 weeks	Time Spent:	Unknown
File Attachments:	1. UP-721_partial_fix.txt (3 kb)

Bugzilla Id:

1755

Description

« Hide

To reproduce this bug, repeat these actions:

1. Login as Admin
2. Click preferences
3. Click Fragments
4. Edit the publish settings for the news fragment or the entertainment fragment
5. Add the "Demo" user (there should be another group in there ... Developers or Everyone or Students)
6. Click home and save if you want
7. Go back into the publish settings for the fragment you edited and you should see that not only was the Demo user not saved ... but the group stored in there has somehow been deleted.

Cannot explain this one ... but again, a pretty serious bug.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Brad Johnson [26/Jan/06 12:16 PM]

Confirmed this behavior on 2-5-patches.

The NPE happens on the line "memelem.setAttribute("selected","true");" this happens because members[0] is null and the null gets passed around until it is differenced and the NPE happenes.

ERROR [Thread-46] groupsmanager.Utility.[] Jan/26 10:58:19 - java.lang.NullPointerException
java.lang.NullPointerException
at org.jasig.portal.channels.groupsmanager.CGroupsManagerServantFactory.getGroupsServantforSelection(CGroupsManagerServantFactory.java:345)
at org.jasig.portal.channels.groupsmanager.CGroupsManagerServantFactory.getGroupsServantforSelection(CGroupsManagerServantFactory.java:91)
at org.jasig.portal.layout.alm.channels.CFragmentManager.getGroupServant(CFragmentManager.java:108)
at org.jasig.portal.layout.alm.channels.CFragmentManager.analyzeParameters(CFragmentManager.java:205)
at org.jasig.portal.layout.alm.channels.CFragmentManager.renderXML(CFragmentManager.java:255)
at org.jasig.portal.ChannelRenderer$Worker.execute(ChannelRenderer.java:591)
at org.jasig.portal.utils.threading.BaseTask.run(BaseTask.java:27)
at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:431)
at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:166)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:643)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:668)
at java.lang.Thread.run(Thread.java:595)

[ Permlink | « Hide ]

Brad Johnson [26/Jan/06 12:49 PM]

This fix prevents the existing groups from being lost when you try to publish to the Demo user. This doesn't fix the issue of being unable to publish a fragment to the Demo user.

[ Permlink | « Hide ]

Andrew Petro [06/Feb/06 08:59 PM]

Split out the unable to publish fragment aspect of this issue to UP-1412 in order to recognize and apply the partial fix ~~UP-721~~ of preventing existing groups from being lost.

[ Permlink | « Hide ]

Andrew Petro [06/Feb/06 09:04 PM]

Brad Johnson appears to have applied this patch on Jan 31.

[ Permlink | « Hide ]

Andrew Petro [06/Feb/06 09:04 PM]

The losing groups aspect of the issue was addressed by Brad's 1/31/06 commit.