Yes, however we are in the process of updating our plug-ins to 64 bit compatibility and in the meantime users needs to use Aperture in 32 bit mode to continue use of our plug-ins. To do this, in the Applications folder find "Aperture" and highlight it. Now select "Get Info" from the File menu. In the info window, check the Run in 32 bit Mode checkbox. If it it locked, click the lock graphic in the bottom corner and enter your password. You should then be able to use the plug-in 32 bit mode until a 64 bit version is available. Alternatively, you may use Aperture in 64 bit mode and when the plug-in is launched an alert is displayed asking if you would like to restart in 32 bit mode to continue use of the plug-in. When you quit, the next time Aperture is launched again in 64 bit mode.

There is a bug in Aperture 3 that causes plug-ins to specify the last used preset in Aperture's export dialogue instead of the one you choose when in the export plug-in module. A suggested workaround is to export an image normally using the required preset in Aperture, then use the plug-in for that setting chosen previously.

We have a general FAQ section with a licensing page outlining the answers to most common questions here. If you find you still need assistance, please email support here.

A Gallery entry's connection settings can edited by selecting the entry and then double-clicking on it.

A likely cause for this is because PHP enforces a size limitation for data uploads (usually 2 MB) which may be preventing your image from being sent to your Gallery installation. This size limitation can be adjusted by editing the php settings in your php.ini file. For more details, click here.

By default the plug-in assumes that the default path (http://www.yourdomain.com/gallery2/main.php) should be used to communicate with your Gallery installation. If you have changed this path or have apache setup to do redirects (via .htaccess files or httpd.conf settings) then you may have problems using the plug-in. One possible solution is to set a custom path for the Gallery entry. This can be specified when creating or editing the connection settings for your Gallery.

Apache mod_security may be preventing access to your gallery. A possible solution is to create (or add to) an .htaccess file in the root of your Gallery installation and enter the following line:

SecFilterEngine Off

HOWEVER, please take the time to research the security risks you take by disabling this feature.

All users accessing this file will need their own licensed copy of FileMaker Pro.

Please ensure that you have enabled the "Remote" and "Upload" modules in the Gallery administration section so that the plug-in can properly communicate with your Gallery installation.

When you load the plug-in all your current albums are loaded and displayed in the browser. If you edit your albums using a web-broswer (or any other means) while actively using the plug-in, these changes will not be reflected and doing so could lead to errors or strange behavior. It is generally advised not to modify your Gallery installation in any way while using the plug-in.

Unfortunately at this time only HTTP servers are compatible with the plug-in. But a future update will allow this functionality. Be sure to sign up for the mailing list or follow us on Twitter to stay current on the latest releases.

Various levels of logging can be enabled by editing the plug-in's plist settings using Terminal. Logs can then be viewed with Console. This log output is useful when corresponding with us about problems you are experiencing The logging levels are as follows: 0 - Fatal Errors; 1 - Normal Errors; 2 - Info Messages; 3 - Warning Messages; 4 - Debug Messages. A given logging level will display that level and any level above it. As an example, the following will enable Debug level logging:

defaults write com.ubermind.export.ApertureToGallery.plist LoggingLevel 4

When diagnosing plug-in errors, there are several system variables to take into consideration first before digging deeper into the code. Repairing your permissions is a good place to start, and also good practice after installing software. To do this, launch Disk Utility from the Applications under Utilities. Then select Repair and press Repair Disk Permissions. This basically cleans up your system files so that they can access each other properly. If this still does not resolve the issue, you could test with another account or create a new test account on your machine prior to more elaborate solutions. For more on what information you should send in when requesting technical support, please read through the general FAQ section.

ApertureToGallery can be removed by deleting the plug-in file located at:
~/Library/Application Support/Aperture/Plug-Ins/Export/ ApertureToGallery.ApertureExport
(~ represents your home directory)

If you are removing this plug-in because you have experienced problems or it did not meet your expectations, please contact us and let us know why.