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.

#126 Backlight Support » File Naming bug in TTG publisher? » 2017-11-16 06:23:33

JimR
Replies: 2

I can replicate this in several ways, and after a few ideas that might be causing the problem. I also tried the magic of deleting the Lightroom preference file, but the problem still occurs.


In the LR Publishing Manager, I select the TTG Publisher and go to the File Naming module.

I select rename files to <sequence #(01)>

What I end up with is only one photo in the album, named "01.jpg"

I tried the option to rename files to <image #(01)> and get the same result.

Both the sequence and image number is always 01, resulting in just a single photos called "01.jpg"


I also tried various combinations such as "test-<sequence #(01)>" and publishes just one photo called "test-01.jpg"

Yet another test was "test-<date (YYMMDD)>-<sequence #(01)>". This published more photos, but only when they had different dates. So if I had three photos, and two were shot on the same date, then I only ended up with two photos (e.g. "test-170101-01" and "test-170102-01"). Note that all photo names end with "....01.jpg"


What I think is happening. TTG Publisher is not incrementing it's internal counter, so all <sequence> and <index> numbers are stuck at the same initial value.

The problem then is if there's a name collision, the TTG Publisher is overwriting the file. So in the case of renaming files to <sequence #(01)> you end up with only one photo, named "01.jpg". Similarly, if you rename files to "Photo-<sequence #(01)>" you end up with only one photo in the album named "Photo-01.jpg"


On a related note, even if the sequence/image counter were working, I'd prefer that TTG Publisher not overwrite a file. It could display an error, naming the problem file, but it would be difficult to figure out which is the problem image(s) and how to fix it. Better if TTG just appended the file name with an incremental value just to avoid the collision.

#127 Re: Backlight Support » Poor quality of images after publishing » 2017-11-14 17:43:44

peter wrote:

I opened the page up in IE instead of Chrome and, it was fine all along.

I've banged my head on the desk so many times I just assume odd things are the cache. If you ever see the "wrong" image or something about it that hasn't updated, flush the browser cache.

I wish Chrome (my only browser) had a development mode that would temporarily disable caching.

There's a menu option in Chrome to flush the cache. That brings up a dialog. You can uncheck everything but "Cached images and files." That will removed cached images (an issue that will come up many times while publishing images).

Chrome's cache is also going to bite you while modifying CSS files.

#128 Re: Backlight Support » Hotlink prevention » 2017-11-14 17:37:15

Ben wrote:

Backlight has a further level of caching to also think about

Oh? I didn't know about this. Probably the biggest source of false problems for me has been due to caching. I'll be making changes, and then not finding the change. Eventually it dawns on me I'm looking at the previously cached data.

What are the details about how Backlight caches? Is there a way to temporarily disable it for development?

Ben wrote:

That would be great if you could continue to share your insights on CloudFlare.

I've used it for many years. It's also my DNS service, because they can do a better job with caching that way. Plus, they have good security to prevent DoS attacks, etc. They also provide a SSL cert, so I have https to my site.

The service has grown a great deal since I first signed up with them. Many hosting services have agreements with them to provide free caching. This is typically a cpanel add on.

I went the extra step of using them as my DNS. Still, it's a free service and has tremendously boosted my site's performance.

I would read through their docs https://support.cloudflare.com

Maybe start a new thread on CloudFlare. I'll join and answer any questions that show up.

#129 Re: Backlight Support » Poor quality of images after publishing » 2017-11-14 17:25:47

peter wrote:

Upon further investigation, I can see by logging on to my host that the uploaded images are great (1920x912). Which leads me to believe it's a setting in Backlight somewhere...

I'm guessing it's your browser's cache. Try flushing the cache from your browser and then reloading the pages in question.

#130 Re: Backlight Support » Hotlink prevention » 2017-11-14 08:47:11

Ben wrote:

have you been using CloudFlare during the time your site was acting strangely and 'corrupting' the db?  That service has been known to interfere with Backlight.

The corruption idea was just an idea. Turns out nothing was actually corrupted. I was just getting the strangest things happening, but that was just once and I can't reproduce what ever problem that was.

