Comments

• acrylian Administrator, Developer

  January 2012

  Yes, your permissions are wrong.
• vincent3569 Member, Translator

  January 2012

  hi
  
  the rights are the same as my other sites :
  - setup.php : 644
  - zp-core/setup : 755
  - zp-core/setup/ setup*.* : 644
  
  I never had this problem before
  
  note that on a fresh install, I can access to setup.php file (the setup process begins).
  but I have this message after .htacess files are created by zenphoto (in the root directory of zenphoto and in zp-data).
  
  it realy seems to be an issue during the setup process.
• acrylian Administrator, Developer

  January 2012

  Sorry, I have really no idea and never encountered this. Generally you ftp client should setup the right permissions to access.
  
  MAybe try to lower the permissions while running and later change them back.
• sbillard Member

  January 2012

  does the problem go away if you remove the .htaccess file?
• vincent3569 Member, Translator

  January 2012

  hi
  when I suppress the .htaccess file at the root directory, I can access to setup.php file.
  
  If I do a setup without creation of .htacess, it's OK.
  If I do a setup with creation of .htacess, I have the error message.
• sbillard Member

  January 2012

  Please remove the line
  `IndexIgnore *`
  and see if things work. That line is supposed to prevent browsing the file list, but maybe it is mis-configured on your server.
• vincent3569 Member, Translator

  February 2012

  hi
  without this line, setup process works perfect.
• sbillard Member

  February 2012

  Thanks for the update. But I really do not know why that line should cause any problems. Here is what I have found on it

  The IndexIgnore directive adds to the list of files to hide when listing a directory. File is a file extension, partial filename, wildcard expression or full filename for files to ignore. Multiple IndexIgnore directives add to the list, rather than replacing the list of ignored files. By default, the list contains `.'.
  

  So it should have nothing to do with direct access to a file as with the setup links. Perhaps you can ask your provider for some explaination. This does work correctly on my installation and I have not heard from other testers of a problem. (Of course, few others would be testing 1.4.3 at present.)