Community @ The Turning Gate

If I had it in my custom.css within the backlight tree, that would be right as long custom.css is activated.

I could probably rely on future updates or reinstallations not to do harm to the /backlight/custom tree, but somehow I tended to put it outside.

Yes,  indeed. It's as open and straightforward as I had hoped it would be. The only thing to keep in mind is to notice if the stylesheet provided with the fonts uses numbers to specify font-weight or elsewise needs modification.

I just managed to use self hosted webfonts with backlight

This is how:
I created a directory outside the Backlight hierarchy (actually in the root of my site where the folder "backlight" also lies) and put the CSS with the webfont definitions there. In this directory I also created a subdir named "fonts" where I put my eot, woff, woff2 and ttf files.
In the "Google Fonts Statement" field of my templates I entered a link to this local stylesheet

<link href="http://fotos.michilge.de/mhfonts/latolatinfonts_mh.css" rel="stylesheet" type='text/css'>

I edited the stylesheet that came with my fontpackage to contain only the variations I really want to use and changed the property "font-weight" according to the convention followed by google fonts from something like "font-weight: bold;" to "font-weight: 700;" and so on since the numerical weights is what I can choose in backlight.

A sample declaration from my Stylesheet would be:

/* Webfont: LatoLatin-Regular */@font-face {
    font-family: 'LatoLatinWeb';
    src: url('fonts/LatoLatin-Regular.eot'); /* IE9 Compat Modes */
    src: url('fonts/LatoLatin-Regular.eot?#iefix') format('embedded-opentype'), /* IE6-IE8 */
         url('fonts/LatoLatin-Regular.woff2') format('woff2'), /* Modern Browsers */
         url('fonts/LatoLatin-Regular.woff') format('woff'), /* Modern Browsers */
         url('fonts/LatoLatin-Regular.ttf') format('truetype');
    font-style: normal;
    font-weight: 400;
    text-rendering: optimizeLegibility;
}

The field "Prepend Font-family w/" must contain the value of the "font-family"-property so in my case "LatoLatinWeb".

Why should one want this?
The font I use is not available via Google Fonts.
I have visitors concerned about their privacy who don't like google to get a call for the fonts with a referrer from the pages they view.

edit: Ah. Found this one http://rodbarbee.com/galleries/4-personal-favorites/

In my case it is not an album page but one of the pages designed with Designer >> Pages.

Users have been created and are underway by mail.

I'm experiencing the same problem.
When I set "Page URL Format" to "about" or "about/" and reload the page with the menu, I get a 404 error.
When I turn it back to "about.php" and reload the page with the menu again, my pages are found.

I did copy the .htaccess file to the directory my backlight/ and galleries/ reside in and also cleared my template cache after changing to "about".

It seems like You convinced Matthew to make a video ;-)

I just received the link and watched it.
http://theturninggate.net/2015/03/ce4-i … -to-video/

As a person who already went through all the steps mentioned with help of written documentation and advice from the community, I find it a helpful entry point into setup of a CE4 site. My compliments.

As CE4 is a complex system with to many possible combinations, to be covered in the sequential form of a video, I testify that the ttg community is what helped me most setting up my site.

Hi Rod,

Thank You for Your advice.
I should have done that earlier.

I just remembered that Matthew wrote something about that "no-conflict" keyword last spring when I had trouble with photoswipe in combination with that old GPX-Viewer.

I deactivated the no-conflict mode in that plugin already last year, but an update of the plugin introduced the same trouble again. I wasn't aware I updated that ...
Stupid me.

Sorry for bothering with the same cause again.

And Thank You again.
Michael

Hi Rod, hi Matthew,

thank You for Your quick response.

I did both of that. I made changes to the menu and saved, changed back and saved over.

The WP-Menu appears correctly in galleries, autoindex pages and even the newly installed CRG. So PHPlugins can be assumed to work.

It is strange only on WP pages. When viewed on the PC, the menu just lacks the lower levels. On handhelds the collapsed menu button won't expand anything, just move the page to top.

I looked into the browser console and it says:

TypeError: $ is not a function
http://fotos.michilge.de/blog/wp-content/themes/CE4WP310/lib/js/init.tail.min.js
Line 1

TypeError: $ is not a function
http://fotos.michilge.de/blog/
Line 950

TypeError: $ is not a function
http://fotos.michilge.de/blog/wp-content/themes/CE4WP310/lib/js/init.head.min.js?ver=4.1.1
Line 11

TypeError: $ is not a function
http://fotos.michilge.de/blog/wp-content/themes/CE4WP310/lib/js/init.defer.min.js
Line 2

I'm not experienced in Javascript. Is there further information I can provide?

Best wishes,
Michael

Hello Rolf,

did You check "Enable Password Protection" in Lightroom?
It's located in section "Ausgabeeinstellungen"

Concerning the other problem. Not sure how You got it. Tabs and spaces in connection with the proportional typeface may distort the levels in Your post. My directory structure is

ttg-be/templates/gallery
ttg-be/templates/autoindex

The autoindex templates can be edited when an album set is right-clicked "Album Set bearbeiten", while gallery templates require right-clicking on an album "Album bearbeiten"

Gruß aus Sprockhövel,
Michael

Hi Volker,

when You export Your CE4 Pages Output, look in the folder on Your local computer You just exported into.
There will be a subfolder "galleries" with a file gallery.xml. Ftp this to the galleries folder on the server and everything will be alright.

PS: I can't access Your site from here because the checkpoint firewall won't let me. I'll take a look as soon as I'm home.

Regards,
Michael