Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-98249

As a portal/site admin I want to configure different 404 URLs per instance, and if possible, per site

    Details

      Description

      It could be nice to have the possibility of configure different behavior per site about 404 errors; currently only it is possible to have an unique configuration per all the sites and companies via the next properties:

       

          #
          # Set this to true if the portal should show HTTP status codes like 404 if
          # the requested page is not found.
          #
          # Env: LIFERAY_LAYOUT_PERIOD_SHOW_PERIOD_HTTP_PERIOD_STATUS
          #
      
          layout.show.http.status=true
          #
          # Redirect to this resource if the user requested a site friendly URL that
          # does not exist. Leave it blank to display nothing.
          #
          # A similar configuration for pages is managed with the property
          # "layout.friendly.url.page.not.found".
          #
          # Env: LIFERAY_SITES_PERIOD_FRIENDLY_PERIOD_URL_PERIOD_PAGE_PERIOD_NOT_PERIOD_FOUND
          #
          #sites.friendly.url.page.not.found=/html/portal/404.html
      
      #
      # Redirect to this resource if the user requested a friendly URL of a page
      # that does not exist. Leave it blank to display nothing.
      #
      # A similar configuration for sites is managed with the property
      # "sites.friendly.url.page.not.found".
      #
      # Note: For backward compatibility, this overrides the property
      # "layout.show.http.status" for the 404 status code.
      #
      # Env: LIFERAY_LAYOUT_PERIOD_FRIENDLY_PERIOD_URL_PERIOD_PAGE_PERIOD_NOT_PERIOD_FOUND
      #layout.friendly.url.page.not.found=/html/portal/404.html
      

      This will give value to our customers as they could manage the not-found responses/behaviour directly with minimal (or without the) intervention of other departments like IT (overwriting the 404 errors in the web servers because currently it is not possible to have a different 404 page per site)

      Also, we should allow to configure directly site pages in order to take advantage of multilingual friendly URLs .

      A global/default configuration like the currently existent could be maintained in case the site does not have configured its specific 404 page/behavior.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              support-lep@liferay.com SE Support
              Reporter:
              jose.jimenez Jose Jimenez
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:

                  Packages

                  Version Package