If an end-user gets a 404 error, can we customize what is displayed to them?
This answer applies to Customer Portal page sets
There are two possible 404 error pages that may be displayed when a user attempts to load an invalid URL in Customer Portal. Which page is displayed to the user is dependent upon the URL path that the user has attempted to load. Both of these 404 error pages can be customized via WebDAV.
URLs in the /app directory:
This applies to users who attempt to navigate to non-existing pages within the /app directory, for example http://mysite.custhelp.com/app/fakepage. The error message displayed to these users can be customized by editing the error404.php file found via WebDAV at the following location:
Customer Portal Framework Version 3.x: /cp/customer/development/views/pages/error404.php
Customer Portal Framework Version 2: /euf/development/views/pages/error404.php
This page may be edited and uploaded via WebDAV. As with other Customer Portal pages, It must be staged and promoted to production before it will be available to your end users in the production environment.
URLs outside of the /app directory:
This applies to users who attempt to navigate to non-existing pages outside of the /app directory, for example http://mysite.custhelp.com/fakepage. Although this URL is technically on your end user pages, it is outside of the Customer Portal framework and thus a different process must be followed to customize the 404 error page.
The error message displayed to these users can be customized by editing the error404.php file found via WebDAV at the following location:
Customer Portal Framework Version 3.x: /cp/customer/error/error404.html
Customer Portal Framework Version 2: /euf/config/error404.html
This page is editable and may be accessed/uploaded via WebDAV. Note that changes to this page take effect in your production environment immediately, as this page exists outside of the Customer Portal framework. There is no stage/deployment process for this page.
Error pages can't use template or widgets or any other rn: type tags on them. These are more like code snippets that are included when a PHP error is encountered. So, if you have some code on the page that is runtime-invalid PHP, we'll include the error_php.php file to display the error. You can use PHP on them, but we don't parse them for CP tags.
Are you experiencing issues with error pages in Internet Explorer? Refer to Answer ID 6417: Custom Error Pages not displaying in Internet Explorer.