This is because your webserver doesn't allow you to use certain .htaccess overrides. The Gallery setup script tries to set some PHP settings, but this requires you to set AllowOverride Options FileInfo or disable the overrides. If you have access to your httpd.conf file, add this to it:

        <Directory "/path/to/your/gallery/directory">
         AllowOverride Options FileInfo
        </Directory>
       

If you don't have access to your httpd.conf, delete the .htaccess file in the setup/ directory.

This is a very common problem. It's usually because the image manipulation program isn't getting called correctly, and this can happen for a number of reasons. To diagnose the problem, follow these steps:

If you see any of the following messages, the solutions are listed below

If you still can't find a solution, try asking in the Gallery Support Forums.

First, send them a quick email and ask them if they are willing to upgrade. They should considering a PHP version this old is years and years old, and probably contains security problems. Your only other good option is to install PHP as a CGI, as in FAQ B.3

This is a bug in some versions of NetPBM that cause it to choke on grayscale images. This is fixed in the version of NetPBM available on the Gallery download page.

This is an unfortunate situation, because Gallery cannot run in safe mode. You have three options, listed below (try them in that order).

Craig Goranson wrote a very informative email about how to fix this.

If you're using Apache 2, especially with something like RedHat, you may need to edit another directive, LimitRequestBody, as described in this forum post. Setting this directive to 0 (i.e. LimitRequestBody 0) will allow you to upload as big a file as you want (until you hit upload_max_filesize and/or post_max_size -- see the above email link for more information).

The answer is to simply upload the configure.sh file in ASCII FTP mode

The most common reason for this is that you have JavaScript disabled or limited in your browser. Make sure that JavaScript is allowed to open windows, or else you may not be able to login to Gallery.

The number two reason for this problem is that your login page has a slightly different hostname than the one you used for your gallery. You can check this by right clicking on the login page and selecting Properties to see what its URL is. The common cause for this is that you used a variation on the standard URL to get to your Gallery, and then the browser thinks that the JavaScript popup is actually on a different host and it causes a security exception when the popup tries to control the main window. For example, if you've told Gallery in the config wizard that your gallery is at http://www.menalto.com/photos and then you actually access the Gallery by going to http://menalto.com/photos (note the "www" is missing), you'll still see your Gallery, but you'll experience this problem. The solution is to pick one hostname and stick with it.

There could be a few reasons why this doesn't work. Here are some of them

Gallery 1.x generates a ton of warnings. We're fixing this in the next release. In the meantime, you need to turn down the error reporting level in your php.ini file so that you don't see these warnings. You can do that by setting error_reporting = E_ALL & ~E_NOTICE in php.ini. Then restart your Apache server.

If you don't see a change after doing this, it's possible that you're editing the wrong php.ini file. Go to gallery/setup/phpinfo.php in your web browser and it will tell you (near the top of the file) where it thinks your php.ini file is located. After making the change, phpinfo() should say that your error_reporting level is "2039".

You can also add this line to your .htaccess file

        php_value error_reporting 2039
       

You've specified an incorrect path to your albums directory in the config wizard. You can fix this by re-running the config wizard and correcting the Albums URL value or you can edit the config.php file and fix the $gallery->app->albumDirURL variable.

If you unzipped/untarred the Gallery script on a Mac running OS 9.2.1 or less (ie, non OS X), once its uploaded, three files need to be renamed. They are in the HTML_Wrap folder - inline_albumthumb.footer.default , inline_albumthumb.header.default, and inline_gallerythumb.frame.default. The last few characters at the end of these file names will get truncated on the Mac so Gallery won't be able to find them (there will be an error message above and below each photo). Adding the 't' at the end in FTP or Telnet will solve this. This is only a problem if its untarred/gzipped on a Mac. If they are unzipped on the server they will work fine. [Thanks James O'Donnell]

This problem is caused by one of two things:

This can be caused by one of two things:

