Print

[xbritney]

Hello, I've bought a domain for my friend bc its his b-day he is going to be 16 and i want to suprise him with a new gallery and domain http://slippingunder.com/ as of now it looks like an IE 404 page (the index)

Now the problem is this http://slippingunder.com/index.php  http://slippingunder.com/login.php both of those pages are empty and i've took it out, made a new database and resinstalled it and its not working any help would be great!

[Joachim Müller]

1) http://slippingunder.com/index.php looks as expected
2) create a redirection file named index.htm or (even better) add index.php to the list of index files using the .htaccess method. If you have no idea how to do this, ask your webhsot for support. Not a coppermine issue.

[Knightmare]

I am having a similar problem with the all white pages.  I have installed all the files and run the installer (sucessfully according to it).  It then sent me to the admin log-in page, which is all white as is the main index page.  My files for this should be in the public_html folder correct?

http://www.ca-painting.com/photos/login.php
http://www.ca-painting.com/photos/index.php

Please advise.

Thank you.

[blurn]

I am also haveing the same error. I can tell you that I have used CPG before and never had a problem like this. It is very strange indeed... Some details about the server I have built...

Web Server: Apache 2.2.2 (Unix)
MySQL: 5.0.22-standard
PHP: 5.1.4 (necessary extensions for GD are installed)

I have tried the .htaccess fix that the administrator said would help. It didn't. I am also having this problem when trying to parse drupal or some other scripts on another domain I am hosting. It is strange, I couldn't view my php info with the script

Code: [Select]

<? phpinfo(); ?> but I am able to view it with

Code: [Select]

<?php phpinfo(); ?>... Even stranger the install.php file worked and said that the install was succesful. I checked the database I installed CPG on and it created the tables and data without issue.

Also, Wordpress works perfectly on some other domains.... Could it possibly be an issue with PHP5?

[Joachim Müller]

http://www.php.net/manual/en/ini.core.php#ini.short-open-tag

[blurn]

http://www.php.net/manual/en/ini.core.php#ini.short-open-tag

Your fix in particular did not fix the issue completly. It fixed the problem with the <? and the <?php tags. GauGau, however, your insane smartness led me to disabling my php.ini temporarily to see if that is where the problem resided. It is definitely that file. When I compilied php I was using the recommended PHP.INI dist file. For anyone else that has access to the the php.ini file, make sure that all of the settings in this file will work with CPG or whatever software you are trying to use. I also recommend starting from the ground up and making your own php.ini file to the guidelines stated by PHP that will ultimately fit your needs.

I am going to try the recommended PHP.ini file to see if that helps, because I need the php.ini file to set settings like max upload size and max post size. There might be a way to make a file that leaves all settings at default except the directives needed? Thanks again GauGau!

EDIT:

Using the php.ini file that is distrubuted with PHP seems to have worked. The file in the distro I used is called php.ini-dist. The file that caused all of these issues was in fact, ironically, the php.ini-recommended file... Hopefully this will help the people out that have made their own servers.

[Joachim Müller]

The recommended method is not to install/compile your own flavour of PHP, but use a pre-made package. Those packages usually come with default settings that make sense for most setups. Gradually changing some of the settings to make your server perform better with your apps (like coppermine) is a process, not a single effort. There is no such thing as a default php.ini file that works for all environments and needs. As a rule of thumb, you should only change some settings at a time that you're aware of what they do, then test thoroughly to find out about the impacts. Running your own webserver is not a trivial task, that's why self-hosting is not recommended. It takes a lot of skills and practice to set up and maintain a webserver of your own. Although I'm a full time network admin by profession and I'm in charge of running several servers on the corporate network (including an intranet webserver), I wouldn't dare to run a webserver at home that is available for the public.