[ http://jira.magnolia.info/browse/MAGNOLIA-1351?page=all ]
Chris Miner reassigned MAGNOLIA-1351:
-------------------------------------
Assignee: Chris Miner (was: Boris Kraft)
> PageMVCServlet broken in a way that disallows forwarding to pages.
> ------------------------------------------------------------------
>
> Key: MAGNOLIA-1351
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1351
> Project: Magnolia
> Issue Type: Bug
> Reporter: Chris Miner
> Assigned To: Chris Miner
> Fix For: 3.0.x
>
> Attachments: patch.txt, stacktrace.txt
>
>
> The page mvc servlet looks for a page name in the forwarding request info.
> Judging from the way the freemarker and jsp servlets are written, probably it
> shouldn't do this. Attached find a patch that permits forwarding to magnolia
> 'pages'.
> Steps to repoduce
> 1. set up a template with a path to a page (for example
> /.magnolia/pages/OfferEditorialCard)
> 2. try to access a path using this template
> You get an error in the log. oddly no exception. but you can set a break
> point
> ERROR info.magnolia.module.admininterface.PageMVCServlet
> PageMVCServlet.java(getHandler:71) 28.06.2007 16:10:22 no page found: []
> then you can see the exception trace. see attachment. After looking at the
> source code for the freemarker and jsp servlets it seems the page name should
> come from the include path and not the forward path. see patch. one could
> debate that only the last term should be taken as the path. I think it is a
> find standard that page names in magnolia have no '/' in them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
