OFBiz › OFBiz - Dev

[jira] Created: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

21 messages Options

Nicolas Malin (Jira)

[jira] Created: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

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

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.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

> 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.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.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764426#action_12764426 ]

Bruno Busco commented on OFBIZ-3022:
------------------------------------

Hi Patrick,
could you please update the patch?
It generates some conflict if applied to the latest trunk.

Thank you.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764443#action_12764443 ]

Bruno Busco commented on OFBIZ-3022:
------------------------------------

Patrick,
I applied the patch but I am not able to see any new content.
Could you please give some information on how to test 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.

Patrick Antivackis

Re: [jira] Commented: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

Bruno,
I defined error pages for CmsSite in CmsSiteDemoData.xml
So if you go to https://localhost:8443/cmssite/cms/CMSS_DEMO_PAGE15 (do not
exist), you should get the content defined by contentId="CMSS_ERROR_404" as
it is a TREE_CHILD mapped with key 404 from CMSS_ERROR_ROOT that is an
ERROR_ROOT type.
If you drop the CMSS_ERROR_404 association with CMSS_ERROR_ROOT and reload
the page you you get the content defined by CMSS_ERROR_ROOT.
For both you can also see that the HTTP status code sent back by ofbiz is
404.
If you make obsolete the content CMSS_DEMO_PAGE1 (giving a thruDate that is
overdue already), and load
https://localhost:8443/cmssite/cms/CMSS_DEMO_PAGE1 you shoudl get a HTTP
status code 410 (page is gone) and the content of CMSS_ERROR_ROOT as i
didn't defined a specific 410 error page for CmsSite.

If you drop CMSS_ERROR_ROOT in the WebSiteContent entity, and reload you
should get the global catch all 410 or 404 page that are defined in
ContentHttpErrorData.xml file.

2009/10/11 Bruno Busco (JIRA) <[hidden email]>

>
> [
> https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764443#action_12764443]
>
> Bruno Busco commented on OFBIZ-3022:
> ------------------------------------
>
> Patrick,
> I applied the patch but I am not able to see any new content.
> Could you please give some information on how to test 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.
>
>

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764448#action_12764448 ]

Patrick Antivackis commented on OFBIZ-3022:
-------------------------------------------

Bruno,
I defined error pages for CmsSite in CmsSiteDemoData.xml
So if you go to https://localhost:8443/cmssite/cms/CMSS_DEMO_PAGE15 (do not exist), you should get the content defined by contentId="CMSS_ERROR_404" as it is a TREE_CHILD mapped with key 404 from CMSS_ERROR_ROOT that is an ERROR_ROOT type.
If you drop the CMSS_ERROR_404 association with CMSS_ERROR_ROOT and reload the page you get the content defined by CMSS_ERROR_ROOT.
For both you can also see that the HTTP status code sent back by ofbiz is 404.
If you make obsolete the content CMSS_DEMO_PAGE1 (giving a thruDate that is overdue already), and load https://localhost:8443/cmssite/cms/CMSS_DEMO_PAGE1 you shoudl get a HTTP status code 410 (page is gone) and the content of CMSS_ERROR_ROOT as i didn't defined a specific 410 error page for CmsSite.

If you drop CMSS_ERROR_ROOT in the WebSiteContent entity, and reload you should get the global catch all 410 or 404 page that are defined in ContentHttpErrorData.xml file.

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764452#action_12764452 ]

Bruno Busco commented on OFBIZ-3022:
------------------------------------

Thank you Patrick,
it works as you specified.

Do you think it would help to have an error section in the content three here?: https://localhost:8443/content/control/navigateContent

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

[ 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764463#action_12764463 ]

Bruno Busco commented on OFBIZ-3022:
------------------------------------

Well,
to be sincere I am not well used to the content application. I am starting using it now that we have help pages there.
I think that having the high level catch-all Error pages here https://localhost:8443/content/control/navigateContent could be usefull.

In https://localhost:8443/content/control/WebSiteCms?webSiteId=CmsSite we will have the site specific error pages.

> 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.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Antivackis updated OFBIZ-3022:
--------------------------------------

Attachment: ContentHttpErrorData.xml

Here is the new applications/content/data/ContentHttpErrorData.xml file that declares the pages as SUB_CONTENT of CONTENT_ERROR that is itself a TREE_CHILD of TREE_ROOT.
Like this they apear in the :
https://localhost:8443/content/control/navigateContent

page

> 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: ContentHttpErrorData.xml, 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.

Nicolas Malin (Jira)

[jira] Assigned: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Busco reassigned OFBIZ-3022:
----------------------------------

Assignee: Bruno Busco

> 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
> Assignee: Bruno Busco
> Attachments: ContentHttpErrorData.xml, 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766269#action_12766269 ]

Bruno Busco commented on OFBIZ-3022:
------------------------------------

Patrick,
I get an error when trying to look at the HTML of the data resource here:
https://localhost:8443/content/control/EditHtmlText?dataResourceId=CONTENT_ERROR_403

could you please check if this is related to your patch?

The error is:
Expression statusCode is undefined on line 1, column 131 in Thu Oct 15 23:30:34 CEST 2009. The problematic instruction: ---------- ==> ${statusCode} [on line 1, column 129 in Thu Oct 15 23:30:34 CEST 2009] in user-directive renderTextareaField [on line 1, column 1 in Thu Oct 15 23:30:34 CEST 2009] ---------- Java backtrace for programmers: ---------- freemarker.core.InvalidReferenceException: Expression statusCode is undefined on line 1, column 131 in Thu Oct 15 23:30:34 CEST 2009. at freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:124) at freemarker.core.Expression.getStringValue(Expression.java:118) at freemarker.core.Expression.getStringValue(Expression.java:93) at freemarker.core.DollarVariable.accept(DollarVariable.java:76) at freemarker.core.Environment.visit(Environment.java:209) at freemarker.core.MixedContent.accept(MixedContent.java:92) at freemarker.core.Environment.visit(Environment.java:209) at freemarker.core.Environment.renderElementToString(Environment.java:1568) at freemarker.core.StringLiteral.getStringValue(StringLiteral.java:101) at freemarker.core.StringLiteral._getAsTemplateModel(StringLiteral.java:86) at freemarker.core.Expression.getAsTemplateModel(Expression.java:89) at freemark...................

> 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
> Assignee: Bruno Busco
> Attachments: ContentHttpErrorData.xml, 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766464#action_12766464 ]

Patrick Antivackis commented on OFBIZ-3022:
-------------------------------------------

Bruno,
No not by my patch but the seed, as the editHtml try to render the page. As the ${statusCode} doesn't exist in this context, everything is breaking.
If you usr EditElectronicText instead of EditHtmlText and change ${statusCode} by ${statusCode?if_exists} everything would be OK.

May be i should put the if_exists claude in all the seed datas in order to keep it safe

> 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
> Assignee: Bruno Busco
> Attachments: ContentHttpErrorData.xml, 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.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Antivackis updated OFBIZ-3022:
--------------------------------------

Attachment: ContentHttpErrorData.xml

Solving the issues when editing the ERROR_ dataresources in the HTMLEditor.
Added ?if_exists in all the ${statusCode}

> 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
> Assignee: Bruno Busco
> Attachments: ContentHttpErrorData.xml, 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.

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-3022) Addind Error Pages (404 - 410) possibilities for the Content app

In reply to this post by Nicolas Malin (Jira)

> 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
> Assignee: Bruno Busco
> Attachments: ContentHttpErrorData.xml, 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.