I have installed the purchased version of my TTG gallery, but when I try to select the gallery in the Web module, it only shows the DEMO version.

To use the purchased version of your gallery, you need to remove the previously installed DEMO version from your Web Galleries folder. The two versions cannot be installed simultaneously.

Are all TTG galleries compatible with TTG Auto Index and TTG Pages’ gallery index?

No, not all. The galleries listed under the HTML Galleries menu are all enabled for use with the auto index. Of those templates in the Flash Galleries menu, only TTG Simpleviewer is enabled for the auto index. And of those templates in the Special Purpose Templates menu, TTG Stage, TTG Auto Index and TTG Pages are enabled for auto indexing.

For those galleries not enabled for auto indexing, or for non-TTG galleries, TTG XML Maker can be used to create the sidecar assets necessary for auto index detection. Any image gallery containing these sidecar assets will be indexed by TTG Auto Index and TTG Pages.

Flash galleries may also be made auto index compatible by embedding them into HTML pages created with TTG Stage. This comes with the added bonus of created an identity plate, header and site navigation menu to keep your Flash galleries inline with the rest of your site design.

The gallery controls in the right sidebar are being cut off, preventing my access to color controls and other options/information.

To fix the issue, hover over the vertical divider between the work area and the panels, click, hold, and expand the panels all the way to the left until you stop. Then quit/relaunch Lightroom. The panel content should reset and be back in view. This fix is demonstrated in video form here.

Can I disable the right-click menu in TTG galleries?

For information on how to disable the right-click menu, please read this article.

Does TTG <whatever> Gallery support multiple pages? / How do I handle large image collections?

Most TTG galleries do not support pagination. This is because some gallery features — such as the Selection Gallery features used for client proofing — are built on HTML forms, which cannot function over multiple pages. Otherwise, input gathered on page one would be lost when the viewer navigated to page two, which would be unacceptable.

Standard advice for large image collections is to divide the group into multiple, smaller collections and to produce multiple galleries. Then use TTG Auto Index to tie your galleries together. Try to find natural places to divide your collections; when a model changes outfits, for example; for a weping, create separate collections for the ceremony, formals and reception; etc.

Presently, only TTG Horizon supports gallery pagination.

What is The Turning Gate’s stance on support for Internet Explorer 6?

The Turning Gate makes no particular effort to support IE6. Internet Explorer 6 is therefore supported only insofar as Internet Explorer 6 supports standards-based web design. Further reading regarding my utter disdain for IE6 may be read here.

I’ve noticed that Lightroom exports web images at 240 dpi. Is it possible to set the web engine to export image files at 72 dpi?

First, Lightroom doesn’t deal in dots per inch (dpi), but in pixels per inch (ppi).

Second, Lightroom exports images from the Web module at their native ppi. This honestly makes no difference on the web, though, as both dpi and ppi only apply to printing. Whether an image is 600 pixels at 72 ppi or 600 pixels at 240 ppi, it will appear onscreen at the same size: 600 pixels is 600 pixels. And at either ppi, the images will print at the same resolution; whether 72 ppi or 240ppi only dictates the physical size of the image. The image at 72 ppi would print larger, while the image at 240 ppi would print smaller. But if you were to scale both images to the same physical dimensions, they would be identical.

To wit, it really doesn’t matter.

If you must really be persistent, though, you can use Lightroom’s Export function from the Library to export images of any size and resolution you like, and can then replace the Web exported images with those of your own specifications. So long as the file names are identical, then the gallery will use them. It’s an extra step. And like I said, it doesn’t really matter.

How can I protect my images on the web?

Fact: There is no sure way to prevent people downloading photos from a website. Watermarking is the only reliable method of rendering your images unusable by downloaders.

There are many tricks used on websites to prevent the download of images. All of these tricks are equally pointless. The CSS trick is easily defeated by disabling CSS. The Javascript trick is easily defeated by disabling Javascript. And all methods are easily defeating by screen captures. I don’t see the use in spending hours of my time to implement tricks in my engines that can be easily defeated in two mouse clicks.

As for watermarking, that is internal Lightroom behavior that I have no control over. The good news is that LR3 is introducing new and greatly improved watermarking controls.