| View previous topic :: View next topic |
| Author |
Message |
zryznar
-
Joined: 13 Jun 2003
Posts: 5
|
 Posted: Wed Jul 30, 2003 10:52 am Post subject: images .pnp .gif .jpg not displayed in phpMyAdmin |
 |
|
I installed Abyss web server 1.1.6. and all (my web-site, phpMyAdmin,
phpnuke) except that in case of phpMyAdmin and Phpnuke images (.pnp.jpg.gif) are not displaying. The path is o'key, additionally I set alliases
and CGI path for /images etc. It seems that image files are not allowed
for these two applications?
Second question:
How can I set up custom error pages? How to associate new error pages?
Locating in \catalogue or in \CGI?
I will be grateful for any advice
Zygmunt |
|
| Back to top |
   |
 |
aprelium
-
Joined: 22 Mar 2002
Posts: 6800
|
| Posted: Wed Jul 30, 2003 5:42 pm Post subject: Re: images .pnp .gif .jpg not displayed in phpMyAdmin |
|
|
| zryznar wrote: | I installed Abyss web server 1.1.6. and all (my web-site, phpMyAdmin,
phpnuke) except that in case of phpMyAdmin and Phpnuke images (.pnp.jpg.gif) are not displaying. The path is o'key, additionally I set alliases
and CGI path for /images etc. It seems that image files are not allowed
for these two applications?
|
We are still waiting for more information to be sent to support@aprelium.com as described in our reply.
| zryznar wrote: |
Second question:
How can I set up custom error pages? How to associate new error pages?
Locating in \catalogue or in \CGI?
|
You should use "Custom Error" pages in the console and associate an error code (usually 404 for "Not found") with a HTML page or a CGI script on your web site. If your script/HTML page is viewable using the URL http://yoursite/path/to/page.ext , you should associate the error code with the virtual path /path/to/page.ext .
_________________
Support Team
Aprelium - http://www.aprelium.com |
|
| Back to top |
|
|
zryznar
-
Joined: 13 Jun 2003
Posts: 5
|
| Posted: Wed Jul 30, 2003 9:36 pm Post subject: : Re: images .pnp .gif .jpg not displayed in phpMyAdmin |
|
|
After setting CGI parameter "Resolve interpreter using Windows registry" to "No" this problem disapears.
Zygmunt |
|
| Back to top |
|
|
|