I've used CloudFlare for many years. It's fantastic, and makes the site much faster. While editing files you have to enable the Developer mode, which turns on caching new/edited files. There's lots of other things to know. I haven't had any problems, once it's all setup.

I have a support ticket into CloudFlare, asking how hotlinking protection is being interfered within htaccess. Once I learn more about that, I can share what I've found. Other than this, I haven't seen any problems. The general issue is just that it's a cache, and while developing the site you have to constantly be concerned if your edits are taking effect or if you're still reading from the (unchanged) cache. I have this same problem with my hosting service's caching, and even my browser's cache.

What problems with CloudFlare do you know about?

#131 Re: Backlight Support » Backlight typography questions » 2017-11-14 07:47:20

peter wrote:

I have: <link href="https://fonts.googleapis.com/css?family=Spectral+SC" rel="stylesheet">
in my Typography Google font box, and this: Spectral+SC in my Navigation Prepend Font-family w/ box.

The font is not Spectral+SC.
Do I need to do something else? I tried diff. items in the Font Family box (in the Navigation settings)

I don't think you want "Spectral+SC" in the Prepend Font-family w/ box. Try "Spectral SC".

If I had a link to your site I could quickly confirm.


peter wrote:

Why is this stuff so frustrating?

I think that's a comment about HTML and CSS wink

One way to debug this type of thing is to learn how to use your browser's inspector. There you can enter the name of the of a font and instantly see the change.

#132 Re: Backlight Support » Hotlink prevention » 2017-11-13 14:55:53

Ben wrote:

One one hand, it's fairly heavy-handed, so may block some referrers that you'd rather allow, such as results from search engines.  To improve on that, see the extra HTTP_REFERER entries mentioned further in the article.

Yup - I caught that too. I don't mind a search engine showing my photos. I actually enjoy that. They'll serve up their own copies. I just didn't want people hotlinking.

Ben wrote:

On the other hand, the article was written in 2012.  With the Internet being a moving target, the recommended code may not be as bulletproof as it once was.

Yup - I caught that too, which is what prompted my question.

To add even more to the mix, I've setup CloudFlare as my caching service. It's great. I also notice it's causing some funny interactions with htaccess. I had written hotlinking protection into htaccess and it was being ignored. I then found out CloudFlare has its own hotlink protection.

I'll dig some more and update this thread.

#133 Re: Backlight Support » The Special {LUA=...} Token » 2017-11-13 14:36:31

Ben wrote:

1. Issues may be catatalog-specific.  Try checking the catalog's integrity and optimising the catalogue.  If that doesn't help, try publishing from a different catalog.

Yup, did all that already and a few similar ideas along that line.

Ben wrote:

2. If that doesn't correct the problem, then try to see whether trashing your preferences helps.  This can fix various LR issues, even if they seem completely unrelated to the preferences.

Whoa! Deleting preferences and then publishing worked! WTF?!

Write that down!

#134 Re: Backlight Support » Wordpress » 2017-11-13 14:19:36

robertmecaj wrote:

I just wish a system this difficult to integrate would come with remote support.

I hear you Robert. I'd like to help. Any and all web sites can be intimidating. Start where you are. What do you want?

#135 Backlight Support » htaccess and WordPress page » 2017-11-12 10:36:20

JimR
Replies: 1

I have Backlight and the WordPress theme. I've got an about page created in WordPress, that's a sub-page of my photos directory. Here's the structure.

/photos/ <- albums created by Backlight
/photos/album1/
/photos/album2/
/photos/album3/
/photos/album.../
/photos/about-my-photography/ <- page created in WordPress

I have a dummy page in WordPress at /photos/ and it's completely replaced by Backlight. The only reason I have the dummy page is to set it as the parent of the About page.

So in WordPress i have a page About My Photography and its parent is Photos (all within WordPress).

If I include the Backlight /photos/.htaccess file, going to /photos/about-my-photography/ generates a 404 error.

If I delete or rename the htaccess file, the URL works. Actually, everything seems to work without the htaccess file.