This typically happens when your ISP makes a change in your environment (like upgrading PHP or moving things around) without telling you about it. In a nutshell, some of Gallery's files wind up being owned by the wrong user and their permissions become set such that Gallery can no longer write to them. I've never found this to be the result of a bug in Gallery. To fix this, you can change the permissions on your Gallery data files so that Apache can read the files again. This should only happen on Unix. If you have shell access, you can fix it like this:

        cd /path/to/albums
        cd ..
        chmod -R 777 albums
       

If you don't have shell access, you can use your FTP client to recursively (every file and every directory) chmod the albums directory 777. Make sure you chmod the .users directory, which can sometimes be hidden from view. See FAQ C.19 for more details

[answered by Vallimar] You are exhausting the available memory that PHP has access to. In php.ini there is a config variable named memory_limit that by default is set to 8MB. I quickly exhausted this after uploading a couple thousand images and had to increase it. Edit php.ini and increase it to a larger value (restart Apache afterwards). If you don't have access to php.ini, you can add this line to your .htaccess file.

        php_value memory_limit [new memory limit]
       

In version 9.19 of NetPBM, they changed the name of the ppmtojpeg binary to pnmtojpeg. It's the same binary and serves the same purpose, but it's got a different name. The precompiled binaries provided on the Gallery download page come with ppmtojpeg . The newer stuff that you might get comes with pnmtojpeg . Gallery tries really hard to figure out which one you have available and use it. However, security restrictions can make it impossible for us to tell for sure. So, it's possible that you have one version of the binary and Gallery expects the other. There are several easy solutions (you only need to do one of these):

In PHP 4.2.3, they made a change to the way that the session code works that results in PHP generating a warning when a session is created. In order to resolve this, we have to update some code in Gallery. This warning has no effect, except that it shows up on screen. You can make it go away by editing your php.ini and setting

        session.bug_compat_warn to off
       

and restart Apache.

If you don't have access to php.ini, add this line to your .htaccess

        php_flag session.bug_compat_warn off
       

This should be fixed in future versions of Gallery.

This is because on some FTP clients, the default setting is to hide files that begin with a dot. The file may actually be on the server, but your FTP client isn't programmed to display it. To make these files "reappear", you must change some settings. PixelPoet has written a tutorial for WS_FTP available here: Quick Tips for Chmod with WS_FTP. If you use CuteFTP, see this thread in the forums.

In RedHat 8.0, the default web server is Apache 2.0. Unfortunately, PHP and Apache 2 aren't very stable together yet, though current versions of PHP and Apache 2 do work relatively well together. However, there is a bug in the version of PHP distributed with RedHat 8.0 that can corrupt uploads. For information on how to fix these errors or scewed pictures, see this thread in the forums. Keep in mind that these are merely workarounds. The best option is to upgrade your PHP version to the latest from http://www.php.net/

As in Red Hat Linux versions since 8.0, the default web server is Apache 2. Apache 2.0 uses a totally different module API, making it necessary to rewrite all modules for this new version. Unfortunately, the PHP version that Red Hat 9.0 is distributed with has a very buggy interface with Apache 2.0. Some of these bugs have been fixed with the latest version of PHP. Please download the latest version from http://www.php.net/. See this forum post for information on how to compile PHP.

There are two ways to do this; both are shown below:

This is a function that was introduced in PHP 4.0.5. You can upgrade your version of PHP, or if you prefer, make the following change to view_photo.php

Insert the following at line 57 in view_photo.php

if (!function_exists('array_search')) {
        function array_search($needle, $haystack) {
                for ($x=0; $x < sizeof($haystack); $x++) {
                        if ($haystack[$x] == $needle) {
                                return $x;
                        }
                }
                return NULL;
        }
}

      

Your host has magic_quotes_gpc enabled in php.ini This causes form variables with quotes to be escaped with backslashes. Gallery tries to turn off this functionality, but in your case, this didn't succeed. You'll need to contact your host and ask them to turn this directive off, at least just for your site.

You need to use WinZip twice. (WinZip is a bit weird when it comes to .tar.gz archives).

