Community @ The Turning Gate

Well, it does show side panels for me. So you most likely you just need to clear the browser cache.

Thank you! Do you do any file renaming when you publish?

Backlight > Cart > Settings

Previous post: I edited your reply to show the 'code' section.

Indeed, the background is controlled by lucnade.css, but the background-color section is not commented and has a different color to the one you showed above. Looks like you are looking at a different file. Have a look at /luc/backlight/custom/css/lucnade.css

        .pages-template-identifier-expos .the__copy>.content ,
        .pages-template-identifier-exhibitions .the__copy>.content {
		background-color: #A607A3; 
		border-radius: 0;
		box-shadow:2px 2px 8px #000000;
		width: 100%;
		max-width: 1440px;
		padding: 50px;
		font-size: 1.25rem;
		color: black;
	}

As shown in my previous response, you can have several selectors using the same CSS statements:

	.pages-template-identifier-expos .the__copy>.content ,
	.pages-template-identifier-exhibitions .the__copy>.content {
		background-color: #A607A3;
		border-radius: 0;
		box-shadow:2px 2px 8px #000000;
		width: 100%;
		max-width: 1440px;
		padding: 50px;
		font-size: 1.25rem;
		color: black;
	}	

Here you use the same CSS code for your french 'expo' page and the english 'exhibitions' page. You can do exactly the same for your en/theater and en/gallery-theater pages. So it is not necessary to have the same identifiers, although that might be helpful.

BTW, the image size doesn't look to make an obvious difference.

The custom.css files seem to differ... Is there a reason why you are not using the same for the two sites?

Yes, I can... was ist das Problem?

Hi Tom,

I forgot that Backlight puts everything possible into one CSS file. But this CSS file is template AND module specific. So the CSS for a page is different than that for an Album Set. That's why your background image is reloaded.

But, you could disable the background image in your page template and add following code it to your custom.css:

.background__image 
{
	background-attachment: scroll;
	background-image: url('http://ttg-test.tomswarbirds.com/backlight/designer/?c=page&a=image&p1=10&433');
	background-position: center center;
	background-repeat: repeat;
	background-size: contain;
}

Since the custom.css file is identical for all your pages and galleries, your background image is only downloaded once and then afterwards served from the cache.

Yep, pdo_sqlite is available now. Really cool to see backlight running on a raspberry pi! One of these days, I have to get one to play with

Have a look at http://backlight.danielleu.com/workshop. It is really easy to do and with some custom CSS you can get the look and feel you want.

<div class="grid_12"> 
	<div class="col_9">  
		<h2>Workshop XYZ</h2>
		Lorem ipsum dolor sit amet,....
	</div>

	<div class="col_3" >  
		<h3>More Infos</h3>
		Lorem ipsum dolor sit amet,... 
	</div>
</div>

And the custom.css:

@media screen and (min-width: 1024px) {	
	.slug-workshop .col_3 {
		box-shadow: -3px 0 3px -2px rgba(0,0,0,0.65);
	}
}

I use the slug 'workshop' for the workshop page. This way I can easily target my CSS for just this page and not affect anything else.

I think some of the users run into issues with batch update. I update one album at a time.

AFAIK, og:image is automatically set on album and album-set pages. It is set as well on regular pages as long as it contains an embedded gallery. There was discussion about this a while ago, but I can't find the thread. If you would like to have og:image populated on regular pages, you just have to include a gallery. If you assign a thumbnail, then I think it would not need to contain any images and therefore it is not visible.