After install 404 After install 404
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

After install 404

Started by jayc57, January 21, 2008, 05:44:07 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

jayc57

I have the following issue when trying to load coppermine
[website not found]

Coppermine install: http://www.republichog.org/gallery
Forum install: http://www.republichog.org/forum
Coppermine version: cpg1.4.14
Forum version: smf 1.1.4

When I go to http://www.republichog.org/gallery/install.php I get a HTTP 404 Not Found

Joachim Müller

Well - all of your pages within the gallery folder are returning a 404, although the folder index is displaying them. Ask your webhost for support - this is not a genuine coppermine problem, but a matter of webserver setup.
You (or rather: your webhost) appear to be using an "exotic" webserver (obviously named "LiteSpeed") - I have no clue wether it fullfills coppermine's minimum requirements.

jayc57

I had Coppermine running fine and upgraded to the latest version.

Joachim Müller

Do as I suggested and ask your webhost for support.
Quote from: jayc57 on January 21, 2008, 08:14:43 PM
I had Coppermine running fine and upgraded to the latest version.
Then this is not related to initial install, but upgrading. Moving accordingly.

Tranz

The gallery is installed so I don't see what the issue is other than install.php showing 404.

Joachim Müller

When I initially went to http://www.republichog.org/gallery/, all that I could see on that page was a list of files that reside in that folder (an index view). Clicking on any of the files there resulted in a 404. This indicated imporper server setup. That's how I found out about the server on that page (because there was a line at the bottom that said "powered by XXX". It appears that the webhost of the thread starter has fixed this. Apparently, jayc57 has just failed to report this issue as "solved" (although he should have done so). As it works now, I'm marking the thread accordingly.

jayc57

You are absolutely right, I should have reported it solve and didn't.  I am very sorry.