I tried deleting several lines in the Backlight htaccess file to see which one(s) are causing the problem, but it seems it's all or nothing. Even when the entire htaccess file is just this, it fails.

<IfModule mod_rewrite.c>
	RewriteEngine On
</IfModule>

So it seems I need to add a rule. I'm not sure how WordPress creates pages for directories and where to locate the source.

What do I need the htaccess file for?
How do I prevent it from blocking access to /photos/about-my-photography/? Or in other words, what rule do I add to /photos/.htaccess to allow for /photos/about-my-photography/ ?

#136 Backlight Support » Hotlink prevention » 2017-11-12 06:12:45

JimR
Replies: 8

I get sites that are linking to my images, and I'd like to block this. Usually there's a cPanel to add hotlink protection. This simply writes a few rules into the htaccess file.

I was reading this article.  https://perishablepress.com/creating-th … -strategy/

I want to understand what potential conflicts with Backlight I could be creating by using hotlink protection.

I also created a 403 error page, and would like anyone hotlinking to get that permission error. Or I could create a custom image to replace targeted image (e.g. "no hotlinking allowed)

What's the best strategy, and the htaccess rules, for this?

#137 Re: Backlight Support » corrupt db? » 2017-11-12 05:50:26

I can't explain it. I tried replicating all the strange problems I was having originally, but now it's all working. I can't reproduce the duplicate albums, the failed deletions, etc. Everything is normal.

I can only say I was having a bad day with Lightroom. Seems it, Backlight, and my server were out of sync somehow.

I still suspect I have some oddities with htaccess, but will start a new thread for things as I find them.

Let's call this thread closed. I'd rather forget all this. I just gives me a headache, and I wasn't even drinking.

#138 Re: Backlight Support » The Special {LUA=...} Token » 2017-11-12 05:28:32

I tried everything I could think of, but any use of {LUA=...} causes Lightroom to hang. Even this simple example:

{LUA=Caption}

I experimented using a new test album with just two images.

The TTG log file is normal, but at the point where the image is to be uploaded the log stops (at the point where it hangs).

So I'm stuck. Nothing I've tried will get any use of LUA= to work. It always causes LR to hang during publish.

#139 Re: Backlight Support » Dual Masthead with Version 1.2.3 ? » 2017-11-09 16:12:47

dakota20 wrote:

Can anybody confirm this?

I'm finding problems. The first time I went to the home page, it work. Then I tried the Galleries but it crashed with a SQL error, and php dump. I refreshed the page and then it rendered correctly. Then I tried to go back to the home page and it wouldn't render. After that, none of the pages would render.

I think you're at something going wrong related to the server more so than Backlight.

Looking at my broswer's inspector, loading the home page got me this:

Failed to load resource: the server responded with a status of 500 (Internal Server Error) /backlight/publisher/resource.php?template=6&extension=css&name=style
Failed to load resource: the server responded with a status of 500 (Internal Server Error) foto.descan.com/
GET http://foto.descan.com/ 500 (Internal Server Error)

Eventually the server request timed out and I got this instead of your home page.

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

One more attempt to refresh the home page and I got this:

SQLSTATE[HY000]: General error: 10 disk I/O error sql: 'select * from settings where 1=1' params: array ( )|#0 /nhldata/872/164872/data/web/foto/htdocs/backlight/framework/dao/PdoExtended.php(540): PdoExtended->_throwSqlQueryException('select * from s...', Array, 'SQLSTATE[HY000]...') #1 /nhldata/872/164872/data/web/foto/htdocs/backlight/framework/dao/PdoExtended.php(156): PdoExtended->_prepareAndExecuteSqlQuery('select * from s...', Array) #2 /nhldata/872/164872/data/web/foto/htdocs/backlight/framework/dao/GenericSettingsDAO.php(32): PdoExtended->selectRows('select * from s...', Array) #3 /nhldata/872/164872/data/web/foto/htdocs/backlight/designer/application/helpers/ApplicationConfigManager.php(10): GenericSettingsDAO->getData(Object(ApplicationConfigManager)) #4 /nhldata/872/164872/data/web/foto/htdocs/backlight/designer/application/helpers/ApplicationHelper.php(26): ApplicationConfigManager->__construct(Object(SettingsDAO), Array) #5 /nhldata/872/164872/data/web/foto/htdocs/backlight/framework/helpers/GenericApplicationHelper.php(28): ApplicationHelper->createConfigManager() #6 /nhldata/872/164872/data/web/foto/htdocs/backlight/designer/application/init.php(9): GenericApplicationHelper->getConfigManager() #7 /nhldata/872/164872/data/web/foto/htdocs/backlight/framework/init.php(144): require_once('/nhldata/872/16...') #8 /nhldata/872/164872/data/web/foto/htdocs/index.php(19): require_once('/nhldata/872/16...') #9 {main}|URL: /index.php

One more attempt to refresh the home page and I got the top banner, menus, and part of the main content. But it still timed out.

One more attempt (the fifth?) and the home page rendered completely and in normal time.

#140 Re: Backlight Support » Using Backlight Galleries to Manage Wordpress Images » 2017-11-09 15:55:57

WordPress has long suffered from a weak media library. After millions of users and many years, it's still weak. The Wordpress media library and database are something I've learned to avoid for my photos. The biggest category of Wordpress plugins I have is to deal with its media library. It's its own world, and nothing I've seen integrates with it.

If you have some specific questions, or could add more details about your idea, I might have some suggestions.

#141 Re: Backlight Support » Wordpress » 2017-11-09 15:49:47

robertmecaj wrote:

I'm a novice when it comes to developing this so I wonder if you could help me set up backlight as a separate page where I can create a link from my current site to a dedicated directory in my website.

Robert,

Yes, you can do all you ask about and more. I have Backlight and the Wordpress theme. The site's design is done in Backlight, and it will export the design for you to use in Wordpress.

Once you have the site designed, you'll only need to go to Wordpress to add a non-photo page, write blog posts, etc. You'll manage all your photos from LightRoom.

You're doing something similar to what I've done. I have all my publically published photos in a single location. I have a few private sections in their own directories, including one for client proofs. You have the option for making those password protected if you wish.

For client proofs I use the fantastic Client Response add-on. I also have a couple other private sections that are only available by invitation. There's the Cart add-on where you can setup images to sell.

There's the new Backlight web pages for administration, replacing the cumbersome method previously used within Lightroom's web module.

Once the site's design is complete, all of your photo management can be done within Lightroom. I have well over 100 galleries/directories, and each of them have 10-100 photos in them. All of that is being managed entirely within Lightroom by clicking and dragging images.

How easy or difficult all this is depends on your level of skill. If you wrote your current site in HTML, you should have enough knowledge to complete it. Getting a basic Wordpress site built is pretty straightforward. Designing your Backlight pages is even easier, especially if you know HTML and CSS.

I think the answer to how difficult this is really comes down to how well you understand web servers, browsers, and HTML. Understanding that will be a big help. Most of the grief comes as a result of venturing off the well-trodden path. If you're skilled enough you can do compelling and creative things.

There's plenty of people here to provide help, and I'll keep my eye out for your questions too.

I've nearly completed my own site which is very close to what you're asking for. I'd like to off load some of the great effort by the moderators. They've helped me over the years! I've been using TTG since the first release. I tend to dig deeper that most, and get into far corners wink I'm anxious to finish a few final pieces and show off my new site.

#142 Re: Backlight Support » corrupt db? » 2017-11-08 09:56:34

Ben wrote:

Hi Jim, it does sound like you're on Apache then.  Do you think you could find a steps that can be easily reproduced?  That would help make it straightforward to diagnose.

Understood. I need to step away for today. I've gotten myself too confused, and will approach it with a fresh start. Too much banging my head on the desk for one day.

Something in the Backlight htaccess files are causing some problems. But I don't think that explains the problems with trying to create/delete albums in LR, such as getting one album creating multiple directories (e.g. test, test1, test2...) and then when deleting that album seeing errors in LR. Then going to Backlight to find the odd series of albums, deleting them, and then finding they still exist while browsing with FTP.

I don't think that's htaccess, but let me clean up today's mess and find a straightforward problem to describe.


I just found this page, http://backlight.theturninggate.net/doc … cess_files

That helped explain a couple things, but there's still a big mystery going on.

#143 Re: Backlight Support » corrupt db? » 2017-11-08 09:38:43

Ben wrote:

As we don't provide support for nginx

Understood. There's just something really strange going on. And the more I poke around, the more strange it gets.

I contacted my host's sr technical staff and they tell me it's pretty much an Apache server. They have Nginx running as a proxy for static caching, antibot, and other things. It should just be a normal Apache server. The htaccess files are supported too.

And there's something odd about the htaccess files. I'm findin if I just delete them, things start working (or at least somethings start working).

I think I'm also running into conflicts with the anti hotlinking protection in the cpanel, as well as with the iThemes Security WP plugin. Both of those are writing rules into htaccess.

Let me try and get things clean up as much as possible. Then try to find a basic failure. Right now I think i've gotten myself tied in knots.

Still, there is something really strange going on and I'll need help, once I can clean things up.

One thing for the time being, where can I learn about what Backlight wants in the htaccess file? Which directories does it want to find this?

I migrated from CE4 to Backlight, keeping all my directories. I wonder if older htaccess files/rules are causing conflicts.

#144 Re: Backlight Support » corrupt db? » 2017-11-08 07:01:09

Wow - I just noticed another thing

All those test albums I created are directories still sitting on my server. That's ever LR failed to delete them, and I went into Backlight admin and deleted them. Backlight no longer shows them but looking with my FTP client I find the directories, and all their contents, are still there. That explains some of the strangeness, like why LR was creating slugs like test1, test2, test3, etc.

Now I'm wondering if some/all of the problems I'm seeing are due to Nginx.

#145 Re: Backlight Support » corrupt db? » 2017-11-08 06:33:39

Hmm, I just saw the note about Backroom and Nginx. Indeed my server is running Nginx, and I'm wondering if my strangeness is related.

The docs for adding the Nginx code doesn't explain where to add that code, or exactly how to add it.

Another thing that has me confused is how there are .htaccess files in several directories, but I thought Nginx didn't use them. Yet when I ask my hosting service's tech support how to add the configuration code for Nginx I was told to add it to my .htaccess file.

I had another strange problem where my WordPress page (about my photos) wouldn't appear under my Photos directory. Photos is controlled by Backllight (templates, album sets, albums, and photos), while the WordPress about page is generated by WordPress. I was getting a 404 error that I couldn't explain. Then I found that if I deleted the .htaccess in /photos/ it all worked.

So now I'm further down the rabbit hole, asking about .htaccess files on my Nginx installation and if they have anything to do with Backlight. If so, where do I go next to understand how to get Backlight working on my Nginx server.

UPDATE: consulting with my hosting service about their Nginx I'm told it's Nginx on top of Apache (acting as a proxy). They do support htaccess files. So everything in htaccess should work. Still, I'm finding problems and when I delete the Backlight rules from htaccess it solves mysterious problems. All I can say right now is something in htaccess generated by Backlight is causing problems.

#146 Backlight Support » corrupt db? » 2017-11-08 06:19:08

JimR
Replies: 10

There's something strange going on. I'll create a new album "Test" in an existing publisher instance within LR, adding 3 photos. When I publish it, I end up with a set of Test albums, Test, Test1, Test2.

When I try to delete the Test albume in LR, it generates an error saying LR could not be deleted from the service.

Checking on the web site, sure enough the three albums are still there.

Checking in the web site's Publisher admin page, Backlight > Publisher> Top-level Galleries, sure enough there are three albums called Test only one of them contains photos.

The first one, "Test" is the slug, does not photos. Test1 also did not, but I found the photos in Test2.

I tried creating a new Publisher instance in LR, and one album with two photos. After publishing that, I found two albums at the location on the web site. The first album at slug Test had no photos. The second album with the same name was at slug Test1 and contained the two photos.

Again, deleting the album in LR also generated the error the it could not be deleted from the service.

Attempting to remove the publisher instance in LR fails, or at least it did the first three times I tried. Closing the LR Publishing Manager dialog and then trying to delete the instance a fourth time worked.

I then quit LR and restarted. Created a new TTG publisher instance, and added a couple photos to the default album. Tried to publish this, but it hangs. I suspect it's the same bug I'm running into with my LUA script, but I can't explain how/why it didn't hang before I restarted.

So I delete the LUA script from the template in Backlight. Restart LR and attempt to publish. This time LR completes with no errors. I go to Backlight and find the new top level gallery containing one album, with two photos. Yet when I view the album there's only one photo.

Going back to LR I do see there are the two photos in the test album. I click on the one within LR of the missing one on the web page, and choose "go to published photo." it takes me to the right album, but the photo is still missing. Going back to LR the missing photo is now marked as modified to be re-published.

This problem of photos I've just published jumping back to being flagged as modified to be re-published is happening in other albums. Also I have one album "Patterns" where if I click "go to published photo" it always takes me to the wrong album on the site, within the "Places" album (instead of Patterns).


It's all really strange.

I found this after trying to debug the LUA problem. I should also note that I ran into some really odd problems while migrating all my albums from CE4 to Backlight. Lots of albums and slugs were strange. I also found albums in the wrong sets. Lots of strange things.


I have over 100 albums, and they average over a dozen images in each album. Re-building all of this would be a major undertaking.

So I'm wondering if my database and/or sync between LR and Backlight on my server has been corrupted, and how to fix it.

Where do I begin to fix the problems?

#147 Re: Backlight Support » The Special {LUA=...} Token » 2017-11-07 01:23:18

Ben wrote:

We have the ttg.log

I forgot about that file. Looking in it just now, wow, it contains nearly half a million lines! It's well over 100MB. 80,000 lines from just this year, mostly while developing with Backlight.

I've been a TTG user for many years wink


Let me see if I can get any further or flush out any details. I really do want the LUA code working. I can't think of a good workaround to what I had in CE4.

#148 Backlight Support » Tip: Iconic album set with descriptions » 2017-11-06 15:46:15

JimR
Replies: 1

I'm using an Album set with the iconic layout. I added descriptions and found the icons would "bump" up in their row to give the description room. This really throws off the nice visual layout. Ideally the default should be that all the icons align at their tops, and allow the descriptions to fall below.

Consider this example...

Iconic album set, with a dozen albums. Each one has a title, and only some have a description. Maybe some have a one line description, but some have two.

The ones with no description "drop" to the bottom in their row. The ones with a description "bump" up in their row. The visual is that each thumbnail is at a different vertical location in their row, causing the row to appear uneven. It's the added height of the description causing the icon to "bump" up in its row.

What's happening is each "figure" (which is the icon, title, and description) is aligned in the row by their bottom. The description add more height to the entire figure, causing the icon to "bump" up in it's row. The better visual is if all the icons were aligned in the row along their tops. This way, all the album's icons, including the ones with descriptions, are all aligned horizontally in their row. Much better visually.

Turns out it's easy to do. I think this should be the default behavior.

.albums-iconic figure {
    vertical-align: top;
}

The image below shows the same row before, and after aligning the figure's tops.

row

#149 Re: Backlight Support » The Special {LUA=...} Token » 2017-11-06 14:23:40

Ben wrote:

That raises the question of why it hangs for you under Backlight while it worked under CE4.  I tested under LR Classic 7 on a Mac.

Hmm. Curious. I verified it does hang LR for me, where I have to restart LR to publish anything after attempting that LUA script. I also have LR Classic 7.

Where to go from here? Is there a cache to clear? Some way to debug this? A log file to generate?

#150 Re: Backlight Support » WordPress theme: how to suppress Google Analytics tracking code » 2017-11-06 09:12:08

D'oh! I found it.

WordPress admin for setting the theme.

Custom Settings panel

"Google Analytics, as set in Backlight"

Board footer

Powered by FluxBB