Any consideration to allow Error pages (400,401, 402, etc) to be handled/editable from within SiteWorx?
Absolutely, on ‘the list’ :).
I know you guys will eventually add the possibility of specifying custom error pages from within SiteWorx, but until then where do I specify it?
I am NOT looking for an overall setting for all my accounts, as some sites (customers), do not need custom error pages.
So what I am looking for is the file, specific for each account(site) where I can edit and specify the custom error pages.
I sure look forward to these much needed features will be added, so I can spend some time developing my own sites, instead of messing with customizing user accounts.
Also maybe it would be helpful to us InterWorx users, if you guys would post a list of features and estimated dates, of what’s cooking.
This is actually really easy.
Put the following at the very end of the /etc/httpd/conf/httpd.conf
ErrorDocument 401 /401.html
ErrorDocument 403 /403.html
ErrorDocument 404 /404.html
ErrorDocument 500 /500.html
Restart the apache webserver, via NodeWorx or at the command line:
service httpd restart
- Create the error files in the users web space. For example, if you create a 404.html in the user’s html directory, 404 errors will show this page.
thanks for your fast reply, however I already knew that.
But is that not for ALL the accounts(sites)?
I was hoping that custom error pages could be specified individually for each site, as I wrote some of my customers don’t need custom error pages.
No, that is not for all accounts. You can have a different 404.html for each site.
Doing it that way, you could have
and it will show the correct 404 page for the correct domain. If there is no 404.html file a generic 404 error will be displayed.
Ok now I a bit confused, because the following is already in the config file:
Customizable error responses come in three flavors:
1) plain text 2) local redirects 3) external redirects
#ErrorDocument 500 “The server made a boo boo.”
#ErrorDocument 404 /missing.html
#ErrorDocument 404 “/cgi-bin/missing_handler.pl”
#ErrorDocument 402 http://www.example.com/subscription_info.html
Putting this all together, we can Internationalize error responses.
We use Alias to redirect any /error/HTTP_<error>.html.var response to
our collection of by-error message multi-language collections. We use
includes to substitute the appropriate text.
You can modify the messages’ appearance without changing any of the
default HTTP_<error>.html.var files by adding the line;
Alias /error/include/ “/your/include/path/”
which allows you to create your own set of files by starting with the
/var/www/error/include/ files and
copying them to /your/include/path/, even on a per-VirtualHost basis.
Alias /error/ “/var/www/error/”
AddOutputFilter Includes html
AddHandler type-map var
Allow from all
LanguagePriority en es de fr
ForceLanguagePriority Prefer Fallback
ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var ErrorDocument 410 /error/HTTP_GONE.html.var ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var ErrorDocument 415 /error/HTTP_SERVICE_UNAVAILABLE.html.var ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var
So my question is, do I leave that as is, edit it or delete it?
Also you wrote do this:
Don’t you mean do this:
ErrorDocument 404 /home/XXXXX/domain1.com/html/404.html
ErrorDocument 404 /home/YYYYY/differentdomain.com/html/404.html
To many possibilities for me to screw up, can you please be more specific.
I was specific the first time RWF
Just do exactly as I said in steps 1, 2, and 3, and it should work as I described.
Oh, I see the confusion now.
You though I was talking about the actual error file, example 404.htm. Well of course I know that can be made by the site owner, and uploaded to his site.
What I was actually talking about, was can I somewhere specify which file to look for, for each site that is?
So for example:
Site 1 looks for 404.htm
Site 2 looks for 404.shtml
Site 3 look for index.htm
Site 4 not specified, so it now looks for the default 404.htm
You get me know?
I see what you’re saying now.
To do this you create a .htaccess file in the user’s html directory, with one of the following lines, if you only wanted to override 404 errors.
ErrorDocument 404 /404.php
ErrorDocument 404 /404.shtml
ErrorDocument 404 /index.htm
Any update to when Custom ERROR pages will be made aviable through SiteWorx?
We have no hard release date for the error page feature but I suspect it will make it into the 2.2 release r-n-r. That said I’m honestly not sure and it could slip depending on the 2.2 priorities.
Thanks fo rthe info Chris, buy the way is there a “Road Map” of new features for future releases posted any where?
There isn’t, for 2 reasons:
Our focus changes as clients suggest things so priorities don’t always stay the same. You can get a feel from reading the forums what’s coming in general by the feedback and our comments.
We don’t want to give any competitors juicy info