Community @ The Turning Gate

Yes. The error said the same as the line from the log, just more nicely formatted.
Authentication between LR and publisher is fine btw.

Took me another 5 years to sign up. I'm kannznichkaufen

While I still like the workflow LR enables me to, I am not inclined to accept any subscription model. In the place where I live, I don't have the bandwidth to up- and download high resolution DNGs to whatever kind of cloud anyway. With less than 1 MBit/s cloud is not the way to go. Also as I strictly believe that in reality there is no such thing as a cloud, but only other people's/companies' computers, I will not give my assets out of my own hands but keep physical copies and backups where I can control them.

What I would like to have is a LR-independent client, that can
1. connect to my server side Backlight backend and sync back all it finds there to a local directory structure and
2. notice when in the local structure a new album is created and sync this addition up to the server.

Both together would also allow for a convenient backup of published galleries.

I care less if there will be a shiny user interface or if I will have to edit template text files with the properties of new albums and album sets.
I am glad, that You have announced to come up with something useful to support those of us who will have to break the bonds to LR at some point in time.
Everything You have published with in the past has turned out to be a pleasure to use and I am confident that this will be true in the future.

During the process of publishing the publisher plugin in LR creates jpgs and uploads those instead of whatever raw filetype you have.
You just create a new album with the publishing service and pull the thumbnails into that album.
Take a look at the settings of Your plugin. There are some options to set there (e.g. watermark in the exportes jpg)
Other settings are specific for the template used for the particular album (e.g. image size). Those are set in Backlight.

Hi Daniel,

no, I had not even thought in that direction yet. I'm not to good at css. So I don't get such an idea without initial help.

To understand You right, I would have to do the following:
1) publish the album, either set a slug or find out the slug created by publisher

2) upload a crafted background to backlight/custom/images/background-xxx.jpg and replace "xxx" with the album slug (or bring up another naming convention)

3) add a section .slug-xxx main{ } to my custom.css and replace the "xxx" with the album slug and adjust the url() to the uploaded image.

If the album gets unpublished, the entry in my custom.css wouldn't do harm.

That sounds convincing.

The "echo " was missing. I copied "echo _x" from the 'Search Blog' instance from further up in the file.

To confirm this precisely I now tried again, changed to "_e", exported the theme, cleared the cache and revisited the loco translate WP plugin. In the plugin I selected the Pangolin-Template to edit the .pot. When I made it sync with the source files, one unused string got removed from the template. After another change back to "_x", 'Search Albums' was found and added to the .pot again as a new string.

I had to make another change to make 'Search Albums' appear in the language template. It is now:

<button type="submit" class="fa_pseudo"><span><thp> echo _x( '<?php echo __c('TEXT_SEARCH_ALBUMS_BUTTON', 'Search Albums') ?>', 'submit button', '<?php echo $template->getIdentifier(); ?>' ); </thp></span></button>

To make this clear for other users, the change was made in the file backlight/modules/pangolin-wordpress/dynamic/view/searchform.php which is the pattern, backlight uses when the theme is exported to Wordpress.

Thank You
Michael

I tried again. It can stay "echo _x".

But I changed the plain words "Search Albums" to "<?php  echo __( 'Alben durchsuchen', 'pangolin-template' ); ?> " and translated again. The whole thing now reads as below.

Now I get the translated handoff string below the search input.

But when I reexport the theme from Backlight it will be overwritten.

<form role="search" method="get" class="search-form" action="<?php  echo esc_url( home_url( '/' ) ); ?>">
	<p>
	<label><span class="screen-reader-text"><?php  echo _x( 'Search for:', 'label', 'pangolin-template' ); ?></span></label>
	<input type="text" class="search-field" placeholder="<?php  echo esc_attr_x( 'Enter search, hit Return...', 'placeholder', 'pangolin-template' ); ?>" value="<?php  echo get_search_query(); ?>" name="s" />		
	</p>
	<button type="submit" class="fa_pseudo"><span><?php  echo _x( 'Search Blog', 'submit button', 'pangolin-template' ); ?></span></button>
</form>

<form role="search" action="/backlight/search" method="GET" class="search-handoff">
	<input type="hidden" id="q" name="q" value="" />
	<button type="submit" class="fa_pseudo"><span><?php  echo __( 'Search Albums', 'pangolin-template' ); ?></span></button>
</form>

<hr />

https://fotos.michilge.de/blog/kleine-gartenbastelei/

I'm using Firefox on phone and desktop.

Oops. I was to quick to say, I like it the way it is.
When the page is viewed on a phone or in a narrow window on the desktop, the social media icons in the top pallet are covered by the spinal column an are not reachable anymore.

I republished again, but this time with full image upload. --> Works!

edit: I also installed the update to 1.2.2 in the mean time.