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: chmod back after install?  (Read 2455 times)

0 Members and 1 Guest are viewing this topic.

Avinash

  • Coppermine newbie
  • Offline Offline
  • Posts: 8
chmod back after install?
« on: July 04, 2006, 04:44:02 pm »
Is it necessary to chmod the include dir to it's old settings after installing? right now its 777 for me.
Logged

Sami

  • VIP
  • Coppermine addict
  • ***
  • Offline Offline
  • Gender: Male
  • Posts: 3686
  • BMossavari
    • My Project
Re: chmod back after install?
« Reply #1 on: July 04, 2006, 06:06:49 pm »
no , include should be Writable (777 or 755 with PHPSuExec)
Logged
‍I don't answer to PM with support question
Please post your issue to related board

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: chmod back after install?
« Reply #2 on: July 04, 2006, 06:57:27 pm »
It won't hurt though to put it back to read-only state after successfull install. Only the albums folder (and everything within it) needs to be writable at all times.
If you need additional logs and web-based plugin installs, you'll have to CHMOD the corresponding folders accordingly.
If your server is configured properly, 777 won't hurt. In rare cases (I repeat: improper server setup), it's safer to have the include-folder read-only.
Logged
Pages: [1]   Go Up
« previous next »
 

Page created in 0.016 seconds with 15 queries.