History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: TORO-11
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Andrew Petro
Reporter: Andrew Petro
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Toro

Intermittently, users exclusively receiving ALM managed fragments cannot log in

Created: 08/Aug/07 06:00 PM   Updated: 08/Aug/07 06:02 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Duplicate
This issue duplicates:
UP-1791 Intermittent infinite redirect for us... Critical Closed
 


 Description  « Hide
Steps to reproduce:
1) Use ALM
2) Create a template user with no personal layout content
3) As an administrator, create one or more ALM managed fragments and publish them exclusively to PAGS groups (using local groups will not replicate this issue)
4) Log in for the first time as a user who will receive the template user with no layout and one more more of the ALM managed fragments
5) Experience the problem, sometimes after logging out and back in again a few times: it goes into an infinite redirect to this url: /portal/tag.44e240ab4d9a4dcb.render.userLayoutRootNode.uP?uP_request_add_targets=folder&uP_add_target=folder&NextID=&targetParentID=&uP_sparam=mode&mode=view&uP_sparam=focusedTabID&focusedTabID=&uP_sparam=targetRestriction&targetRestriction=column&uP_sparam=targetAction&targetAction=New%20Column&uP_cancel_targets=true&uP_sparam=newNodeID&newNodeID=

Expected behavior:
Expected to experience the ALM managed fragments published to the user with no layout contribution from personal layout content (i.e., no layout contribution from the template layout).

 All   Comments   Work Log   Change History   FishEye      Sort Order:
Andrew Petro [08/Aug/07 06:02 PM]
TORO-11 documents an issue discovered in Academus 2.1, the closed-source precursor to the code that is Toro. It is believed but not yet demonstrated that this issue afflicts uPortal itself, hence UP-1791.