Community @ The Turning Gate

We've done that. See Ben's reply above.

There's just the one cookie, and it's mandatory.

You may create a page via the usual means in Backlight, and link to it from your cookie notice.

Is this suggesting that the first page a person sees on visiting a site should be a cookie acceptance form, rather than the site's own home page?

No other cookies should be enabled unless the user logs into the site with a user account, or they begin to interact with Client Response or Cart-enabled galleries.

That would be only orders placed via the cart, or feedback received via client response. Both of which the site owner can delete via Backlight's admin.

Again, there is only one cookie and it's mandatory. If a visitor would like to have their purchase history or client feedback purged, then they should reach out to the photographer, or you can create a special page with a contact form, again in the usual Backlight ways.

I don't imagine you can delete records of orders, though, as that would impact your ability to report taxes. And client response feedback only has the person's name and email address as a means to facilitating communication, and stores no personal information.

There is no data, apart from what we have described above.

What I just said. Also, see Ben's comment above about session expiry.

----

So, correct me if I am misunderstanding, but it seems to me there's not much for us to do here. The bulk of the onus for cookie responsibility falls on the site owner, and them having to be aware of what else is going on on their site regarding cookies. As I've described previously, Google, WordPress, and other third-party services are not something we have control over insofar as cookies being a thing.

Looks great. I wish the images were larger in the gallery, but if the printed pages were all you had access to, then good enough. Mostly, happy to hear she's so thrilled with the result.

I've created a new page of documentation based on this conversation:
http://backlight.theturninggate.net/doc … _backlight

I think just about any third-party service does. This is one of the many reasons the EU regulations are utterly daft. Well intentioned, but daft.

If you use Google Analytics, Google Maps, reCaptcha, Fotomoto, PayPal, a third-party hit counter, etc. Wordpress does whatever it does; and its plugins do still more. The very popular Jetpack plugin that I keep telling people to stop using is a privacy nightmare.

Use just about any online software or service, you are taking on cookies. That doesn't mean they're up to no good; without cookies, the services literally would not function. Often times, the cookies are a part of authentication -- ensuring that you are actually you from page to page, view to view, and for every API call -- security, for your protection. That makes them a good thing.

There's nothing odd about it. Mobile file systems are not the same as desktop file systems, and so downloads are tricky business.

Nonetheless, we have devised a solution and it will be rolled out in our next release.

Wordpress users should also be aware that Wordpress does its own thing with cookies -- more or less, depending on what plugins you've installed -- that are entirely out of our hands, even when using the Backlight WP Theme.

The implication here is unclear to me.

Google Analytics is opt-in by providing your API key in Backlight's settings. I don't think that Backlight or TTG are responsible for individuals' use of Google Analytics. That data collection is between the user, and Google.

For anyone for whom this is an issue, don't enable Google Analytics, yeah?

You can combine media queries much as you like, if they're using the same values. But really, 174 lines of CSS is not cause for alarm.

We also have some documentation around managed albums, here:
http://backlight.theturninggate.net/doc … ged_albums

Worth reading if you haven't seen it.

I would do it maybe like this, then use custom CSS to correct the padding, spacing and borders.

<div id="main-copy-credits">
<p>Texte de  VOLTAIRE</p>
<table>
	<tbody>

		<tr>
			<td>Mise en scène:</td>
			<td>ALICE RONFARD</td>
		</tr>		

		<tr>
			<td>Décor:</td>
			<td>DANIÈLE LÉVESQUE</td>
		</tr>		

		<tr>
			<td>Éclairages:</td>
			<td>CÉDRIC DELORME-BOUCHARD</td>
		</tr>		

		<tr>
			<td>Costumes:</td>
			<td>MARIE CHANTAL</td>
		</tr>		

		<tr>
			<td></td>
			<td>VAILLANCOURT</td>
		</tr>		

	</tbody>

</table>
<p>Du 11 septembre au 6 octobre 2018</p>
</div>

Grr. Jetpack.

I'm implementing a custom field for IMG alt attribute. Accepts tokens in the same way as other, similar areas. Falls back on file name if set OFF, or is empty.