Support community for TTG plugins and products.
NOTICE
The Turning Gate's Community has moved to a new home, at https://discourse.theturninggate.net.
This forum is now closed, and exists here as a read-only archive.
You are not logged in.
This is almost exactly what my files look like.
There is one thing still which I am not completely sure about yet:
When I try to edit a post in a browser while wathing the console, I see a 404 error for the GET on
https://fotos.michilge.de/blog/wp-content/themes/BacklightReseda-child/style_admin.css?ver=4.7I tried to enqueue that in this way:
wp_enqueue_style( $parent_style,
get_template_directory_uri() . '/style.css',
get_template_directory_uri() . '/style_admin.css'
);But that didn't do the trick.
For the moment I simply copied the style_admin.css from the Backlight Theme folder to the child theme folder.
But I am quite certain that is not the way it should be done since the file might be changed in the parent theme.
Hi and a good new year!
But the way it is, we can put hidden albums in any set.
That's fine. Isn't it?
When I copied my LR catalogs to a new computer last week, I also did not see my published albums first. I took some care to set up my publisher instance first. I then copied the catalog with all my dngs and synchronized the published collections with AlloySoft's LR Voyager plugin. Nevertheless I did not find the published albums and album sets until I created the first album on the new installation. As soon as I saved the settings for that new catalog, all the others appeared. It seems to me as if that event triggered the Publisher plugin to either sync with the server or to rebuild the tree from the catalog.
You wrote You have been alerted about an album already existing on the server side. Have You tried creating an uploading a new one?
Best wishes
Michael
Exactly.
Plus there are several instances in content.php where the theme name must be changed to the name of the child theme to prevent functions from being void. I will post a writeup with source code to round up this thread as soon as I get on a computer with a keyboard and rename the thread title to something related to child theme creation.
Hello Rod,
I originally started this post to ask further questions, but describing what I tried so far helped me find my mistake.
What's left is to say Thank You.
Yours
Michael
Is there a way to do that with Backlight Theme for Wordpress?
Thanks in advance
Michael
I'm not yet sure what hjaerta.se is going to need and be, but let me com back to Your first post in this thread and give you some input.
At the moment You have a link to the customer area on top of your entry page.
From there it goes directly to the password entry.
You could point the link to your customer zone to an album set first.
This album set can contain albums one for each customer.
And it offers more options to provide Information since album sets have a main copy area.
Each album in the set can display a thumbnail. If the customers don't want one of thier photos disclosed, just upload their brand logo and set that as thumbnail.
These albums are configured as CRG albums.
The password page appears after the customers click on their album.
If You have customers who do not want others to know that You work for them, You can pick the option "Hide from Album Set" in LR when You create the album.
Downside is, You will have to give a special link to those customers bringing them directly to their CRG album.
But the visible album of the customers serves as a reference for Your company. When working for corporate customers that might not be a bad idea.
If You have customers for whom You do several jobs in parallel, You can give them separate CRG albums for each job. You can even use another album set to bundle multiple CRG Albums for one customer.
Album Template >> Large Image Presentation >> UI Backgraound Colour and if neccessary Overlay Colour
I believe it's the Navigation, Header section of Your Page Template -- Menu Items
If You create and send me a login for that page I can tell for sure.
But give it a try first.
If you find the layout of the login page less appealing than desired, I believe, there is another way which I will test and write up as soon as I get my hands on a computer.
I just dont under stand the correlation between all these things???
A page template describes properties like typography and appearance of pages.
It can be assigned to
- album templates
- album set templates
- theme templates (if you use the Backlight WP-theme)
- backlight pages
An album is what You publish from LR with help of Publisher an populate with photos for there.
An Album Set is what You create and publish from LR to put either albums or other album sets or both in.
An Album Template accepts the assignment of a previously prepared Page Template and allows some adjustments on how the images that will be put into it later from LR will be presented.
An Album Set Template more or less does the same but for Album Sets.
And a Backlight Page is a (static) page You can populate with content from the Backlight frontend.
You can have multiple Album Templates all referencing one and the same page template.
In LR You create a new album or edit an exiting one.
The Publisher will speak to the server and ask Backlight, which Album Sets are available on the server side.
You pick one from the dropdown list in LRs "Create Album" dialogue.
Then that album template will be applied to that album. There are some other things You can enter in LR.When You're ready, The whole thing gets uploaded.
When You don't like the look anymore, You modify Your Page Template.
Clear the Template cache and the change in appearance is in effect for all Albums referencing that Page Template. No need to republish.
If You don't want to change the look of the whole site, but would like to create a new look for the next Album, You create a new Page Template either from scratch or by duplicating an modifying an existing one.
You then create a new Album Template (again either from scratch or by duplication), assign that new Page Template to it and will find the new option in LR as soon as You create a new album there.
What remains up to You is plan ahead what You will need:
- 1 column pages, 2 column pages for albums, special 2 column page for the blog, different colour schemes for different pages to refer to various thematic aspects or to support viewer orientation
- different types of albums with different behaviour with metadata displayed or without.
- different types of album sets perhaps behavin equally but with a different colour scheme.
When finsihed with planning I recomend developing a naming convention to support Your orientation when You revisit the working site after a while.
For example If I have an Album Template "Reseda A Mas oN oMD oDL" that means to me
- colour scheme based on reseda green
- it is an Album Template
- style is Masonry (not Classic= CL)
- no numbers for Thumbnails
- no metadata displayed with the thumbnails
- no download in higher resolution available
That naming scheme will help You in LR later. Typically once You're done with configuration in Backlight, You will look at it mostly from the LR side when You create and publish new albums. If You have multiple templates, You will want to tell one from another.
Hope that helps a little.
Edit: You should also know that the Main Copy and Tray Copy content in Album Templates or Album Set Templates can be overridden from LR. Think of it as a fallback. My Album Templates all have a Main Copy "I hope the Photos speak for themselves."
@ Rod: If You find some of this helpful for a more elaborate explanation, feel free to take.
Cheers, Michael
I don't have that impression.
There have been some things I did not understand immediately. But the community ist great. There has not been a single problem that has not been solved in reasonable time.
For the manpower available Matt an Ben deliver a complex piece of software and are always helpful. TTG is not a company like Adobe who can throw a whole team at pre launch documentation and expect return on that investment during the first year.
I love what I got here.
Cheers
Michael
originally it is not meant to be reopened, but to be configured in the desired way from the start.
If You have a sort of client paying You 50€ for a session with 3 Prints included, You would like the feedback to be closed to avoid ambiguity in the prints they actually ordered.
If you have a client, for whom You do a complex job that requires continuous communication, You can leave the Feedback open.
In Client Response Settings You find the "Post Submission Actions" setting. If You choose "Clear Feedback in Browser", the Feedback will not be closed. The client may enter another feedback in another session.
Perhaps it is a language matter.
I also have trouble understanding even basic information when I concentrate hard on a subject.
Do You speak and understand german?
Be assured. Client Response Module is made exactly for what You want to achieve. :-)
What I also had to do was touching the masthead image and other images on my static Backlight pages.
Thsi means logging into Backlight via a https-connection, go to the masthead section of my templates, choose the masthead file from the dropdown list containing the uploaded files and save. Clear the template cache of course.
Reloading the Gallery in another browser window will now result in loading the identity plate via https.
Hello again,
I have a feature proposal for futer releases concerning sitemaps.
Some of us combine a WP blog with galleries managed by backlight.
For WP there are plugins that generate sitemaps dynamically whenever there is new content in the blog.
I found a popular one that can also generate subsitemaps and even include external URLs: https://wordpress.org/plugins/google-sitemap-generator/
With a rewrite rule in .htaccess it can even make the sitemap.xml available in the site root while WP sits in a /blog/ subdir.
With a large number of backlight galleries it gets tedious to enter all gallery URLs into the plugin configuration dialogue.
But as external URLs can be entered, it should be possible to add the path to another .xml file containing entries for all the galleries. I believe Publisher and Backlight to have (nearly) all the information required to build it. It could be updated whenever a gallery is added or changed. The filename could be configurable. If the file is named sitemap.xml it would serve as a standalone sitemap for the galleries and backlight pages. If it is given another name, it could be given to the sitemap plugin to be combinde with the WP sitemap.
Would that be worth the effort?
After having looked at external generators I like the idea of being able to manage the sitemap generation on the own site.
I wish You all a good time over the holidays.
Kindest regards
Michael
Update: After some research I added this to my .htaccess file:
RewriteCond %{SERVER_PORT} !^443$
RewriteRule (.*) https://%{HTTP_HOST}/$1 [R=301,L]
Intention is to avoid
- that content will be seen double by search engine crawlers which is said to have negative influence on rankings
- that content can be accessed unencrypted at all
Any thoughts on that?
Hello Rod,
You were quick, but I was quicker ;-) See my edit above.
What's left is edit my custom.css itself, but the ftp-server won't let me access fron this computer.
Thank You!
Michael
Hello community,
my hosting provider talked me into investing in a certificate which I delayed until now fearing the hassle of transition.
Now it has happened.
What are the places I have to touch?
I already changed may backlight settings, site settings in Wordpress, the typography section of all my templates for the url of locally hosted fonts. I cleared the template cache and exported the WP-Theme to wordpress after changing the url to the fonts.
For good measure I activated a standard WP-theme and switched back to my Backlight theme.
When I view a page from my WP blog, my site is still marked as partly insecure by firefox. When I look at the page source in firefox, the links to my custom.css and font-awesome.css still are http-links.
On gallery pages everything is fine.
Can I help myself with a rewrite rule?
Is that good practice?
And if yes, how is that done?
My site is at https://fotos.michilge.de/blog
Thank You in advance.
Best wishes to everybody
Michael
Edit: I believe, I could clear most of my problems by logging out of backlight admin, logging in again via a https-URL, touching my default menu and exporting the WP-theme once again.
Oh yeah. Not closing html-tags in the copy area can make you sweat. Try a font awesome icon without the </i> to have some fun. If you don't find it, do as Rod offered. :-)
You have to find out, which album template is assigned to the galleries page. That album template refers to a page template. When you open this page template in the designer, you can edit the font color there.
The plugin may very well be from a third party author, but the adress is http://s3.amazonaws.com/cdn.knightlab.c … xtapose.js
which looks like the juxtapose authors put that up there.
Anyway, I like the way You chose better. Also avoids the risk that the cloud hosted version changes in a way that won't work with Backlight.
Having tried the juxtapose plugin for Wordpress I must say that I would appreciate if the [juxtapose]-shortcode would be integrated into the Backlight-WP-Theme someday.
My test post with a juxtapose image pair loads the files juxtapose.js and juxtapose.css from the cloud. Not only s3.amazonaws.com takes surprisingly long to deliver the bits, I generally prefer self hosted files especially when it comes to active content like scripts.
That is to be solved in Wordpress. When You edit the post, You can add multiple images to the post and integrate the into the text flow. One image can be qualified as the featured image of the post. This one will appear on the starting page of Your Wordpress blog within the abstract of the respective post. I'm not sure, how the corresponding settin in the editor is named in english. But it is a separate function in the editor.
There also is a possibility to make Wordpress scroll endlessly through the fulltext of all articles. But afaik You need a special Wordpress plugin for that.