[
https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764455#action_12764455
]
Patrick Antivackis commented on OFBIZ-3022:
-------------------------------------------
I more intend to complete the fonctionalities on :
https://localhost:8443/content/control/WebSiteCms?webSiteId=CmsSite
both for menu (that have never worked) and error.
But may be it could be interesting to add an error section in the link you
specified for at least the high level catch-all Error pages.
I do it ?
> Addind Error Pages (404 - 410) possibilities for the Content app
> ----------------------------------------------------------------
>
> Key: OFBIZ-3022
> URL: https://issues.apache.org/jira/browse/OFBIZ-3022
> Project: OFBiz
> Issue Type: Improvement
> Components: content
> Affects Versions: SVN trunk
> Reporter: Patrick Antivackis
> Attachments: Patch-OFBIZ-3022-824037.txt, Patch-OFBIZ-3022.txt
>
>
> The idea is to allow CMS based sites to have 404 not found, 410 page is gone
> and 403 Forbidden pages (not yet used).
> For this I first create global error pages in Data Resources/Content (id =
> CONTENT_ERROR_xxx). These pages will be catchall Error pages if nothing is
> defined at the Website Level (see below). Of course, theses pages can be
> localized through the ContentAssoc ALTERNATE_LOCALE type (see the seed file
> for example).
> Then I added a ERROR_ROOT type in the WebSiteContentType entity.
> The Document declared as ERROR_ROOT for a CMS Website will become an Error
> catch-all page for this site.
> Under this root, specific error pages (404, 410) can be added (just one
> sublevel) in order to have a specific page per error code (status code =
> mapKey)
> These documents can of course be localized too.
> I then updated the CmsEvent class in order to find a corresponding error page
> (first look at the subcontent of ERROR_ROOT, or take ERROR_ROOT or take the
> global CONTENT_ERROR page). Now the rendered content also received the status
> code in its context, so a $[statusContent} in a ftl template can show the
> statusCode (200/404/410)
> Also updated the WebSiteCMSNav.ftl and WebSitePublishPoint.groovy in order to
> show error tree (and may be manage the pages later)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
