Community @ The Turning Gate
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.
- New user registrations are disabled.
- Users cannot create new topics.
- Users cannot reply to existing topics.
You are not logged in.
- Topics: Active | Unanswered
#1 Re: Backlight 3 Support » JSON » 2020-05-01 22:51:20
One of the things I would love is some way to automate the creation of a hierarchy of album sets and albums in such a way that it is visible both in Lightroom and Backlight. It's not uncommon for my daughter's dance studio recital shoot to have two levels of album sets (top level and then 3-4 different shows with 20 dance routine albums per show) and creating them through Lightroom is rather painful.
I'm not sure what the best way to do that would be.
The most likely candidate (in my mind) would be a LUA script in Lightroom to interact with the Backlight Publisher directly to create the album sets and albums programmatically considering that implementing a true two-way sync between Lightroom and Backlight is likely to be far more of a pain than it's worth for the few of us who build massive gallery collections.
What would be really cool would be taking a top-level folder in Lightroom and having some sort of plug-in traverse the folders to build that hierarchy in the Backlight Publisher...all we'd really need to do is provide a slug prefix for the album sets/albums and the templates to use for album set and album and let it pick the name and description out of the folders themselves. And if such a hypothetical beast could automatically add the files to the albums wherever they exist, that would truly rock. At that point, my workflow becomes load the pictures, sort them by show and then dance, kill the rejects, and then let this thing build the huge recital galleries and hit [Publish] once it's done and let it run overnight! 
Push comes to shove, my current workflow (whilst somewhat painful) does the job I need it to do and Backlight's part in it really does shine in spite of Lightroom's limitations. If it weren't for the fact that Lightroom Mobile my iPad Pro is where I prefer to sift through the 14,000+ recital pictures, it'd be much easier to divorce myself from the Publisher for these massive galleries.
#2 Re: Backlight 3 Support » error trying to update to version 3 » 2020-04-30 22:53:04
FYI, The PHP memory_limit setting also bit me when I kicked off the upgrade (I made it to line 117 but the gist of the message was the same).
For Backlight users that are on a virtual private server (VPS) rather than shared hosting (Bluehost, HostGator, et al), you might have to fix the PHP memory_limit directive in a slightly different fashion. What follows worked on my VPS at inMotion...your VPS vendor may have a different set of tools available to you for managing the VPS.
Whilst debugging this on my server, I discovered that PHP 7.3 was ignoring the local php.ini files in the home directory and webserver root that the CPANEL php.ini editor can edit in favour of the default php.ini in the server-wide PHP installation directory.
Seeing that I'm on a VPS and don't mind kicking those settings up for every site I host on that server and can do so safely without wrecking anyone else on that physical box, I got round the error by going ahead and editing that base php.ini file using the php.ini editor available in Web Host Manager (WHM) as root.
Then it was back to Backlight's module screen and it was clear sailing for the upgrade! Woo hoo! I've got to admit to being rather spoilt by the Backlight 2+ update screens/processes compared to the old "copy all of this stuff hither and yon and fiddle with these things and for goodness sake don't trash the data directory and really ruin your day" README procedures from the CE3/CE4 days...
#3 Re: Backlight 2 Support » Contact form recaptcha v2 not working in FireFox... » 2020-01-16 10:34:23
That's a shame -- the 'address' field doesn't look like it's the culprit. I'm out of ideas. Can you provide me with FTP access and a Backlight admin login so I can try to debug this?
Sent via EMAIL. Thanks and have a good afternoon/evening!
#4 Re: Backlight 2 Support » Contact form recaptcha v2 not working in FireFox... » 2020-01-16 08:59:08
I've found a way to consistently make the form work now with FireFox...as long as you don't autofill the form, it works perfectly.
I also deleted the stored data for "address" and then did an autofill using that entry and that also worked correctly.
So I guess that "address" is the key field here that's breaking the form under FireFox which is where I think Ben was heading.
Weird. But certainly a fun investigation!
#5 Re: Backlight 2 Support » Contact form recaptcha v2 not working in FireFox... » 2020-01-16 08:38:54
That would be it then. I'm more interested in the network traffic, and which fields and values are sent to the server when clicking Send. That submission and the values sent should be available under the Network tab of the inspector. Look for a sub-panel called Params. You may need to check 'Persist Logs' so that the request info doesn't get removed on the page redirect to the success page.
On my site (and in my own Firefox 72 that doesn't seem to autofill anything for me), I see entries with values for 'name' and 'email', and an entry for 'address' with no value sent.
If this does prove to be the issue, then I can look at adding the autocomplete="off" attribute for either just the address honey pot, or for all fields.
Hopefully a quiet evening then?
One can dare to dream... 
Two more screenshots and the log file containing the HTTP requests are now out in Google Drive for your perusal. I did submits with and without the recaptcha enabled to see if there was any appreciable difference (and autocomplete was turned off).
Hopefully this exercise has at least proven to be interesting, if not useful! Write once, debug everywhere with browsers is one reason I'm finding I enjoy photography and videography more and more every day. At least if the camera settings are bolloxed, it's usually pretty to sort out who put the foot wrong!
If there's anything else I can do or test, please don't hesitate to ask (meanwhile, I'm going to put everything back the way it was with recaptcha enabled). And of course, thanks to you and Rod for proving once again that awesome technical support still does exist in this world...
#6 Re: Backlight 2 Support » Contact form recaptcha v2 not working in FireFox... » 2020-01-16 07:17:57
Thanks, Rod. Sunfox, please see my reply above.
I put a couple more screenshots into the Google Drive folder I sent above showing the hidden CSS/DOM mismatch. Didn't really see any fields that shouldn't be there. I'm going to see if I can find some PHP logs to see if they're helpful in figuring out why the form submission is failing.
Might be a bit as I have to drop off two of the three kids that I'm not keeping tonight...
In the meantime, I'm going to re-enable recaptcha on that form so the spammers are hopefully blocked.
#7 Re: Backlight 2 Support » Contact form recaptcha v2 not working in FireFox... » 2020-01-16 07:12:41
That is strange. The contact page will report success if the honey pot field is submitted. I’m not in front of a PC to see what the name of the field is. ‘address’ perhaps. It is a field on the page that is hidden by CSS. Some bots may not be able to detect that it’s meant to be hidden and attempt to provide a value.
Can you inspect the contact submission from Firefox to see whether an extra field is being sent by Firefox?Also, if you disable reCAPTCHA on the form, do submissions from Firefox get through?
Disabled recaptcha on that form and FireFox is still appearing to successfully submit the form but no EMAIL is stored in the database (looking in Backlight admin or my inbox). Doesn't throw the exception either but if recaptcha source code isn't included, that's not surprising given where the debugger said the error was.
That's rather weird.
I did check the form under debugger and it looks like everything that should be there is...the address field shows up in the HTML but it's hidden by CSS. Looking at the form, it does appear to have a non-NULL value (probably populated by the saved form info feature in FireFox). What was really interesting is that if you look at the form in the debugger, the hidden attribute on the field is set to false even though the CSS does hide it...wasn't expecting that mismatch between the CSS and the inspected DOM value.
I turned off the auto-complete functionality but it appears that FireFox is still caching the value and is populating the hidden field even if I don't explicitly choose to auto-complete the form.
#8 Re: Backlight 2 Support » Contact form recaptcha v2 not working in FireFox... » 2020-01-16 06:38:12
test message sent
Nothing has arrived in the inbox...also now completely updated to latest version of Windows 10 and it's still persisting with failing on that one script with the unknown base64 encoding error. I suspect the problem is on Google's side serving up that recaptcha code.
I appreciate your help with this...fortunately, it's more annoying than anything else as there is a workaround. As long as it stops the spammers cold, I'll be thrilled!
#9 Re: Backlight 2 Support » Contact form recaptcha v2 not working in FireFox... » 2020-01-16 04:33:04
Post a link to your site and I’ll try sending a test message
https://www.redvixen-studios.com/
The contact form is under the “burger” menu.
I’m in the process of updating my laptop to the latest feature release of Windows 10 (taking forever!). A web post on recaptcha suggested that Windows 10 and FireFox may be exploiting an OS bug...I’m looking to prove or disprove that. My version of Windows 10 was fairly old (1809) because my OS drive was critically low on space until a month ago.
#10 Re: Backlight 2 Support » Contact form recaptcha v2 not working in FireFox... » 2020-01-16 03:11:57
Currently running version FireFox 72.0.1 (64-bit) on Windows 10 which Mozilla is reporting is the latest version.
I also temporarily disabled the enhanced tracking protection feature for the site thinking that might make a difference (I'm normally running FireFox in STRICT mode which usually doesn't tend to affect the Backlight sites but it was worth testing!). Before I turned it off, FireFox was reporting that it didn't detect any trackers on the site which is a bit of good news.
Unfortunately, still seeing the same behaviour where reCaptcha seems to pass and the submit reports success but the EMAIL isn't stored or sent. That behaviour occurred both before and after clearing cache.
I fired up the FireFox debugger and loaded the page and hit an "Unknown base64 exception" in recaptcha__en.js at line 61 (unfortunately, it's minimised code which makes debugging much more painful). That's probably what's breaking FireFox...
I've dropped a couple of screenshots onto Google Drive:
#11 Re: Backlight 2 Support » Custom Thumbnails Sort Order » 2020-01-15 23:42:06
Closed a similar topic: http://community.theturninggate.net/vie … hp?id=9087
This is proving to be very difficult to fix. I'm still looking into it.
Well, at least it's an interesting problem to consider! Those of us who extensively use the custom thumbnails will be very appreciative at the same time we're sad that LUA is making you have to jump through all of these hoops when the server already has done the heavy lifting apparently in vain! 
#12 Backlight 2 Support » Contact form recaptcha v2 not working in FireFox... » 2020-01-15 23:30:02
- SunFoxNC
- Replies: 16
I've finally gotten round to adding recaptcha v2 support to my contact form for redvixen-studios.com because someone has unleashed a spambot against it.
I fired up FireFox (my preferred browser) and updated all of the Backlight 2 modules (thank you so much for making that about as painless as it can possibly be!) to the latest and greatest versions, went to Google to get the v2 site keys (public and private), added them to the contact form in Admin and turned recaptcha debugging on.
I went to the contact page and saw the "I am not a robot" recaptcha filled out a test EMAIL submission, clicked the recaptcha checkbox and was passed with the green check mark. My first thought was "wow...Matt and Ben made this so freakin' easy that I really feel like a complete and utter doofus for not doing this earlier!"
I then clicked [Send] and no EMAIL was received with no error messages on screen or in the logs.
I cleared the cache and tried again...same thing...passed by recaptcha but no joy in the inbox.
I then thought that maybe the debug setting was just testing the communication with Google without actually sending the EMAIL (I'll admit...beta-testing was my first real job and I'm such a nerd to think of things that way!) so I turned it off and tried another submission...was passed through recaptcha but no EMAIL in the inbox afterward.
I popped back into the Backlight 2 admin and chose the "send test EMAIL" option and that EMAIL landed in the inbox so I was at least sure the underlying mail handling was working (as the spammers had also proved).
Finally, I fired up Chrome to see if it's potentially a browser problem (that would be a *HUGE SHOCK*, I know!)...filled out the fields, passed by recaptcha after checking the box...clicked [Send] and the EMAIL showed up almost immediately in the inbox.
I also tested it on Safari on my iPhone...got the images challenge from recaptcha (yay...nice to see that!), was passed through and also received the EMAIL almost instantly in the inbox.
I checked Backlight 2 Admin to see if the EMAILs at least made it to the contacts screen which shows all of the EMAIL requests that came through but none of the ones sent when using FireFox appear in the list. The ones sent through Chrome and Safari do appear there which makes me think that FireFox is somehow failing to save the EMAIL in the database preventing it from being sent by the mailer. I didn't see any error messages in the logs to that effect to aid in debugging, unfortunately....
The site is hosted on an inMotion VPS using the stable version of php v 7.3.
#13 Backlight 2 Support » Changing hosting providers with Backlight 2... » 2019-11-06 01:07:09
- SunFoxNC
- Replies: 2
When I started with CE4 and Backlight three years ago, my photography site was hosted with Bluehost as the suggested hosting. Since then, I've grown out of shared hosting and had to get a VPS with Inmotion for an application I was supporting and the fact that Lunarpages which I had been with for many years was now completely flaking out.
Needless to say, I wasn't looking forward to moving redvixen-studios.com until the term ran out on Bluehost...i.e. until I absolutely had no choice!
Major kudos to Matthew and Ben and their architecture of Backlight 2 as well as a couple of posts here in the support forums by Rod...the migration turned out to be breathtakingly simple:
---
1. Backup the entire site to a local drive via FTP.
2. Provision a CPanel account for redvixen-studios.com on the VPS server.
3. ZIP the local backup and FTP it to a temp directory on the VPS server. If the file is huge, you'll definitely want a FTP client that can resume uploads where it leaves off when the connection gets dumped every now and then. Studios was about 17GB...it took 14 hours to back up and about 10 to upload the ZIP file over a cable modem connection.
4. Use FileManager in CPanel to extract the uploaded backup archive file into public_html.
5. Point DNS to Inmotion's name servers and let the changes propagate through the net. The top-level name servers updated almost instantly but Spectrum took about a day before they took the hint.
At this point, the site was 95% functional with only the menu items for home/about/contact pages being broken.
This turned out to be caused by Bluehost defaulting to PHP 7.3 whereas the VPS was only provisioned up to PHP 7.2. One quick run through EasyApache 4 to clean out the old PHP versions and add 7.3 and then update all of the domains to use PHP 7.3 sorted that problem.
Updating the PHP version broke the top-level .htaccess by clearing out the Backlight rules...easily fixed by copying them back in via the local backup.
---
It's nice having that site moved to its new home and Publisher has no idea that it's on a much better provisioned server!
#14 Re: Backlight Support » Seeing weird custom thumbnail sizing in Iconic album set... » 2018-12-10 08:35:18
Rod...brilliant as always!
Custom Thumbnails was using my default album template which set thumbnails at 250x250...prior to the upgrade to Backlight 2, the recital thumbnails were using a custom album template where the thumbnails were maxed to 512x512 but for some reason that template didn't get migrated.
I've cloned the album template and changed the renditions as suggested and republished...now the thumbnails look uniformly lovely (well, except for those that were being randomly selected but they were using a different template which I've just fixed and I'm now forcing the republish!).
Thank goodness for the "publish only thumbnails" option on the Publisher considering this part of the website has over 36K pictures in it!
Cue Ren and Stimpy doing the "Happy Happy Joy Joy" dance...
#15 Re: Backlight Support » Seeing weird custom thumbnail sizing in Iconic album set... » 2018-12-10 06:07:00
That's why I was so surprised at seeing the behaviour I'm seeing...the original images in the Custom Thumbnails folder for that Publisher instance are 7360x4912 which should be more than enough for the 500px maximum width specified in the template for Thumbnail Max-width (that slider is full to the right).
Other than the theatre season poster images (which are sized 375x250 but show up as 250x167 in that album set even though it's well under max width in the template), everything in Custom Thumbnails is either 12mp (D700), 16mp (D7000), or the vast majority 36mp (D810).
I want to say I've tried forcibly resizing the image and then adding it to Custom Thumbnails and noticed no difference after forcing that album set to republish. The only thing I could think of that was different was when the recital galleries were published in 2017...the site was running Backlight 1. The upgrade to Backlight 2 happened before the NC State Fair galleries were uploaded which is what made me think that there might have been some code changes for Iconic between the two versions of Backlight.
Mind you...it's not like you can't tell what's happening in the thumbnail images. It just looks kind of weird when some are fuzzy looking and another one in the same gallery looks nice and clear and the original images were all 36mp photos from the D810.
#16 Backlight Support » Seeing weird custom thumbnail sizing in Iconic album set... » 2018-12-10 05:44:48
- SunFoxNC
- Replies: 6
For the Backlight 2 site at redvixen-studios.com, I've noticed some interesting behaviour with random sizing of custom thumbnails when displayed by an album set template using the Iconic layout.
The following link is where you can see some screenshots for the gallery that is exhibiting this behaviour so you can follow along with my narrative.
https://drive.google.com/open?id=14snZL … 5UeHz1_TW4
If you look at the first screenshot, you can see that the first two thumbnails from galleries created in 2018 are kind of fuzzy and are sizing at 250x167 but the third thumbnail from 2017 is nice and clear sizing at 500x334.
All three of these images were copied as-is from Lightroom into the Custom Thumbnails gallery that has been suggested by Matthew and published using the Publisher plugin. The original images all came from a Nikon D810 with an original resolution of 7360x4912.
The last set of screenshots show the template configuration for the iconic album set used for the galleries.
=======
Has thumbnail resizing changed significantly in the underlying Backlight 2 code from 2017 to 2018 to explain why newer thumbnails are sizing much smaller? I don't see anything in either of the Backlight changelogs that would apply to this situation. BTW, love having the link to the changelog in the Backlight 2 module management screen...a subtle but very nice touch!
Are there any best practices one could employ to ensure consistent sizing of custom thumbnails for Iconic album sets? Ideally, I'd like them to all publish at least at 500x334 (or larger if possible!) which works well in a three-column album set layout on all of the devices I would view the set.
Thanks!
#17 Backlight 2 Support » Slight bug in phplugins-pangolin-sample.php... » 2018-10-03 02:05:53
- SunFoxNC
- Replies: 5
As I was fooling about with grabbing album information via phplugins to automatically display in Galleria, I was playing with this code and noticed that the third break (br) tag is missing the closing greater-than. Most browsers won't necessarily care but those of us who were toilet-trained at gunpoint do...
/* DELETE THIS LINE
function copy_top()
{
//echo 'style: '.$this->style.'<br/>';
//echo 'path: '.$this->path.'<br/>';
if ($this->hasAlbum()) {
echo '<p>';
echo 'Album Title: '.$this->album->getTitle().'<br/>';
echo 'Album Description: '.$this->album->getDescription().'<br/>';
echo 'Number of photos: '.$this->album->getNumberOfPhotos().'<br/';
echo '</p>';
}
return true;
} // END /**/There's a couple of new features in Backlight 2 that I think are not necessarily going to be appreciated for how awesome they are until you actually get round to playing with them. This is one of them and is exactly what I was asking about a long time ago about having an API that would expose details of items. At the time I was thinking exclusively of images but being able to extract album information programmatically is way cool...especially when you're using them as the image dumpsters in a Wordpress site! I can't wait to see what else I can extract from published gallery items...
The other feature is the movement of the authentication and album passwording functionality into the core from the Client Response Gallery. Yes, it was number two in the announcement but became very much appreciated when I did a photo shoot this weekend at a therapeutic horseback riding event. It was trivial to build a new album set containing the albums and stick a password on it to discourage casual browsing from people who weren't at the event until we can determine the privacy requirements/implications. No more futzing about with users in Apache and .htpasswd which is always a pain!
This will make putting up galleries from the kid's school events equally as trivial (especially when you're dealing with a class where kids have special needs and you don't know who opted out of photos/videos)...woo hoo!
But the best part of that new feature is that you get a choice of just putting a password on or creating a full client account. That distinction in the implementation was unexpected but brilliant, IMO.
#18 Re: Backlight 2 Support » Goofy Lightroom error since updating to Backlight 2... » 2018-09-29 13:09:51
The Publisher plugin has changed very little, and we've not seen these problems locally. Please ensure you are using the most current version of the Publisher, downloaded from Backlight's Admin => Backlight Modules page. If problems persist, then you may need to reset Lightroom's preferences (unfortunately, a fairly standard troubleshooting step with Lr).
I suspect it might be something I've been triggering by what I was doing with a lot of mouse clicks.
I was effectively "transplanting" collections from a CE4 Publisher instance for a subdomain that no longer existed to a Publisher instance pointing to the Backlight 2-managed collections on a different domain. As I'd edit an old album set to see which custom thumbnail I'd used (and then get the warning that it couldn't connect to the defunct CE4 instance) and then do some other clicking about the old CE4 collections to select photos to move about on disk...that's when I'd notice Lightroom getting unhappy more often than not.
As I retire these old CE4 Publisher instances in favour of the Backlight ones and stop trying to be Lewis Hamilton and driving Lightroom right to the limits, these problems will likely go away.
#19 Backlight 2 Support » Order of custom thumbnail filenames in Publisher album set/album list? » 2018-09-28 22:50:17
- SunFoxNC
- Replies: 2
I've got a custom thumbnails album for my publisher instance where I've been putting the thumbnails used in my album sets / albums and it contains thumbnails with filenames like this:
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 6/18/2017 11:31 55981 emw_20170604_115455_Studio5_Recital_1100_1512.jpg
-a---- 6/18/2017 11:28 60486 emw_20170604_131122_Studio5_Recital_1100_4367.jpg
-a---- 6/18/2017 11:51 65593 emw_20170604_135756_Studio5_Recital_1330_0583.jpg
-a---- 6/18/2017 12:41 64767 emw_20170604_164938_Studio5_Recital_1615_0512.jpg
-a---- 9/9/2018 22:59 57397 emw_20170921_201929_Gilbert_Evil_Dead_0097_thumbnail.jpg
-a---- 9/9/2018 22:59 36878 emw_20170921_210719_Gilbert_Evil_Dead_1119_thumbnail.jpg
-a---- 9/9/2018 22:58 69603 emw_20170921_215410_Gilbert_Evil_Dead_2092_thumbnail.jpg
-a---- 9/9/2018 23:00 63212 emw_20170921_215456_Gilbert_Evil_Dead_2113_thumbnail.jpg
-a---- 11/26/2017 18:53 31875 emw_20171122_202547_Its_A_Wonderful_Life_0485.jpg
-a---- 2/3/2018 06:30 59637 emw_20180201_203333_Gilbert_Venus_in_Fur_0319_thumbnail.jpg
-a---- 2/3/2018 06:30 67890 emw_20180201_211423_Gilbert_Venus_in_Fur_0956_thumbnail.jpg
-a---- 2/3/2018 06:30 71589 emw_20180201_215301_Gilbert_Venus_in_Fur_1437_thumbnail.jpg
-a---- 4/6/2018 12:27 60397 emw_20180405_202739_Gilbert_Antigone_D810_0107_thumbnail.jpg
-a---- 4/6/2018 12:25 32054 emw_20180405_203008_Gilbert_Antigone_D810_0127_thumbnail.jpg
-a---- 4/6/2018 12:30 50289 emw_20180405_204515_Gilbert_Antigone_D810_0286_thumbnail.jpg
-a---- 4/6/2018 12:22 72989 emw_20180405_220950_Gilbert_Antigone_D810_0873_thumbnail.jpg
-a---- 6/1/2018 22:13 36413 emw_20180531_201308_Gilbert_CatOnAHotTinRoof_0081_thumbnail.jpg
-a---- 6/1/2018 22:14 53397 emw_20180531_202705_Gilbert_CatOnAHotTinRoof_0295_thumbnail.jpg
-a---- 6/1/2018 22:12 61926 emw_20180531_205509_Gilbert_CatOnAHotTinRoof_0940_thumbnail.jpg
-a---- 6/1/2018 22:15 56800 emw_20180531_214311_Gilbert_CatOnAHotTinRoof_1433_thumbnail.jpg
-a---- 9/9/2018 23:12 50875 emw_20180908_181224_Pryer_Awards_2018_0011_thumbnail.jpg
-a---- 9/9/2018 23:13 67235 emw_20180908_185404_Pryer_Awards_2018_0147_thumbnail.jpg
-a---- 9/9/2018 23:10 41897 emw_20180908_204745_Pryer_Awards_2018_0676_thumbnail.jpg
-a---- 9/23/2018 16:50 72490 emw_20180920_194432_Godspell_0006_thumbnail.jpg
-a---- 9/23/2018 16:50 89557 emw_20180920_204842_Godspell_0677_thumbnail.jpg
-a---- 9/23/2018 16:50 71607 emw_20180920_205336_Godspell_0811_thumbnail.jpg
-a---- 9/23/2018 16:50 71241 emw_20180920_205737_Godspell_0920_thumbnail.jpg
-a---- 9/26/2018 23:55 48609 gilbert_2012_2013_seasonposter.jpg
-a---- 9/28/2018 07:31 40425 gilbert_2013_2014_seasonposter.jpg
-a---- 9/26/2018 23:59 44810 gilbert_2014_2015_seasonposter.jpg
-a---- 9/26/2018 23:58 54746 gilbert_2015_2016_seasonposter.jpg
-a---- 9/26/2018 23:57 75395 gilbert_2016_2017_seasonposter.jpg
-a---- 9/23/2018 15:57 41122 gilbert_2017_2018_seasonposter.jpg
-a---- 9/23/2018 14:45 46829 gilbert_2018_2019_seasonposter.jpgThis custom thumbnails album is set to order on filename in Lightroom and if you look in the album in Backlight 2's publisher section, you can see that the filename sorting is respected.
But when the list of custom thumbnails are offered in the Lightroom Publisher plug-in popups for album sets/albums...the filenames offered in the list are presented in a random order making finding and selecting the desired custom thumbnail somewhat painful.
Would it be possible to have that drop list offer the filenames in the custom thumbnail album's defined order?
Also, it'd be nice if I'm looking to choose from a custom thumbnail that only the custom thumbnails be offered in the drop list. The current implementation seems to pull all of the potential thumbnails after the custom thumbnails are offered which for some of my albums can be a huge list.
Thanks!
#20 Backlight 2 Support » Goofy Lightroom error since updating to Backlight 2... » 2018-09-28 21:28:12
- SunFoxNC
- Replies: 3
I've noticed a new Lightroom error message that is popping up if I'm doing a lot of fiddling with albums/album sets with the Backlight 2 version of Publisher:
"Lightroom has encountered a problem with its menus. Some menu commands will not work until Lightroom has been restarted."
I'm using Lightroom Classic CC 7.5 on Windows 10 and it definitely started with the new version of Publisher. I've not found a consistent cause for the error other than doing a lot of Publisher operations and doing the restart does fix things until the error decides to rear its ugly head again.
#21 Re: Backlight 2 Support » Mixed Publishing » 2018-09-21 14:22:44
You can also make any changes to an album that came from LR within Backlight itself, except for change the parent of the album. That includes changing the album settings and adding new photos. Any changes to the album settings get propagated back to the LR album the next time you edit it.
Am I correct in presuming that album sets/albums created directly in Backlight 2 in a gallery managed by LR Publisher won't be propagated back to LR via the Publisher?
I was in the process of building the skeleton for a Wordpress/Backlight2 site which took all of three hours...two and a half of which was spent in Wordpress. After I had Backlight2 installed on the server...I quickly created a test album set and album using the Backlight Admin publisher (in all of two minutes for both of them including upload time for some images I just dropped on that window...that new direct album set/album functionality is SLICK!).
After making a quick run to Fayetteville for a dress rehearsal photo shoot, I updated the Publisher plug-in in Lightroom and created a new Publisher instance to play with the default installed Backlight 2 gallery but only saw the empty "Default Album" that's normally populated with a new instance.
I imagine a fully bi-directional sync would be a far more massive undertaking for the Publisher plug-in given the required backwards compatibility with CE4 and BL1 so I would expect the behaviour I saw above to be "as designed" unless you tell me otherwise.
Because I can see a use case where the majority of gallery album sets/albums are created and managed in LR Publisher as they have been for years but that there would also be times where it'd be nice to bang out a quick album set/album through Backlight 2 directly (i.e. Lightroom isn't available like on a tablet away from home)...would the best practice be to have two separate galleries...one for LR to populate via Publisher and one for the one-off ones populated directly through Backlight 2 and not mix them?
#22 Re: Backlight 2 Support » Clean install on local WAMPSERVER instance... » 2018-09-13 03:25:42
I used to be a beta-tester/QA way back when in my IT career so it's nice to know that I can still break things even when I'm not even trying!
I went ahead and tried the new installer (1.02) anyway because I was genuinely curious and it's a local throwaway install...the Framework.php error referenced earlier is gone but I'm still seeing the same error message "The installer was unable to connect to the server: https://get.theturninggate.net/install/has_backlight/" with the following entries in access.log.
Interestingly, the access log is showing GET requests at root even though I explicitly chose to navigate to the URL "http://localhost/sunfox-test/backlight/installer/" directly...not sure where those are coming from.
Looks like the redirects for installer's CSS gets into an infinite loop until Apache or Firefox pulls the plug on the redirects.
::1 - - [12/Sep/2018:14:03:58 -0400] "GET / HTTP/1.1" 200 5584
::1 - - [12/Sep/2018:14:03:58 -0400] "GET /wampthemes/classic/style.css HTTP/1.1" 200 2466
::1 - - [12/Sep/2018:14:03:58 -0400] "GET /index.php?img=gifLogo HTTP/1.1" 200 4549
::1 - - [12/Sep/2018:14:03:58 -0400] "GET /index.php?img=pngPlugin HTTP/1.1" 200 548
::1 - - [12/Sep/2018:14:03:59 -0400] "GET /index.php?img=pngWrench HTTP/1.1" 200 741
::1 - - [12/Sep/2018:14:03:59 -0400] "GET /index.php?img=pngFolderGo HTTP/1.1" 200 694
::1 - - [12/Sep/2018:14:03:59 -0400] "GET /index.php?img=favicon HTTP/1.1" 200 1429
::1 - - [12/Sep/2018:14:03:59 -0400] "GET /index.php?img=favicon HTTP/1.1" 200 1429
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/installer/ HTTP/1.1" 200 929
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/installer/js/scripts.js HTTP/1.1" 200 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/installer/css/styles.css?v=1.0 HTTP/1.1" 200 1936
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/normalize.css HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:11 -0400] "GET /favicon.ico HTTP/1.1" 200 202575
::1 - - [12/Sep/2018:14:04:18 -0400] "POST /sunfox-test/backlight/installer/ HTTP/1.1" 200 1074
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/installer/js/scripts.js HTTP/1.1" 200 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/installer/css/styles.css?v=1.0 HTTP/1.1" 200 1936
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/normalize.css HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:04:19 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
So I tried "http://localhost/sunfox-test/backlight/installer/index.php" (not relying on the default resolution)...saw the same cascading redirects and failure to contact the server with these access.log entries:
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/installer/index.php HTTP/1.1" 200 929
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/normalize.css HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/installer/js/scripts.js HTTP/1.1" 200 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/installer/css/styles.css?v=1.0 HTTP/1.1" 200 1936
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:38 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:47 -0400] "POST /sunfox-test/backlight/installer/ HTTP/1.1" 200 1074
::1 - - [12/Sep/2018:14:14:47 -0400] "GET /sunfox-test/backlight/installer/js/scripts.js HTTP/1.1" 200 -
::1 - - [12/Sep/2018:14:14:47 -0400] "GET /sunfox-test/backlight/installer/css/styles.css?v=1.0 HTTP/1.1" 200 1936
::1 - - [12/Sep/2018:14:14:47 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/normalize.css HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:14:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:04 -0400] "POST /sunfox-test/backlight/installer/ HTTP/1.1" 200 1074
::1 - - [12/Sep/2018:14:15:04 -0400] "GET /sunfox-test/backlight/installer/js/scripts.js HTTP/1.1" 200 -
::1 - - [12/Sep/2018:14:15:04 -0400] "GET /sunfox-test/backlight/installer/css/styles.css?v=1.0 HTTP/1.1" 200 1936
::1 - - [12/Sep/2018:14:15:04 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/normalize.css HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:04 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:04 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:04 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:04 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:04 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:04 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:14:15:05 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/installer/ HTTP/1.1" 302 -
I've also tried the requests with SSL and it's still showing the same sort of cascading redirects.
I'll keep playing with it...I'm wondering if it's not liking that the directory in question is configured as an alias via Apache.
Here's the alias configuration from Apache:
Alias /sunfox-test "e:/srv/wamp/sunfox-test/"
<Directory "e:/srv/wamp/sunfox-test/">
Options Indexes FollowSymLinks MultiViews
AllowOverride all
<ifDefine APACHE24>
Require local
</ifDefine>
<ifDefine !APACHE24>
Order Deny,Allow
Deny from all
Allow from localhost ::1 127.0.0.1
</ifDefine>
</Directory>
FWIW, this is running on WAMPSERVER 3.1.3...Apache 2.4.26 and PHP 7.2.7.
I do appreciate the time you've spent on sorting this out so far but please feel free to treat it as the lowest priority as I've got a perfectly sound workaround.
#23 Re: Backlight 2 Support » Clean install on local WAMPSERVER instance... » 2018-09-12 16:30:53
Appears to be a missing directory/file (modules/module-framework/Framework.php) that is referenced by the index.php at the top-level directory. The ZIP file contains the modules directory but is completely empty.
access.log:
::1 - - [12/Sep/2018:02:27:45 -0400] "GET / HTTP/1.1" 200 5584
::1 - - [12/Sep/2018:02:27:45 -0400] "GET /wampthemes/classic/style.css HTTP/1.1" 200 2466
::1 - - [12/Sep/2018:02:27:46 -0400] "GET /index.php?img=pngFolderGo HTTP/1.1" 200 694
::1 - - [12/Sep/2018:02:27:46 -0400] "GET /index.php?img=pngWrench HTTP/1.1" 200 741
::1 - - [12/Sep/2018:02:27:46 -0400] "GET /index.php?img=gifLogo HTTP/1.1" 200 4549
::1 - - [12/Sep/2018:02:27:46 -0400] "GET /index.php?img=pngPlugin HTTP/1.1" 200 548
::1 - - [12/Sep/2018:02:27:46 -0400] "GET /index.php?img=favicon HTTP/1.1" 200 1429
::1 - - [12/Sep/2018:02:27:46 -0400] "GET /index.php?img=favicon HTTP/1.1" 200 1429
::1 - - [12/Sep/2018:02:27:47 -0400] "GET /sunfox-test/ HTTP/1.1" 302 -
::1 - - [12/Sep/2018:02:27:47 -0400] "GET /sunfox-test/backlight/installer/ HTTP/1.1" 200 929
::1 - - [12/Sep/2018:02:27:47 -0400] "GET /sunfox-test/backlight/installer/js/scripts.js HTTP/1.1" 200 -
::1 - - [12/Sep/2018:02:27:47 -0400] "GET /sunfox-test/backlight/installer/css/styles.css?v=1.0 HTTP/1.1" 200 1936
::1 - - [12/Sep/2018:02:27:47 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/normalize.css HTTP/1.1" 200 2153
::1 - - [12/Sep/2018:02:27:47 -0400] "GET /favicon.ico HTTP/1.1" 200 202575
::1 - - [12/Sep/2018:02:27:53 -0400] "POST /sunfox-test/backlight/installer/ HTTP/1.1" 200 1074
::1 - - [12/Sep/2018:02:28:07 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/normalize.css HTTP/1.1" 200 2153
::1 - - [12/Sep/2018:02:28:27 -0400] "POST /sunfox-test/backlight/installer/ HTTP/1.1" 200 1074
::1 - - [12/Sep/2018:02:28:31 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/normalize.css HTTP/1.1" 200 2153
::1 - - [12/Sep/2018:02:29:46 -0400] "POST /sunfox-test/backlight/installer/ HTTP/1.1" 200 1074
::1 - - [12/Sep/2018:02:29:48 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/normalize.css HTTP/1.1" 200 2153
php_error.log:
[12-Sep-2018 06:27:47 UTC] PHP Warning: require_once(../backlight/modules/module-framework/Framework.php): failed to open stream: No such file or directory in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 06:27:47 UTC] PHP Stack trace:
[12-Sep-2018 06:27:47 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
[12-Sep-2018 06:27:47 UTC] PHP Fatal error: require_once(): Failed opening required '../backlight/modules/module-framework/Framework.php' (include_path='.;C:\php\pear') in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 06:27:47 UTC] PHP Stack trace:
[12-Sep-2018 06:27:47 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
[12-Sep-2018 06:28:07 UTC] PHP Warning: require_once(../backlight/modules/module-framework/Framework.php): failed to open stream: No such file or directory in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 06:28:07 UTC] PHP Stack trace:
[12-Sep-2018 06:28:07 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
[12-Sep-2018 06:28:07 UTC] PHP Fatal error: require_once(): Failed opening required '../backlight/modules/module-framework/Framework.php' (include_path='.;C:\php\pear') in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 06:28:07 UTC] PHP Stack trace:
[12-Sep-2018 06:28:07 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
[12-Sep-2018 06:28:31 UTC] PHP Warning: require_once(../backlight/modules/module-framework/Framework.php): failed to open stream: No such file or directory in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 06:28:31 UTC] PHP Stack trace:
[12-Sep-2018 06:28:31 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
[12-Sep-2018 06:28:31 UTC] PHP Fatal error: require_once(): Failed opening required '../backlight/modules/module-framework/Framework.php' (include_path='.;C:\php\pear') in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 06:28:31 UTC] PHP Stack trace:
[12-Sep-2018 06:28:31 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
[12-Sep-2018 06:29:48 UTC] PHP Warning: require_once(../backlight/modules/module-framework/Framework.php): failed to open stream: No such file or directory in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 06:29:48 UTC] PHP Stack trace:
[12-Sep-2018 06:29:48 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
[12-Sep-2018 06:29:48 UTC] PHP Fatal error: require_once(): Failed opening required '../backlight/modules/module-framework/Framework.php' (include_path='.;C:\php\pear') in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 06:29:48 UTC] PHP Stack trace:
[12-Sep-2018 06:29:48 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
I was thinking the redirect from server root index.php (which references Framework.php) to the installer's index.php (which doesn't) was screwing up the installer so I reinstalled the ZIP contents and then called the installer directly but got the same result only without the redirect:
::1 - - [12/Sep/2018:03:00:31 -0400] "GET /sunfox-test/backlight/installer/ HTTP/1.1" 200 929
::1 - - [12/Sep/2018:03:00:32 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/normalize.css HTTP/1.1" 200 2153
::1 - - [12/Sep/2018:03:00:44 -0400] "POST /sunfox-test/backlight/installer/ HTTP/1.1" 200 1074
::1 - - [12/Sep/2018:03:00:44 -0400] "GET /sunfox-test/backlight/modules/module-admin/lib/css/normalize.css HTTP/1.1" 200 2153
[12-Sep-2018 07:00:32 UTC] PHP Warning: require_once(../backlight/modules/module-framework/Framework.php): failed to open stream: No such file or directory in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 07:00:32 UTC] PHP Stack trace:
[12-Sep-2018 07:00:32 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
[12-Sep-2018 07:00:32 UTC] PHP Fatal error: require_once(): Failed opening required '../backlight/modules/module-framework/Framework.php' (include_path='.;C:\php\pear') in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 07:00:32 UTC] PHP Stack trace:
[12-Sep-2018 07:00:32 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
[12-Sep-2018 07:00:44 UTC] PHP Warning: require_once(../backlight/modules/module-framework/Framework.php): failed to open stream: No such file or directory in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 07:00:44 UTC] PHP Stack trace:
[12-Sep-2018 07:00:44 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
[12-Sep-2018 07:00:44 UTC] PHP Fatal error: require_once(): Failed opening required '../backlight/modules/module-framework/Framework.php' (include_path='.;C:\php\pear') in E:\srv\wamp\sunfox-test\backlight\index.php on line 8
[12-Sep-2018 07:00:44 UTC] PHP Stack trace:
[12-Sep-2018 07:00:44 UTC] PHP 1. {main}() E:\srv\wamp\sunfox-test\backlight\index.php:0
Tracing the code from installer/index.php...I'm a bit mystified as to why backlight/index.php one level up from the installer somehow managed to be invoked even though the access logs don't show it.
I'm sure I'm probably missing something silly but for the life of me I'm not seeing it. What really strikes me as odd is that when I went to Plan B...I dumped the exact same contents of the ZIP file on the VPS and called the installer and it worked fine right out of the box. I can't think of anything where the VPS is really different than the local WAMP install...it's straight Apache in both instances.
At any rate, it's not critical...I can work round not having a local install fairly easily though I wouldn't mind eventually having a working local install for development purposes but I'm sure there's lots of more important things to worry about besides satisfying my curiosity!
#24 Backlight 2 Support » Clean install on local WAMPSERVER instance... » 2018-09-12 13:48:57
- SunFoxNC
- Replies: 6
I was looking to test the Backlight 2 installer in a clean installation (not an upgrade) locally on my laptop using WAMPSERVER just to kick the tyres...I was able to drop the files into the aliased directory and get the Backlight page that requests order ID and EMAIL but when I provided those items, I get this error message in a red box:
The installer was unable to connect to the server: https://get.theturninggate.net/install/has_backlight/
If I go to that URL, I get "No input" as a response (not particularly surprising that browsing the naked URL would respond that way but it is kind of surprising that I'm able to get a connection and response directly in the browser but not by the form submission on Backlight's default installer page).
---
So I went for plan B...drop the installer files on a brand new VPS I commissioned last month as a throwaway installation to develop templates before the real installation begins in the server that's going to replace my old family photos site with a new site with Wordpress fronting Backlight-managed galleries.
This time...order ID/EMAIL and the installer worked a treat. One quick login later and fixing up the quick setup and I was into the admin interface. Of course, I had to check out the new installer module and I wasn't disappointed...three clicks and galleria/theatre/WP add-ons were dropped right on the server. The modules management screen is *MARVELOUS* and is going to make managing the version upgrades so much easier. Not that it was particularly hard before if you followed the directions in the README but this is like going from Oracle's old patching system with 50 pages of manual script jockeying to the newer download a huge patch file and run the executable which does all of that crap under the covers!!!
I'm also totally digging the new admin appearance...very clean and tidy and easy enough for someone to use that's already used to Backlight but will also be fairly simple for new users as well.
I am looking forward to playing with Backlight 2 more thoroughly but as it's already very late here, I've got to deliver three kids to three different schools about six hours from now, and then there's this minor matter of Hurricane Florence that's due to strike not too far away from us in a few days...really having fun with Backlight 2 is unfortunately going to have to wait a little longer!
But all in all...well done gents! Well done, indeed!
#25 Re: Backlight Support » Backlight / Wordpress ... best practices? » 2018-01-23 08:33:48
IIRC, if I were to go that route...WordPress would be installed in the document root and I'd just point Publisher at the gallery/galleries I'd be managing there.
The galleries/ folder should be on the same server level as the backlight/ folder. So just put both in the root of the site along with the WordPress installation.
And perhaps the more important question...am I a fool for even thinking of doing this local->remote sync or should I just develop/publish live and save myself a ton of aggravation?
Yes?
It all sounds pretty ambitious though!
That's a fair cop...I was already coming to that conclusion but hearing it from someone who knows Backlight and Wordpress way better than I do makes it easier to take!
I'm just hoping that by asking questions now rather than blithely proceeding that I won't end up like the previous set of Top Gear presenters (Mssrs Clarkson, May, and Hammond) where most of their projects ended up being "ambitious but rubbish" (but bloody delightful watching them on the telly!).
Unfortunately, this particular site was always going to be a horrendous pain no matter what I did...it's sort of a huge Frankenstein monster (weighing in at 70GB now with nearly 300K files in play!) where Backlight is the fifth different framework used for it's pages and galleries since 2003.
I'd have binned it long ago except that it was a labour of love for family and after fifteen years may as well be considered a member of the family! But sadly without unlimited inodes and a fibre connection...maintaining that fifteen years of history just isn't realistic anymore so I've got to evolve and be more intelligent with the server resources I have available.