The paths and URLs in this guide are examples. Be sure to replace them with the paths and URLs specific to your installation.
With Gallery 2.3 and later, the best way to run Gallery Remote is no longer to install it, but to run it from Gallery's Add item page (on the Gallery Remote tab). This requires that you already have Java installed on your machine. Java will optionally create an entry in your applications menu and/or desktop so you can run GR later without having to log in to Gallery. It will also keep GR up to date automatically each time you run it.
You can still install GR the old-fashioned way, but this may no longer work on newer OSes, like Windows 7 and newer versions of Java:
If you're using WebStart to run GR, you don't need to do a thing: Java will keep GR up to date.
If you encounter a problem, the logging system may be some help, and we will definitely request it if you ask for support. By default, GR writes most log information to the file GalleryRemoteLog.txt in the temporary directory for your platform. If you want to see more detailed information in this file, you can set the log level to "Detailed, very verbose" in the Gallery Remote preferences dialog.
If you would like to see the log unfold as you use the application, rather than having it go to a file, you should change the following:
Caution: Your password is printed in clear text in several places throughout the log. Be careful before posting your log to forums or sending it to anyone.
Don't look for the Gallery Remote log on the server, it's on the client!
The log file is in the temporary directory for your platform:
When you install Gallery Remote version 1.4.1 and later on Windows, it installs two executables: Gallery Remote and Gallery Remote Debug. You can run the latter to get a log window. At the top of the log, it should tell you where the log file is saved.
Whereas on Windows, ImageMagick and jpegtran are installed by the installer, on other OSes, they are not automatically installed, and must be installed by the end-user.
Please make sure that these products are available in your Unix PATH variable: you should be able to run them from a command-line as:
Also see Gallery Remote:Bundled.
Same as above.
You can use https:// URLs with Gallery Remote to connect to secured web sites. This functionality is only available on Java 1.4 and later. If the site you are attempting to connect to uses a server certificate that is not certified by a trusted certificate authority, Gallery Remote will be unable to connect. If this happens, you will need to add the site's certificate to the Java registry of trusted certificates:
keytool -import -trustcacerts -file path_to_cer_file -keystore %JAVA_HOME%/jre/lib/security/cacerts -alias arbitrary_name
cd /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/security sudo keytool -import -keystore cacerts -trustcacerts -alias mycacert -file path/mycacert.crt
For Linux (debian and ubuntu, at least)
sudo keytool -import -keystore /etc/java-1.5.0-sun/security/cacerts -trustcacerts -alias myalias -file myfile
Even though there is a Preferences dialog, the preference files can still be edited for some hidden extra options. You should not modify the defaults.properties file, but you can read it to understand what each preference does. Then, you can edit the GalleryRemote.properties (it is created the first time GR is run) and add or replace the preferences you want to change.
Make sure Gallery Remote is not running when you edit the GalleryRemote.properties files, or your changes will be overwritten.
The preferences files is in a directory named .GalleryRemote inside the current user's home directory (on recent versions of Windows, this is the Documents and Settings/username directory on the boot partition). Mac and Linux users generally know what their home directory is.
On G2.3 and later, the best way to run GR is by starting it from the Add Items page in G2, in the Gallery Remote tab. Select run Gallery Remote immediately. This uses WebStart, and should work more reliably on new OS and Java versions.
For older versions of Gallery, the following applies:
If you get an error message saying ImageMagick or jpegtran is not installed please see Gallery Remote:Bundled.
If you are running Gallery 2, make sure that you have installed the 'Remote' module. It contains the 'Implementation for the remote control protocol' and enables the remote applet. This module is not included in the (current) 'Typical' installation package.
Make sure you are not running in maintenance mode - trying to connect from Gallery Remote while in maintenance mode also causes this error.
You will usually get this message when your web server is set up to return a nice-looking page to tell you when a page is missing rather than the 404 error message GR expects. You have two options:
<?php header("HTTP/1.0 404 Not Found"); exit; ?>
Mac users you will have to go into the Terminal (shock horror) becuase this directory is hidden. Make sure you have run Gallery Remote at least once but that the application is closed before you start. Then open up Terminal app and type the following:
You will be confronted with the GalleryRemote.properties file in the PICO text editor. Use the arrow keys on keyboard to scroll down to bottom of file then paste the code from above. Change the letter n to the number of your url (mine was 0 as I only added one url).
Then save your changes by using the key combination [ctrl] - O
Then exit PICO by using the key combination [ctrl] - X
Now close Terminal app and relaunch Gallery Remote. This worked for me :)
Most of the time, GR (1.5.1-b5 and later) works out of the box in non-latin languages, but sometimes it's necessary to help it along add the following lines to your GalleryRemote.properties file:
fontOverrideName=SimSun fontOverrideSize=12 fontOverrideStyle=0
If any of these lines is absent, GR won't apply the correct font settings. For example, if only fontOverrideName is set, the font won't change.
Please note that the recommended way to run Gallery Remote is to run it directly from Gallery, please see this other FAQ.
Gallery Remote is installed using Install Anywhere, which is developed by Macromedia. In a small number of situations, the installer may not work correctly. When that is the case, please try to install the .jar version: download it from SourceForge and run the installer (you need to already have Java 1.5 or later installed)
java -jar GalleryRemote.jar
(the name of the file you downloaded may be slightly different)
Usually, the standalone version of Gallery Remote will not run out of memory, because it is configured to get a lot of it. The Gallery Remote applets, on the other hand, have to make do with whatever the web browser allocates for them, and that is often not enough.
If you get a message about an out of memory error, here are a few possibilities to ensure you can use your applets without problems:
Then you'll want to take a look at the manual for the Gallery Remote protocol manual.
You can also check if you can reuse some of an existing such application (most are open-source).
You need to install the Gallery Remote module on your web server. To do this, log in to your gallery as the administrator, go to "Site Admin," then "Plugins," "Get More Plugins," find "remote control" near the bottom, and download that module. Voila!
Starting with Java 1.6, you can enable smoother transitions by adding
-Dsun.java2d.opengl=true to the Java command-line, which allows Java 2D to use OpenGL to composite images. For applets and on Windows, this is done in the Java control panel, in the Java tab, Java Applet Runtime Settings (click View...). Add the snippet above to the Java Runtime Parameters (to be safe, add it to all lines that correspond to a versions 1.6.0 or above).
When Gallery Remote runs as an applet or from WebStart, the Java VM attempts to load some files from your web server, which are not present by design. This causes the web server to log 404 errors (unknown document or incorrect URI). These messages can safely be ignored.
In Gallery 2.3 and later, when GR runs on a 1.6 Java VM, Java should not attempt to load these files, and the errors should not appear.