"must create config.php and .htaccess" weirdness

logullo
logullo's picture

Joined: 2003-07-19
Posts: 4
Posted: Sat, 2004-05-22 15:34

I have two Galleries on my server. One was running Gallery 1.4.2; it upgraded easily.

My older Gallery, however, was running version 1.4.1, and I've not been able to upgrade.

When I finish config screen three, I am told:
--------------------
2 errors. Details below.

Error: You must create empty file config.php and chmod it 777 before proceeding. See [documentation] for more details.

Error: You must create empty file .htaccess and chmod it 777 before proceeding. See [documentation] for more details.
--------------------

Argh. Yes, I've run 'sh ./configure.sh' prior to this step; my .htaccess and config.php files exist where they've always been.

From the forums I see others having this problem; one case seems to have been solved by deleting all files except for config.php and installing fresh binaries. I tried that and again had the same error. It's as if my config.php file has some sort of cancer.

Ideas? Thanks!

----
Gallery version: Gallery version 1.4.3-pl1
Apache version: Apache/1.3.27 release 10327100
PHP version (don't just say PHP 4, please): PHP Version 4.3.1
Graphics Toolkit:
Operating system: SuSE Linux 8.2 (i586) 2.4.20-4GB
Web browser/version (if applicable):

 
texx

Joined: 2004-02-13
Posts: 6
Posted: Sat, 2004-05-22 18:17

have you tried backing up your php.ini and .htaccess files, then doing the upgrade, then replacing the files after your done? I have no idea if this will work, but it's just my 2 cents.

 
logullo
logullo's picture

Joined: 2003-07-19
Posts: 4
Posted: Sat, 2004-05-22 20:27

Ah-ah! Perhaps a clue... on Step 1 of the Config Wizard, I note that the final test, "Checking to see if you have the latest versions of all gallery files" tells me:

Success: All 0 test files up-to-date.

Indeed! How nice. I went to the "Gallery Diagnostics" page and the "Check versions" module returns similar info: "No files up-to-date."

Hrmm.

My setup is a little odd, so let me describe further. I have two galleries. The Gallery installations are /usr/share/gallery and /usr/share/gallery2. The albums for each instance are in /srv/www/htdocs/gallery and /srv/www/htdocs/gallery2.

I have a "user" apache.conf file with lines

Alias /gallery /usr/share/gallery
Alias /gallery2 /usr/share/gallery2

as well as entries for each like this one:

<Directory /usr/share/gallery>
Options FollowSymLinks
AllowOverride Limit Options FileInfo
</Directory>

So with that background out of the way... it turns out that if I set aside my existing /usr/share/gallery directory, untar a complete fresh set of gallery files to /usr/share/gallery, run configure.sh (which creates config.php and .htaccess files), proceeding with the config steps gives me the same error.

Used to work: now it doesn't. And maddeningly, that gallery2 subdirectory DOES work. Though I see that when I go through its config wizard, though it completes without error, it still tells me that there are "No files up-to-date".

 
maj12

Joined: 2004-06-09
Posts: 2
Posted: Wed, 2004-06-09 20:19

I am experiencing the exact same situation as logullo. Any suggestions? I'm about to deep-six Gallery becasue my website has been down for a month now. I have 2 gallery dirs running different sites.

link:

http://www.maj12.com

 
neomorph

Joined: 2004-07-05
Posts: 5
Posted: Mon, 2004-07-05 17:17

I'm in the same boat, too. I see the same "0 test files" as well.

 
mjc

Joined: 2004-07-06
Posts: 3
Posted: Tue, 2004-07-06 04:13

I had the same problem. I assumed all of my installs were 1.4.2, but one gave me trouble, so I am guessing it was not already 1.4.2. Anyway, here is what I did to fix it:

Copy 1.4.2 over the local files
Upload to site
Configure site normally (it worked)
Leave in config mode (left appropriate chmod settings at 0777 and 0755)
Download changed files from site, overwriting what I had locally

Copy 1.4.3 files over local files (now I am overwriting the "new" files I just downloaded)
Upload to site
Configure site normally

It worked! (as opposed to the .htaccess and config.php error message)

I suppose the morale of the story is get up to 1.4.2 first, then go to 1.4.3?

Regardless, this is what I did, and I think I must have been at 1.4.1 with the problem site.

HTH

 
signe
signe's picture

Joined: 2003-07-27
Posts: 2322
Posted: Tue, 2004-07-06 15:40

The "All 0 files" is a misnomer. That means that all files verified fine.