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.
Currently running the latest updates from BL2 that came out a few days ago: BL 2.0.5, Cart 5.0.4, Publisher 4.0.5 Doing all my publishing from BL2. Encountered this problem when I tried to add a couple photos to an existing online album. The 2 photos have pricing scheme data stored in the category field of the metadata. This is confirmed in both Capture One and Photomechanic. When the images are published via BL2 the pricing scheme seems to not be transfered and the pricing of the 2 images is set at the default setting. I have deleted and republished these 2 images a dozen times each. Cleared cache in BL2 and in browser. Clicked "Updfate Album Files" in BL2 admin. Examining the database in phplite I don't see the pricing scheme metadata for either of these photos.
Album with problems is here: https://photophart.com/art-prints/art-p … and-white/
Images with problems are: "Layers, Lines" and "Rain Drops On Pine"
Category (pricing scheme) should be "Collector_BW_13X19" Both are listed with default pricing.
I'm just now looking at the naming of the gallery where these images reside and wondering how I got 3 dashes in that directory name. Could that be the problem??
Thanks in advance, Mark
I'll look forward to that. Thanks again.
Mark
Well, that didn't take long. Ben, you've nailed it. Wordfence is indeed the culprit. I couldn't figure out how to have Wordfence exclude Backlight so I deactivated it. Image uploads to the site via BL2 immediately worked perfectly. Should be useful information for Wordfence users to have.
Thanks as always, Mark
Wow, that's a lot of feedback. Starting at the top. Rod and Daniel, these are albums in an album set created by BL2 that exist on a page in a wordpress blog. A menu selection takes you to the album set. It's cute and worked well up till now. Ben, your input looks to be exactly like what's happening. Let me experiment with your two suggested strategies. I do, in fact have Wordfence running on this site. Why it didn't occur to me that it might be playing a part in this is beyond me. I'll get back to you on how this goes. Many thanks for the input all.
Mark
PS emailing Ben an image that doesn't upload
Thanks Daniel, yup, I've done that and it works fine but it won't get the images into a Backlight managed album.
This problem originally was raised in this post http://community.theturninggate.net/vie … hp?id=9242 and rather than add to that lengthy thread I thought perhaps I should start a new one. Using Ben's excellent help with the first publishing problem I thought I'd found a workaround to republish all my images in all my albums on all my websites using BL2 publisher, not Lightroom, by carefully examining the metadata of each image before publishing. It worked perfectly on hundreds of images in dozens of albums. And then I got to the blog... On my blog I've several small albums of just a few images. I spent a ten hour day yesterday trying every trick I could think of and using every one of a half-dozen software applications to export images, change images, change metadata, strip metadata, resize, downsize, change file type, change file name, in a vain effort to publish images to the website using BL2. In all instances, no images would publish. In every case the error was a timeout that Ben had previously determined was mangled metadata in the images. Methods I had used to successfully publish troublesome images on other websites didn't work on the blog. Finally, in desperation I tried to use Lightroom to publish the images. That's when an even stranger thing happened. Lightroom will not publish images to the blog either. In fact, it won't update images in previously published albums that still exist on the blog. Lightroom generates the following error:
Unable to perform action: uploadRendition Message: Unexpected error: Unexpected character in input: (ASCII=25) state=0 in rules.php on line 842
The ASCII value in the error varies, being either 24, 25, or 26. If memory serves those ascii values are symbols for things like substitute and cancel. Not sure what those are doing in previously published images.
Sorry for the long-winded post but is was a long-winded day. Any ideas on what might be going on here would be most welcome.
Regards, Mark
Create a new shortcut on your desktop. In the box for "type the location of the item" paste the url of the page you want to go to, https://pideja.ca/mbf/galleries/ in this case. That url is gotten by actually going to the page in question, clicking on the url of the page in the address bar, press ctl-c to copy it, then ctl-v in the box mentioned above. Don't forget to click next, then give the shortcut a name.
Ben, it's on its way to you. Interestingly if I take the image that failed to upload, open it in Photomechanic, update the metadata fields there, and then drag the image from Photomechanic to the BL2 upload screen it uploads just fine with the correct metadata intact.
Tried different ways of exporting as a JPEG from Capture 1 with and without various kinds of metadata. All failed. Tried exporting as a JPEG from Affinity Photo. This image will upload to BL2 but there is apparently missing metadata as no print ordering is possible, assuming the category metadata has been stripped. I've some other options which I will try later tonight or early AM. Keep ya posted. Most frustrating part of this is that BL2 uploads with images exported from Capture 1 work perfectly 99% of the time. I've uploaded literally hundreds of images in the last week. These failures are quite rare, but annoying.
Mark
The image was exported as a JPEG from Capture 1. Capture 1 has export "Process Recipes" that are quite versatile, allowing all manner of export variability from location, to file time, to file size to....you name it. Let me try exporting that image from something else. But it will need to be something that exports "category" in the metadata as that's where my pricing schemes are hiding.
All done. Go Ben!
By share an image do you mean upload it to the forum? Just letters in the pricing scheme name. Working on Ben's request.
Tried that. Even tried FTPing the images directly to the /thumbnails, /photos/, photos-for-purchase, and /master directories on the server. That doesn't work, presumably because they aren't being seen by the database during the BL2 upload process. Next on the agenda I'll try modifying the images ever so slightly..say, maybe re-crop or something, and export them again to see if that changes anything. I'm starting to wonder if perhaps there might be something stored in metadata that could be clobbering the upload. Tricky to sort out as different image processing software shows you different fields of metadata. ON1 for instance doesn't show you "category" but Capture 1 shows you "category" in 2 different places.
The more you dig the more you find there's more in the hole than you thought.
Mark
I've been happily going along converting ALL of my Lightroom published albums to BL2 published albums and it's been going great...except for one troublesome issue that pops up from time to time in a very unpredictable manner. When I drag a bunch of JPEGs from Windows Explorer to the upload space in BL2, occasionally 1 to 5 images will fail to upload. Each time the error is about a "timeout" that exceeded 30 seconds. Sometimes if I try to re-publish those errant photos 1 or 2 will succeed, but mostly not. If I wait a day or two the same failure occurs. So it's probably not a server hicup. I try re-exporting the errant images from Lightroom changing the settings slightly and get the same error. So it seems to be something peculiar about the image that makes it fail to upload. There are no weird characters in the filenames and they are well below the size limit of 64GB. Stranger still is the fact that the failed images are actually in the album and can be viewed on the website. Only thing flaky about the image is that its pricing scheme didn't seem to be uploaded because adding it to the cart for purchase produces the wrong product and price. So it seems metadata is what's failing in the upload. This could be gotten round if I could find a way to update metadata in images uploaded via BL2.
Any ideas?
Mark
PS The whole idea in all of this was, of course, to get rid of Adobe products. Haven't given up on that, just need to get over or under this little bump in the road.
False alarm perhaps. A re-installation of BL2 was all that was required. Seems to be working now.
regards
Unexpected error: Cannot redeclare class URLHelper in URLHelper.php on line 4
The above error happens when I try to open it at: http://www.valhoffman.com
Obviously I missed something. Just moved the entire site from subdomain to here then changed URL in backlight settings.
Ideas? mark
PS subdomain runs fine here http://subval.valhoffman.com
OK, got my site back by clearing the cache in BL. Looks like I wiped out my home page slideshow in my zeal to free myself of the tyranny of the Adobe empire. As you might imagine I've got a bit of reconstruction to do now. Ever hear the saying "haste makes waste" ? Certainly true in this case.
Sorry to waste your time.
mark
Have been busily converting all my LR albums in to BL2 published albums and it's been going great. Was cleaning up some loose ends in BL publisher by deleting old LR albums and album sets by just hitting the delete button. Seemed simple enough. Now when I try to get to my site at: https://markhoffmanphotography.com I get the following error: Something went wrong
The album with id 11914 could not be found in GalleryDelegate.php on line 91
Obviously something I did. Any ideas on how to fix it?
mark
Right as always Rod. My bad. Forgot about avoiding the use of weird characters in filenames.
Thanks, Mark
This error message began appearing for all new albums I try to create in BL2 publisher. I'm publishing from BL2 not LR. Images I publish appear to transfer to the respective albums and when I check the server the images are where they are supposed to be but they don't appear in BL2 or on the actual site. I get place holders but no images.
See it here: https://markhoffmanphotography.com/imag … in-valley/
This problem popped up as I was converting a bunch of LR albums to BL2 albums. Worked fine for about five albums then this error started and all further attempts to publish from BL2 have failed.
Mark
In Motion Hosting. Been with them over a decade. Backlight1 and Backlight2 run great there.
Live blog at https://blog.photophart.com has been successfully updated to BL2. However I had to reinstall Wordpress from within WP admin on the site after the BL2 update just as with my test site. Without reinstalling Wordpress the blog displayed NO content. Latest updates to BL2 appear to have made PHPlugins functional again. Thanks.
Regards, mark
Resolved. The issue with Wordpress showing no content after updating to Backlight2 has been resolved for the test site https://blog.photophart.com/testblog . The fix should have been a bit more intuitively obvious. It wasn't. A reinstallation of Wordpress from within WP admin was the first step to the solution. I then went to the posts, edited the very first post, made no changes and clicked update. All subsequent posts then appeared on the test site. Sidebars as well.
A problem still exists with PHPlugins not appearing on the home page. PHPlugins does appear to be active on other pages in the blog such as galleries and search.
Worth a try if you're seeing this on your site.
mark
P.S. Many thanks to Matt for going above and beyond on this one. A rare event in today's world.
I've created at ftp acct for you allowing access to the test blog. But when I try it I get a blank file listing. Thought I knew how to setup ftp accounts in cpanel but apparently I'm missing a step or steps. Will email you the logon. Maybe it works from your end.
Is it conceivable that a plugin like, say, Wordfence, might be clobbering the site? I bring that up because I encountered a problem with Wordfence destroying the ability to setup cloned Wordpress sites.
On that assumption I disabled them all. Problem persists