Community @ The Turning Gate

I think I've got it fixed now. At least, the Backlight Modules page appears to be working correctly for The Turning Gate's installation of Backlight.

Sorry for the inconvenience. I've been making some background changes with our domains.

Thanks, Jim. Probably a change we can effect in a future release.

Right. The docs are here if you need them:
http://backlight.theturninggate.net/doc … ge_support

We came up with this as the easiest solution, without having to lean on paid third-party localization services, etc.

Backlight is quite fast by default. Sounds like probably a server/hosting issue. Maybe temporary.

Sit in it for a day and see whether it improves. If not, this being a separate issue, please open a new thread. I’m closing this one as resolved.

Backlight is too small a thing to be targeted by hackers, and Ben happens to be very good at securing our back end. Likely Wordpress was the point of entry; Wordpress is one of the hottest targets for hacking, as prevalent as it is. You’d do well to ensure you’re up-to-date with the latest version of WP and whatever plugins you’re using, and you should look into some security focused plugins, such as Wordfence.

We have nothing to announce at this time.

In the past, major updates have released on cycles of roughly 18-to-24 months. You make take from that what you will.

As always, when announcements occur, the blog will be the first place to see them; blog posts are shared to social media, and announcements are then echoed via our newsletter.

Insofar as learning the software, Backlight 2 is a very good place to jump in. We like the paradigm now established, and we’re not keen to reinvent the animal.

FWIW, Lightroom has never been good at passing code through its metadata fields, and we've forever discouraged users trying to do this, specifically because it is not reliable. We can attempt to make certain allowances as we're able, but at the end of the day, Lightroom does what Lightroom does, and ¯\_(ツ)_/¯ ...

If at all possible, I advise trying to work out a more hardened solution, hopefully via PHPlugins. This is something that both you (the user) and we (the developers) have greater control over.

Watch those syntax errors. CSS doesn't like them at all. One missing semi-colon, or one set of braces unclosed, can break your entire stylesheet.

You might also be able to do something with PHPlugins to create a custom index that jumps out to you pano pages. This could get very involved and dynamic, or could just be an index built of static PHP that you keep up-to-date as you add new pages.

i can't remember what Backlight 1 uses. Backlight 2 implements v2 via the Settings page, so I'd try that.

Guys, hamburgers are gross and unsustainable. Backlight is environmentally neutral; it's a Pancake menu.

If you want it centered always, then you might try a full-screen design, and simply do not upscale the images.