Advanced search  

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: 403 Forbidden on admin.php  (Read 4744 times)

0 Members and 1 Guest are viewing this topic.

cliffr76

  • Coppermine newbie
  • Offline Offline
  • Posts: 2
    • Naturesview & More Photography
403 Forbidden on admin.php
« on: July 06, 2007, 08:44:32 pm »

I recently upgraded to 1.4.12 from 1.4.10 and am getting permission error on admin.php when I try to change any of the config settings.  I have tried changing the permissions from 644 to 755 and 777 and still get the same error. Before the upgrade I did not have any problems with permission errors.

Cliff

coppermine is located at http://photo.naturesview.ca/
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: 403 Forbidden on admin.php
« Reply #1 on: July 06, 2007, 08:54:43 pm »

Not related to upgrading. Permissions are not being handled by coppermine, but dependant on file-system level.
  • Possible reason: you need to apply permissions (CHMOD) accordingly
  • Your webhost changed something (ask them)
  • You have a .htaccess file in place that causes this
Logged

cliffr76

  • Coppermine newbie
  • Offline Offline
  • Posts: 2
    • Naturesview & More Photography
Re: 403 Forbidden on admin.php
« Reply #2 on: July 06, 2007, 11:46:29 pm »

I realize coppermine does not handle permissions but why before I upgraded was I able to change the config settings and now after upgrading I am not able to...  What should the permissions be set to for the file.

Cliff
Logged

Nibbler

  • Guest
Re: 403 Forbidden on admin.php
« Reply #3 on: July 06, 2007, 11:49:48 pm »

You can access the file, so it's not a permissions issue. Ask your host if they have some security mechanism in place that can cause this.
Logged
Pages: [1]   Go Up
 

Page created in 0.04 seconds with 19 queries.