[Answered by forum user Allistah] Replace your NetPBM binaries with binaries from this page. Then add libjpeg.dll which can be downloaded from this page. Unzip the NetPBM binaries and libjpeg into the same directory. Finally, re-run the configuration wizard and provide the path of these new binaries. (original forum post: here).

This is caused by a PHP directive called open_basedir. Basically, your host has mis-configured this directive and not added the directory where Gallery is to the allowed directories where PHP can access and modify files. You'll need to contact them and ask them to add the directory where you website files are located.

Your host setup a quota for the web server user. Though your account may still have space left, the quota for the web server user has been overrun. Basically, you'll need to contact your host and ask them to cleanup the filesystem and/or adjust the quota. If you are your host, adjust the quota using edquota.

Basically, this is a form of safe mode. Gallery requires functions like exec() to perform operations on images. The steps to "fix" this problem are the same as in FAQ C.5.

The default install of ImageMagick on FreeBSD doesn't seem to compile with some important image support (e.g. JPEG), so you must explicitly tell it to. There are two ways of doing this.

There are two ways, each pretty much equal in simplicity.

Upload a file named test.php to your NetPBM or ImageMagick directory. The contents of this file should be

<?php
print getcwd ();
?>

       

View this file via the web (for example: http://www.example.com/gallery/ netpbm/test.php). It will tell you the absolute path to specify.

One of two things in happening

These values are defaults. They take effect for new top-level albums, but do not affect already existing albums. If you want to change the value of these parameters for already existing albums, edit each album's properties.

The straight answer is no. Gallery must have the images on the local server in order to manipulate (i.e. resize, rotate, etc..) them. There is no fast, easy, and widely available way to manipulate (i.e. edit) files on remote servers (there are a few, but none fit all 3 criteria).

It is possible, however, to host your images on multiple servers in order to distribute the bandwidth. For instance, if you have a server that doesn't support PHP, but has lots of bandwidth, you can host the images on that server (as well as the local server) and Gallery will attempt to use the images on the server with lots of bandwidth, so that the local server doesn't suffer so much. More information is available in the mirroring tutorial.

If you go to http://www.example.com/gallery/setup/check_mail.php and it gives you the following errors:

         "Error! sendmail_path not set"
         and/or 
         "Error! SMTP not set"
         

you will have to do some changes to your php installation. If you get the "Error! sendmail_path not set" you can safely ignore it on Windows, since it disregards the sendmail_path anyway. To fix the other potential problem, locate your php.ini (probably under C:\Program Files\php or C:\windows), open it with a texteditor and find "[mail function]".

It should look something like this:

         [mail function]
         ; For Win32 only.
         SMTP = 
         ; For Win32 only.
        sendmail_from = 
        ; For Unix only.  You may supply arguments as well (default: 'sendmail -t -i').
        ;sendmail_path =
        

Change SMTP to whatever smtp-server you can use that doesn't need authentication and sendmail_from to an email address. Example:

         SMTP = smtp.server.com
         sendmail_from = youremail@server.com
        

Resetting your admin password is easy; just rerun the configuration wizard and specify a new password on step 2.

If you have a file called gallery/css/embedded_style.css (ie without the ".default" ending) you should update it. Download your version, open it in Notepad, and cut and paste the contents of gallery/css/embedded_style.css.diff to the end. You can configure the new classes if you want to, and then upload the new version to your website.

You do not need to make any changes to standalone.css. Since version 1.4.1 Gallery also has configurable image frames. If you have customized frames for your images, they should still work with 1.4.1.

However, if you would like to use the new frames, you will need to remove the following files, as appropriate:

        html_wrap/inline_albumthumb.frame   html_wrap/inline_photo.frame
        html_wrap/inline_gallerythumb.frame html_wrap/inline_photothumb.frame
        html_wrap/inline_moviethumb.frame
       

If you didn't touch the CSS or frame files, this probably means that you didn't override the files upon upgrade. Make sure that your FTP client overrides the old files and upgrades to the new ones.