[ http://issues.apache.org/jira/browse/JS2-506?page=all ]
Randy Watler resolved JS2-506:
------------------------------
Fix Version: 2.1-dev
Resolution: Fixed
This has been implemented in the portal-site component as per request.
Additionally, historical pages per folder are reset in the fallback folders to
make the default behavior more predictable in this case. Note: all fallback can
be disabled in the Spring configuration for the profiler valve,
(assembly/pipelines.xml).
> Extend profiler to fallback to parent folders when requested path is not
> available.
> -----------------------------------------------------------------------------------
>
> Key: JS2-506
> URL: http://issues.apache.org/jira/browse/JS2-506
> Project: Jetspeed 2
> Type: Improvement
> Components: Profiling/Portal Navigation
> Versions: 2.0-FINAL
> Reporter: Ethan Adams
> Assignee: Randy Watler
> Priority: Minor
> Fix For: 2.1-dev
>
> It would be helpful to have the profiler fallback to the parent folder of the
> requested path if it is no longer accessible.
> Ex:
> A user navigates to /a/b/c/123.psml. The user logs in and is redirected back
> to to /a/b/c/123.psml. However, the logged in user no longer has access to
> /a/b/c/123.psml. In the current 2.0-FINAL, an exception would be thrown
> ("org.apache.jetspeed.page.document.NodeNotFoundException: No page matched /
> request in site view."). Ideally, the profiler would try to fallback to the
> parent nodes (and its parents if necessary) default page. So it would try
> /a/b/c, then /a/b, etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
