Support community for TTG plugins and products.
NOTICE
The Turning Gate's Community has moved to a new home, at https://discourse.theturninggate.net.
This forum is now closed, and exists here as a read-only archive.
You are not logged in.
I hate it when computers do exactly what I tell them to do.
That was it. Can't even call that a problem, just didn't remember that was a setting.
Mostly I am trying to make bigger (useable for iconic) thumbnails, but I have discovered that Lightroom is not making new image editions at all when I "mark to republish". It does make the new renditions (to the size I have set) when publishing new albums. It even does when I add a new photo to an existing album, but I cannot trigger a new rendition for an already existing image.
(yes, I am aware of the "make custom thumbnails post" by Matt. the problem is I really want to have random thumbnails, and I have a lot of album sets to keep track of, too many to choose custom thumbnails for)
Failure process:
- Updated from CE3 to Backlight2
- Accepted when Lightroom wanted me to republish when setting up new publisher plug-in
- "Publish" all albums and sets
- Notice that (in ftp client) the dates of files in "thumbnails" and "photos" have not changed (most date back to 2015, oldest to 2009)
- Notice that thumbnail sizes are really small (long ago setting was 180px)
- Add new photo to album and publish and it gets correct sized rendition
So, it's working correctly for new images (and hence probably not a backlight problem) but Lightroom is not generating new renditions for previously (CE3) published albums.
What am I missing?
Publishing problems solved as well?
Yes, Ben solved it remotely.
A complication we found while troubleshooting is that Lightroom seems to be maintaining a session with the server and changing the key without restarting Lightroom makes it refuse to authenticate with the new key, yet still work with the one that was there when launched. But on a per publisher instance basis, so it could work with one instance but not another.
So for anyone fighting with Lightroom, restart it every time you change something.
Thank you Matt! No promises required, I appreciate your looking into it.
Well, that was easy with 2.0.5
What you should have in your .htaccess file is a directive that reroutes all http traffic to https, effectively eliminating http traffic altogether.
I don't have a cert, but I think there is one for the server. I can't find what the htaccess file should look like for that in the documentation using the documentation search.
Not sure what I should change to make https mandatory
We'll have to wait and see if Matt decides to add a pano feature to Theater.
That's the reason I made it more of a feature request. Editing the code each time for each is not really practical, but publishing to a template would be.
Hopefully this catches Matt's interest once he sees it.
What about something like this, embedded in Theater's Pym iframe
https://codecanyon.net/item/360-panoram … ref=annapx
or this, without Wordpress:
https://www.jqueryscript.net/other/Mobi … Query.html
or this:
https://www.jqueryscript.net/other/Simp … pport.html
I'm trying to avoid having a Wordpress instance, but that may be the simplest way to do this.
However, may I humbly suggest a feature request for a new add on for flat-panorama album type? It's far outside my coding ability, but displaying (iPhone) panoramas outside of facebook is a need I bet many photographers would pay for.
There used to be a way to display panoramas (in CE4) with the stage plug-in so that they would scroll rather than scale. There seems to be no way to do this in Backlight. Does anyone have any clever ideas to do this?
I have been poking around a bit while waiting to hear back from Ben
I have one instance of publisher authentication working in Lightroom. Of Five. All others fail with the exact same settings. It least I know that the site is actually able to publish, but why only one?
The one I got working I used https:// for the prefix and that got it working.
Just so we don't have to go down that path, I'll preemptively explain;
Master Lightroom Catalog: My (mostly) landscape images, has a giant Collections top level with a lot of albums and a Separate Portfolios top level of curated samples. I could be convinced to roll this together.
Events Lightroom Catalog (an entire separate library): has My event work that I donate to a non profit. in a top level directory called events. This is not in main catalog
NSFW Lightroom Catalog; Art nudes, both portfolios and private albums. Obviously, kept entirely separate
I've been doing this in CE4 (and CE3) For years
If you edit the master are those changed reflected to the clone, or is it more of a fork than clone?
Thank you for clarifying. That is very fair and generous terms.
I havn’t been able to find anything on the site or docs;
Where and how many times may I install and use Backlight?
I manage several sites, most on one server, but not all. I spin up test sites. I install dev instances in sub directories. How many times an under what circumstances are allowed for one purchase (order number)?
All the sites I own (I have access to and am putting my credentials into)? Just one? Just one domain?
Mostly curious, but it may be handy to use in two domains and have a test “instance” in a subdirectory.
What is the official answer? (Keeping in mind I am unlikely to buy more than one full priced licence)
Maybe an obvious question, but is the API key the same in Backlight and Lightroom?
It never hurts to check the obvious, but I even made it 123456 in both places just to eliminate any possible way to screw that up. (It’s not that anymore)
So I am pretty sure that isn’t it.
Website provider is going to upgrade PHP an reinstall GD and imagenagic, hopefully that will solve the upload issue. I’ll report back.
Still need to solve the Lightroom API issue.
Here is a snip from the server log regarding the upload failed error
[Mon Jan 07 01:12:03.699778 2019] [:error] [pid 2651] [client 71.36.96.158:63236] PHP Fatal error: Call to undefined function ImageCreateFromjpeg() in /srv/photo.fx4.net/htdocs/backlight/modules/module-publisher/application/helpers/ImageResizer.php on line 134, referer: http://www.lightsmithy.com/backlight/pu … 1600/view/
[Mon Jan 07 01:12:03.699875 2019] [:error] [pid 2651] [client 71.36.96.158:63236] TRACE: returning: {"status":"error","message":"Unexpected error: Call to undefined function ImageCreateFromjpeg() in ImageResizer.php on line 134"}, referer: http://www.lightsmithy.com/backlight/pu … 1600/view/
I have managed to somewhat successfully upgrade my existing site, however:
I can not authenticate the API in Lightroom "Authentication check was NOT successful"
API URL is http://www.lightsmithy.com/backlight/publisher/ (note that it will not let me delete that trailing slash)
I am also unable to publish an image using the web publisher, "Upload failed" and then "Upload error". I can create an album and album set, but cannot upload an image.
I have:
- removed all other instances or TTG publisher and older versions from Lightroom, and installed and reinstalled the version downloaded from my backlight site.
- Reinstalled the entire backlight installation from the modules page
- Poked around with the designer and Backlight seems to be functional other than not publishing anything in any way.
I can't find any specific match here for my problem and the similar ones have not provided a solution. Not sure how to proceed from here.
galleries/custom-thumbnails should be a directory that you create via FTP, and therefore always writeable by you. This is not the same folder as custom_thumbnails found within each album. Any image placed within galleries/custom-thumbnails can be used as the cover image for any album.
THAT is extremely helpful. That was unclear.
Hmmmmm. I'll have to dig deeper then. Or just fix it and not care what's broke.
To be clear, if I load the thumbnails directory of a child auto index with something, the parent auto index should use that (as well as the thumbnail directories of child galleries alongside the child auto index) is my logic correct there?
Would this behavior be caused by any empty thumbnail directory within search range? (i.e. an untapped error)?
nope. That was first thought.
http://www.lightsmithy.com/collections/01parks/
Eastern Mountain region was migrated from CE3, as was Alaska, and Rocky Mountain. Southwest, Midwest, and Pacific is all new. I think Alaska is the only one with no new galleries, I've added some new one other places.
In any case, if it used to work and now doesn't....
Who is the owner of the directories? It's Apache in my case
the only way that random will work for those sets is if you've manually uploaded thumbnails to each set's thumbnails/ folder.
except that it is working for some of them, and I can't manually upload any thumbnails ( http://community.theturninggate.net/post/28428/#p28428 )
If it wasn't working at all, it would make more sense
Something is causing my autoindex thumbnails to break, and I can't figure out what. (It wasn't what I thought)
see http://www.lightsmithy.com/collections/01parks/
Some of the thumbnails are missing, some are working. All auto indexes were created using the same template with the same settings (cover image set to random). I had thought that it had something to do with nested album sets, until I noticed that Eastern Mountains was broken (it doesn't have any nested sets) and Pacific region is not, though it does have nested album sets (thumbnails on auto index's within /pac are broken when there are nested sets, is that a coincidence?)
I can manually set thumbnails from the list, but that is not as nice as the random thumbnails (IMHO)
http://www.lightsmithy.com/collections/02regional/ is 100% broken
These are a mx of CE3 upgraded to CE4 published incidences and new published only with CE4. Eastern Mountains is upgraded (and does not have custom-thumbnail directory or a mobile-thumbnail directory. Pacific was created with CE4
Any idea what I've done wrong?
I should also note that the custom-thumbnails directory is also 755, so I can't put anything in it.
additionally, it does not appear that published albums converted from CE3 have custom-thumbnails directories (which I suppose means I can fix those)