Community @ The Turning Gate

Your pano selector page uses full-sized images instead of smaller ones that are just 1000px wide. This slows down loading the images and doesn't really provide a benefit since clicking on an image shows your nice slider.

For album sets, try following:

.the__albumSet figure:hover {
    background-color: red;
}

There a global body classes that you can use to target a particular page, or pages using the same template, if needed.

Rod, CentOS is fine. It is a standard Linux distribution.

CE4 Publisher based site migration is built-in into Backlight! All albums and albums sets are migrated, same for the cart.

I don't see what is not responsive with the blog.

Generally, if there is an issue with Wp based pages, I would first disable all plugins and see if the issue persists (yep, clear template cache and browser cache, just to be safe)! If the issue still persists, report back, if the issue is solved, re-enable one plugin after the other (yep, same story about cache), and once the miss-behaving plugin is identified, report back.

Not that strange since you told it in your custom css file to be there!

.main__column > .content {
    left: 120px;
}

It works for me! But the image for the secondary header is big ~660k. It is too big for what it should be. It took a while on my phone to load it! I opened it in Ps and it shows as 16-bit. Once I cropped it to the text area and changed it to 8-bit, it comes in at 40k.

I have a function that is based on the same technique:

function page_match($gallery) {
   if (substr($_SERVER["REQUEST_URI"], 0, strlen($gallery)) == $gallery) {
      return 1;
   }  else {
      return 0;
   }
}

This function returns 1 for subpage matches too, eg, page_match('/blog'). This works well for my purpose.

But then it would be nice to have the twitter and open graph fields set as well.

Maybe the easiest might be to have a ttg_meta hook that can replace the default settings. This way one can target specific pages from phplugins and add whatever one desires.

Maybe even easier, if Backlight would not set empty fields, they could then be easily added with the existing ttg_head hook. I don't know what's happening if the same metadata field is set twice, first without content and then a second time with content.

You can have CE4 Publishing Services along Backlight Publishing Services. I have them as well. They both you the same TTG Publisher plugin.

Just curious, do you post from a laptop? If yes, it might be interesting if you went to an internet cafe and tried to post from there. This way you might circumvent GoDaddy's denial-of-service prevention for a bit by having a different IP address and likely a much slower connection.

This is what the readme.txt file has to say about that:

=== To update from earlier versions of Backlight+Pages to Backlight+Pages 1.2.3 Release 2: ====

	Follow upgrade instructions for 1.2.3 Release 1, below.