Community @ The Turning Gate

That doesn't solve the problem. It's just another way to work around the problem, but ends up being a more complicate (manual) way than simply using the (automatic way) with Publisher renditions.

The original images are held in a folder "photos" which is automatically created when you publish. When you're using a desktop computer and have the download image option enabled pointing at "photos", those are the same images you see as the ones you download.

On a mobile device with the Touch gallery, the download option is broken. It won't download from "photos." This works in Magnific which seems to be looking in the "photos" folder for downloads.

The work around for Touch is to enable Publisher renditions, which creates a second folder of images which are placed in "photos-for-download." While this is automatic, it's a second copy of the same file. Doing it this way is a work around, but it's redundant and slows the publishing process creating duplicate files.

Your suggestion of using images in an entirely another folder is just another second copy. Setting this to "photos" is how you avoid creating a second copy of all the images. Changing this to something else means manually creating images, and then uploading them. It also means every time I edit an image, rather than simply clicking Publish on the album I'd have to remember to manually create the images and then upload them. Right? That defeats the purpose of using Publisher.

I don't want any manual effort, as this would be a real hassle maintaining the over 1,000 images in dozens of albums that change as I add/edit/delete images.

Using the Publisher renditions is the best option, since this is fully automatic. I'm just wondering if there's a way to avoid the duplication of rendering the same file twice, at the same settings.

A quick test seem to show the download option works on the iPhone using the Touch gallery if you set Publisher to push the downloadable renditions.

There's a couple downsides.

I have to remember to keep the Publisher's copy to use the same settings at the Gallery's template. Not all that bad, since changing the template is a rare event (for me).

This creates two copies of all the images and that makes publishing take twice as long. That's a bummer because LR is so slow creating all the files, and I can only publisher one album at a time (to avoid LR bugs).

Is there a way to make the Touch gallery use the original set of images for downloading. The originals are in "photos" and the Publisher generated ones are in "photos-for-download".

I'm guessing a PHP Plugin couldn't change this.

Hmm, it works with mobile presentation set to Magnific popup, but it fails when set to Touch. That's the opposite of what I would have guessed.

The odd thing is using the Magnific popup create a grey ghost for the down-arrow cloud icon. When touching it, it opens the image in a new window. Long touch that and you get the Save Image option.

If you just long touch the original item, you also get the Save Image option.

I think I can change my gallery to not use Touch, and use the Magnific popup. But this seems like a bug in the Touch gallery.

I'm using Gallery 6.1.7, and regenerated the gallery with Magnific popup. Still fails.

will G_TEMPLATE suffice

Oh, sweet. That sounds perfect!

Yup, all the latest software installed.

I simply remove all "Feedback Options" from the CRG Admin page. I leave just one for Comments in the "Feedback Textfields".

Then a tall thumbnail in the feedback page causes the stars to collide with the comments label, as I've shown.

Changing the CSS moves the thumbnail, to stop the collision.

I could change the title in Magnific Popup, but not in Highslide Slideshow

Argh - I'm getting confused by the server and/or browser caching previous data. My changes are sometimes being seen, even when I thought I got it.

Never mind <sound of head hitting desk surface>

Yup - I found that to be true. Pain in the butt to only publish on album at a time.

Thank Rod,

I think you're saying to copy the original code. Then use the PHPlugins to replace it with the same code minus the one I want to remove. Correct?