Vegas slide show discrepancies

pideja · 2018-04-22 06:37:29

For reasons unknown to me, suddenly the Vegas slideshow display has gone wild:
On the English side it's ok, but on the French side, it's showing the images at twice the size intended.
I've checked both Backlight settings pages for differences but there are none. Both CSS files are identical.
I really can't find what has happened. The images are the same size save for one that's a tad smaller. Both Gallery pages where Published at almost the same time.

What am I missing?

pideja.ca/luc

rod barbee · 2018-04-22 07:14:43

the css files aren't exactly the same. In the French site you have, starting on line 40:

.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;
	}

that breaks the css for everything that comes after.

If you want that css applied to both templates, it should be written like this:

 .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;
	}

Daniel Leu · 2018-04-22 07:30:57

In the future, it would be helpful if you include links that show the issue. Currently, I'm looking at http://pideja.ca/luc/en/Gallery-theater/ and http://pideja.ca/luc/fr/theater/. Hope this is correct!

1) The size of the english images are 600x800 and the french are 450x600. So not exactly the same.
2) The css is not the same either.... and this is where the issue is coming from. I strongly would advocate you to use ONE common CSS. Rod already showed you how to do it. PLEASE do this now.

In the french CSS, you have

	 .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;
	}

but it should be

	.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;
	}

And with this code change, the CSS will work for both sites

pideja · 2018-04-22 07:58:31

I fully understand the idea of a single CSS file.

However, I fail to see how CSS code referencing the "Exhibitions" page should affect the "Gallery" page.

Also, I think I should at least have the identifiers the same: http://pideja.ca/luc/en/gallery-theater/ should read http://pideja.ca/luc/en/theater/ to be consistent with the French side, i.e. http://pideja.ca/luc/fr/theater/ but alas, Backlight won't let me.
Seems a page already has the same identifier.
There are already pages with the same identifier on both sides (about, contact) and it doesn't seem to pose a problem.

I will review the image sizes also.

Anyway, I'll start merging my CSS files tonight. Hope to be done and online by tomorrow.

Daniel Leu · 2018-04-22 08:36:10

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.

pideja · 2018-04-22 08:52:57

Trying out this php code that would lead to "lucnade.css"

// CUSTOM lucnade css
function ttg_head_end( $style, $path ) { 
	echo '
	<link rel="stylesheet" href="backlight/custom/css/lucnade.css" />
	';
} // END

lucnade.css is one of the two used by each side. Since it's all shared settings.
But the Prints/oeuvres pages use a slightly different CSS.

Think it will work?

Last edited by pideja (2018-04-22 09:01:18)

pideja · 2018-04-22 09:06:42

Well, tried and...no effect noticeable on the Gallery/galerie pages. The French "galerie" pages still shows extra big images.

I'll have to sleep on it.

rod barbee · 2018-04-22 09:15:05

pideja wrote:

Trying out this php code that would lead to "lucnade.css"
// CUSTOM lucnade css
function ttg_head_end( $style, $path ) { 
	echo '
	<link rel="stylesheet" href="backlight/custom/css/lucnade.css" />
	';
} // END
lucnade.css is one of the two used by each side. Since it's all shared settings.
But the Prints/oeuvres pages use a slightly different CSS.
Think it will work?

use the ttg_head hook. The ttg_head_end hook was from CE4 and won't work with Backlight.

rod barbee · 2018-04-22 09:19:31

pideja wrote:

However, I fail to see how CSS code referencing the "Exhibitions" page should affect the "Gallery" page.

If it's from the css above, it's probably because that css is malformed and breaking all the css that follows it.

Daniel Leu · 2018-04-22 18:45:17

The path to the CSS should be "/luc/backlight/custom/css/lucnade.css". And then you should disable the CSS file specified in Backlight too.

pideja · 2018-04-22 22:18:51

I've changed the php to read:

// CUSTOM lucnade css
function ttg_head( $style, $path ) { 
	echo '
	<link rel="stylesheet" href="/luc/backlight/custom/css/lucnade.css" />
	';
} // END

It is placed in pideja.ca/luc/backlight/custom/phplugin … ortail.php

I disabled all CSS in all the Pangolin Pages/Advanced Setup/Extensibility/Custom Style Sheet except for the gallery page which uses a different CSS. I will try to merge this CSS into the main one later.

I did this only on the English side in order to compare results.
At first glance: not much change. That is good, I assume.

But, there must be something in the CSS to be corrected because the font size is now smaller on the English side and the slideshow on the English side is now as big as the French side.

I'll have to check carefully what discrepancies there are between the English and French versions of the CSS I used before.

pideja · 2018-04-22 23:56:47

The text on http://pideja.ca/luc/fr/expos/ is as I want it: bigger and with a "beige" background where the text on http://pideja.ca/luc/en/exhibitions/ is smaller with a transparent background.

Both the CSS lodged in http://pideja.ca/luc/backlight/custom/css/lucnade.css used on the English side and the one used in the French version which is still is in Backlight/fr/custom/CSS. However, after comparing both versions, they are the same. Also, I checked the settings in Backlight/Pages/Content Area for disparities and they are identical.

Using the Inspector, I found that the code in the English version that the font size is smaller (1rem) :

.the__copy {
    font-size: 1rem;
    line-height: 1.5rem;
}

than on the French side (1.25rem)

But the CSS in the Home page (lucnade.CSS) and the one on the French side (luc-fr.CSS)and both indicate 1.25rem!

 .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;
	}

But, if I enable the original CSS in the English version with Backlight (luc-en.CSS) I'm back to the correct formating.

Last edited by pideja (2018-04-23 00:00:46)

rod barbee · 2018-04-23 01:21:15

the css files for those pages are still not exactly the same. the French version has one more line (see below).

the french version is coming from:
/luc/fr/backlight/custom/css/luc-fr.css

the english version from:
/luc/en/backlight/custom/css/luc-en.css

you're apparently not using the ttg_head hook to insert the same css file into both?
The phplugins file needs to be placed in each site's /backlight/custom/phplugins/ folder and you need to select it in each page template. Placing it where you have placed it does no good since you won't be able to select it in each site's page templates.

you still have this css in the french version starting on line 40 (the second line here is the one more line in the french version):

 .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;
	}

this is the problem:
.pages-template-identifier-expos .the__copy>.content {
.pages-template-identifier-exhibitions .the__copy>.content {

If you want the css to be applied to both the expos template and the the exhibitions template, the selectors need a comma between them, not a curly brace. The way it's written is breaking all the css that follows. This is what it should look like:

.pages-template-identifier-expos .the__copy>.content,
.pages-template-identifier-exhibitions .the__copy>.content {

rod barbee · 2018-04-23 01:35:31

pideja wrote:

I've changed the php to read:
// CUSTOM lucnade css
function ttg_head( $style, $path ) { 
	echo '
	<link rel="stylesheet" href="/luc/backlight/custom/css/lucnade.css" />
	';
} // END
It is placed in pideja.ca/luc/backlight/custom/phplugin … ortail.php

This won't work. You need to place it in each site's (EN and FR) /backlight/custom/phplugins/ folder and then select it in each page template under the Advanced Setup tab.
http://backlight.theturninggate.net/doc … _phplugins
And to be safe, you should use an absolute url:

as written, the browser is going to look in the root of each site as determined by the site urls you're using for the French and English sites.

pideja · 2018-04-23 03:00:23

Rod wrote:

the css files for those pages are still not exactly the same. the French version has one more line (see below).
the french version is coming from:
/luc/fr/backlight/custom/css/luc-fr.css
the english version from:
/luc/en/backlight/custom/css/luc-en.css

You are right, but it's only because I edited one of the files in order for it to be used in a single CSS for both the French and English sides.

Rod wrote:

you're apparently not using the ttg_head hook to insert the same css file into both?
The phplugins file needs to be placed in each site's /backlight/custom/phplugins/ folder and you need to select it in each page template. Placing it where you have placed it does no good since you won't be able to select it in each site's page templates.

Not knowing exactly where to place the PHP file and the new, unique CSS file that will be used by both sides of the site, I placed it the "portal" thinking it would then affect both sides.

Rod wrote:

This won't work. You need to place it in each site's (EN and FR) /backlight/custom/phplugins/ folder and then select it in each page template under the Advanced Setup tab.

So, if I understand correctly, I place a PHP file into each side in the Custom/PHP folder and then activate the PHP in each page template in the Advanced Setup tab. The CSS file refered to would be situated in the Home page custom folder: http://pideja.ca/luc/backlight/custom/css/lucnade.css

Am I still in the wilderness?

rod barbee · 2018-04-23 03:07:52

pideja wrote:

You are right, but it's only because I edited one of the files in order for it to be used in a single CSS for both the French and English sides.

But the problem is that the line you added is breaking everything that follows (see the highlight in red above)

pideja wrote:

Not knowing exactly where to place the PHP file and the new, unique CSS file that will be used by both sides of the site, I placed it the "portal" thinking it would then affect both sides.

phplugins files need to be in the backlight/custom/phplugins/ folder for the site that's using them.

pideja wrote:

So, if I understand correctly, I place a PHP file into each side in the Custom/PHP folder and then activate the PHP in each page template in the Advanced Setup tab. The CSS file refered to would be situated in the Home page custom folder: http://pideja.ca/luc/backlight/custom/css/lucnade.css

Yes, that should work.

pideja · 2018-04-23 03:14:40

I just finished placing the PHP file on both sides. I activated the PHP file in each page template's Advanced Setup tab. I also de-activated the CSS file where it still was activated in each page templates.

First glance conclusion: it seems to work, both sides being identical, even in their mistakes. The font-sizes are still too small (I'd prefer 1,25rem) and the images in the Vegas slideshow are still way to big. But, on the whole, it seems to work.

Still a lot of tweaking to do, I fear.

P.S. I edited that line in red as suggested by you. It now reads:

.pages-template-identifier-expos .the__copy>.content,
.pages-template-identifier-exhibitions .the__copy>.content {

Last edited by pideja (2018-04-23 03:18:28)

rod barbee · 2018-04-23 03:42:55

Something is still not right. Look at the top of each of those pages. See the text there? That's not supposed to be there.

How did you create your phplugins file? You should be using one of the sample files that Matt has provided in backlight/custom/phplugins/ and place your code in the User area. (the un-commented code at the top of the file is needed)

http://backlight.theturninggate.net/doc … _phplugins

the css file you want is still being called, it's just that it looks like you've simply added the code to the top of the page and that code is now visible. Just open one of the sample files, like phplugins-pangolin-sample.php and place your code below the area defined by the line: // SET USER FUNCTIONS BELOW

pideja · 2018-04-23 04:00:13

I changed the PHP file. I now use one based on the Pangolin model:

 <?php
function ttg_head( $style, $path ) { 
	echo '
	<link rel="stylesheet" href="http://pideja.ca/luc/backlight/custom/css/lucnade.css" />
	';
	
//END

No more text appears at the top of the pages.

And the site is down!

Last edited by pideja (2018-04-23 04:11:02)

pideja · 2018-04-23 04:25:25

Modified the PHP file:

<?php
/*
 *	TTG Core Elements "PHPlugins" User Hooks v1.2 - initialization mainline
 *
 *	developed by john bishop images (http://johnbishopimages.com)
 *	for Matthew Campagna of The Turning Gate (http://theturninggate.net)
 *
 */

function ttg_user_load( $style, $path ) {
	$g_tsvrl = explode( ' ', $style );                          // Extract gallery type
	define ( 'G_STYLE', strtoupper($g_tsvrl[1]) );              // and set global for later
	$g_path = str_ireplace('\\','/',$path);                     // change \ to / 
	$chunks = explode('/',$g_path);                             // and put into array
	define ( 'G_PATH', strtoupper($chunks[count($chunks)-2]) ); // gallery folder name is second to last
	//define ( 'TTG_SITE', '');                                   // set new site root for navigation, resources, etc.
	}
	
// END
/*
 *	
 *	*************************************************************************************
 *	*                                                                                   *
 *	* Warning! When using echo or print special care must be qiven to using quotes.     *
 *	*                                                                                   *
 *	* Strings inside single quotes must contain only double quotes                      *
 *	* or all single quotes must be escaped (ie \') or vice-versa                        *
 *	*                                                                                   *
 *	*************************************************************************************
 *	
 *	Fourteen user exits are defined in all web engines - all are optional 
 *		(i.e. ttg_user_load.php may be the only processing)
 *		
 *	Some web engines will have additional exits defined, specific to that gallery type
 *		
 *	Each is called with the same parameters:
 *		%1	-	TTG gallery-style gallery-release
 *				3 blank delimited values
 *				- %1.1	-	'TTG'
 *				- %1.2	-	string describing gallery type; no embedded blanks
 *				- %1.3	-	a series of two to three period delimited integers
 *							describing gallery release level; x.y or x.y.z
 *		%2	-	server filesystem file name and path of calling file
 *		
 *
 *	Defined exits:
 *
 *		ttg_user_load			
 *      - return value ignored
 *      - called immediately after this file returns
 *      - called before any output is produced
 *      - all header and response variables are accessible
 *      - cookie and session processing can be initialized
 *      - globals to be used by later hook calls can be defined 
 *
 *    ttg_head
 *      - return value ignored
 *      - called immediately before </head>
 *      - encompasses nothing; use to insert content into the <head>
 *
 *    ttg_header_top
 *      - if return=false, the contents of the normal Backlight header are skipped
 *      - called immediately within the header section
 *      - encompasses the full contents of the header section; can be used to replace those contents
 *
 *    ttg_header_bottom
 *      - return value ignored
 *      - called last in the header section
 *      - encompasses nothing; use to insert content at the end of the header section
 *
 *    ttg_masthead_primary_top
 *      - if return=false, normal Backlight masthead is skipped
 *      - called immediately before the masthead element
 *      - fully encompasses the masthead; can be used to replace it
 *
 *    ttg_masthead_primary_bottom
 *      - return value ignored
 *      - called immediately after the masthead
 *      - encompasses nothing; use to insert content after the masthead
 *
 *    ttg_masthead_secondary_top
 *      - if return=false, normal Backlight masthead is skipped
 *      - called immediately before the masthead element
 *      - fully encompasses the masthead; can be used to replace it
 *
 *    ttg_masthead_secondary_bottom
 *      - return value ignored
 *      - called immediately after the masthead
 *      - encompasses nothing; use to insert content after the masthead
 *
 *   ttg_navigation
 *     - if return=false, normal Backlight navigation is skipped
 *     - navigation is separate from the header section, so not affected by the above ttg_header... hooks.
 *      - encompasses the navigation <ul> element; can be used to replace it
 *
 *    ttg_main_top
 *      - return value ignored
 *      - called immediately within the main content column
 *      - encompasses nothing; use to insert content at the very top of the main content column
 *      - located outside the password protected area
 *
 *    ttg_main_bottom
 *      - return value ignored
 *      - called immediately before closing the main content column
 *      - encompasses nothing; use to insert content at the very bottom of the main content column
 *      - located outside the password protected area
 *
 *    ttg_footer_top
 *      - if return=false, the contents of the normal Backlight footer are skipped
 *      - called immediately within the footer section
 *      - encompasses the full contents of the footer section; can be used to replace those contents
 *
 *    ttg_footer_bottom
 *      - return value ignored
 *      - called last in the footer section
 *      - encompasses nothing; use to insert content at the end of the footer section
 *
 *    ttg_pallet_top_title
 *      - if return=false, the encompassed code is skipped
 *      - wraps the site title in the top pallet
 *      - use to replace the site title
 *
 *    ttg_toggle_T1
 *      - if return=false, the encompassed code is skipped
 *      - wraps the label element for "page__toggle__T1"
 *      - use to replace the toggle button with one of your own making
 *
 *    ttg_toggle_T2
 *      - if return=false, the encompassed code is skipped
 *      - wraps the label element for "page__toggle__T2"
 *      - use to replace the toggle button with one of your own making
 *
 *    ttg_social_top
 *      - if return=false, normal content is skipped
 *      - called immediately before social media icons in the top pallet
 *      - encompasses the social media icons; can be used to replace them
 *
 *    ttg_social_bottom
 *      - return value ignored
 *      - called immediately after social media icons in the top pallet
 *      - encompasses nothing; use to insert content following the social media icons
 *
 *    ttg_scripts
 *      - return value ignored
 *      - called immediately before </body>
 *      - encompasses nothing; use to insert content at the very bottom of the page
 *
 *    ttg_copy_top
 *      - if return=false, normal copy is skipped
 *      - called immediately within the page copy area
 *      - encompasses the page copy; can be used to replace it
 *
 *    ttg_copy_bottom
 *      - return value ignored
 *      - called immediately before closing the page copy area
 *      - encompasses nothing; use to insert content following the page copy
 *
 *    ttg_pallet01_top
 *      - if return=false, pallet content is skipped
 *      - called within pallet01, after masthead and navigation
 *      - encompasses the pallet01 content area
 *
 *    ttg_pallet01_bottom
 *      - return value ignored
 *      - called after the pallet01 content
 *      - encompasses nothing; use to insert content at the end of pallet01
 *
 *    ttg_pallet02_top
 *      - if return=false, pallet content is skipped
 *      - called within pallet02, after masthead and navigation
 *      - encompasses the pallet02 content area
 *
 *    ttg_pallet02_bottom
 *      - return value ignored
 *      - called after the pallet02 content
 *      - encompasses nothing; use to insert content at the end of pallet02
 *
 *    ttg_albumset_top
 *      - if return=false, normal copy is skipped
 *      - called immediately within the media area
 *      - encompasses the gallery grid / slideshow; can be used to replace it
 *
 *    ttg_albumset_bottom
 *      - return value ignored
 *      - called immediately before closing the media area
 *      - encompasses nothing; use to insert content following the gallery grid / slideshow
 *
 *    ttg_album_top
 *      - if return=false, the album content is skipped
 *      - called immediately within the media area
 *      - encompasses the album grid / slideshow; can be used to replace it
 *
 *    ttg_album_bottom
 *      - return value ignored
 *      - called immediately before closing the media area
 *      - encompasses nothing; use to insert content following the album grid / slideshow
 *
 *    ttg_single_top
 *      - if return=false, single image and content are skipped
 *      - called immediately above the single image display
 *      - encompasses the single image and related metadata; can be used to replace it
 *      - available only on single-image HTML pages for applicable album templates
 *
 *    ttg_single_bottom
 *      - return value ignored
 *      - called after the single image display
 *      - encompasses nothing; use to insert content following the single image display
 *      - available only on single-image HTML pages for applicable album templates
 *
 */


// SET USER FUNCTIONS BELOW
// Some example functions are included below. Feel free to delete or modify unwanted functions.
// ****************************************************************************************************

function ttg_head( $style, $path ) { 
	echo '
	<link rel="stylesheet" href="http://pideja.ca/luc/backlight/custom/css/lucnade.css" />
	';
    return false;


/* DELETE THIS LINE
// Basic structure for a PHPlugins function
function _HOOK_( $style, $path ) { 
	echo '

	';
	return false;
} // END /**/




/* DELETE THIS LINE
function ttg_main_top( $style, $path ) { 
	echo '<ul style="background-color:#FFF9C4;color:#000;margin:1.5rem 0;padding:24px 36px;">';
		if (PASSWORD_ENABLED) {
			echo '<li><strong>This gallery is private</strong>.</li>';
			if (LOGGED_IN) {
				echo '<li><small>The user is logged in</small>.</li>';
			} else {
				echo '<li><small>The user is logged out</small>.</li>';
			}
		} elseif (defined('CLIENT_RESPONSE_MANAGED') && CLIENT_RESPONSE_MANAGED) {
			echo '<li><strong>This gallery is client managed</strong>.</li>';
		} else {
			echo '<li><strong>This gallery is public</strong>.</li>';
		}
	echo '</ul>';
	return false;
} // END /**/




/* DELETE THIS LINE
// Create a contextual logout button for password protected & client-managed albums;
// button is added to the end of the navigation menu.
function ttg_scripts($style, $path) { 

	$logoutURL = '';

	if (PASSWORD_ENABLED && LOGGED_IN) {
		$logoutURL = '?logout';
	} elseif (defined('CLIENT_RESPONSE_MANAGED') && CLIENT_RESPONSE_MANAGED) {
		$logoutURL = shortSiteURL().'backlight/client-response/?c=client&a=logout';
	}

	if ($logoutURL) { ?>
		<script>
			var logoutButton = '<li class="menu-item"><a href="<?php echo $logoutURL; ?>">Logout</a></li>';
			$('.menu').append(logoutButton);
		</script>
	<?php }

	return false;
} // END /**/




/* DELETE THIS LINE
function ttg_toggle_T1( $style, $path ) { 
	// Below, the bare minimum markup required for functioning toggles;
	// fill in the LI element as you wish. Custom CSS may be necessary.
	echo '

	<label for="page__toggle__T1">
		<ul><li></li></ul>
	</label> 

	';
	return false;
} // END /**/




/* DELETE THIS LINE
function ttg_pallet_top_title( $style, $path ) { 
	// Below, the default markup for the title. The LI wrapping element is mandatory;
	// replace the inner HTML as you see fit. Retain the "masthead_pallet_top" class and styling,
	// or assign a new class, with styling defined in custom CSS.
	// Take note, the top pallet height is a 48px fixed value.
	echo '

	<li class="masthead_pallet_top">
		<h1><a href="/">Your Site Title</a></h1>
	</li>

	';
	return false;
} // END /**/




/* DELETE THIS LINE
function ttg_navigation( $style, $path ) { 
	echo '
	<ul class="primary-menu menu mouseable">
		<li class="menu-item"><a href="/">Home</a></li>
		<li class="menu-item menu-item-has-children"><a href="/galleries">Galleries</a>
			<ul class="sub-menu">
				<li class="menu-item"><a href="">Sub-item 1</a></li>
				<li class="menu-item"><a href="">Sub-item 2</a></li>
				<li class="menu-item"><a href="">Sub-item 3</a></li>
				<li class="menu-item"><a href="">Sub-item 4</a></li>
				<li class="menu-item"><a href="">Sub-item 5</a></li>
				<li class="menu-item"><a href="">Sub-item 6</a></li>
				<li class="menu-item"><a href="">Sub-item 7</a></li>
				<li class="menu-item"><a href="">Sub-item 8</a></li>
			</ul>
		</li>
		<li class="menu-item"><a href="/blog">Blog</a></li>
		<li class="menu-item"><a href="/about">About</a></li>
		<li class="menu-item"><a href="/contact">Contact</a></li>
	</ul>
	';
	return false;
} // END /**/




/* DELETE THIS LINE
// Adding new social media icons before ... 
function ttg_social_top( $style, $path ) { 
	echo '

	<li><a target="_blank" href="" class="social_media fa fa-google-plus"></a></li>

	';
	return true;
} // END

// ... and after.
function ttg_social_bottom( $style, $path ) { 
	echo '

	<li><a target="_blank" href="" class="social_media fa fa-pinterest"></a></li>
	<li><a target="_blank" href="" class="social_media fa fa-instagram"></a></li>

	';
} // END /**/




/* DELETE THIS LINE
// Highlight menu item for current page 
function ttg_scripts( $style, $path ) { 
echo <<<SCRIPT
	<script>
	$("ul.menu a[href='" + window.location.pathname + "']")
		.parentsUntil('.menu', 'li')
		.addClass("current_page_item")
		;
	</script>
SCRIPT;
	return false;
} // END /**/




/* DELETE THIS LINE
// Adds custom text to Next-page Cards in albums 
function ttg_scripts( $style, $path ) { 
echo <<<SCRIPT
	<script>
		var card = $('#nextPageCard');

		var numPages = card.data('pages');
		var thisPage = card.data('current');
		var nextPage = card.data('next');

		// 1. 
		// Add text to the card
		var cardText = $('<div />')
			.html('<p>to Page ' + nextPage + ' of ' + numPages + '</p>')
			.css({
				color: '#fff',
				display: 'block',
				fontSize: '0.875rem',
				position: 'absolute',
					bottom: 12,
					left: 0,
				textAlign: 'center',
				width: '100%'
			})
			.appendTo($(card));

		// 2. 
		// Change Font Awesome icon via addClass
		$(card).find('i')
			.removeClass('fa-step-forward')
			.addClass('fa-long-arrow-right');

		// 3. 
		// Fully replace and customize card content
		$(card).find('a')
			.html(
				'<span class="fa-stack">' + 
					'<span class="fa fa-file-o fa-stack-2x"></span>' + 
					'<strong class="fa-stack-1x"><span style="font-size: 0.75rem">' + thisPage + '</strong>' + 
				'</span>' + 
				'<i class="fa fa-long-arrow-right"></i>' + 
				'<span class="fa-stack">' + 
					'<span class="fa fa-file-o fa-stack-2x"></span>' + 
					'<strong class="fa-stack-1x"><span style="font-size: 0.75rem">' + nextPage + '</strong>' + 
				'</span>'
			);

	</script>
SCRIPT;
	return false;
} // END /**/




/* DELETE THIS LINE
// Target "Backlight Pangolin" templates specifically
function ttg_main_top( $style, $path ) { 

	if(preg_match('/^BACKLIGHT-PANGOLIN(.*)$/', G_STYLE)) {
		// FUNCTION HERE
	}

	// OR //

	if (G_STYLE == 'BACKLIGHT-PANGOLIN') {
		// FUNCTION HERE
	}

} // END /**/




// ****************************************************************************************************
// END USER FUNCTIONS

?>

I still get an error message: "Unexpected error: syntax error, unexpected end of file in phplugins-pangolin-luc.php on line 468"

(Sorry for the long code but I wanted to show all in case of an error I might not have seen.)

rod barbee · 2018-04-23 05:15:59

you haven't closed your function. It needs a curly brace at the end (and doesn't need the return false; , though that doesn't really matter in this case).

function ttg_head( $style, $path ) { 
	echo '
	<link rel="stylesheet" href="http://pideja.ca/luc/backlight/custom/css/lucnade.css" />
	';    
}

pideja · 2018-04-23 21:40:05

Ah, those pesky curly braces...

It's a good news (thanks to Rod), bad news story: the site is back up and looking good except for the bad news...that big purple background in the /Expositions / Exhibitions" pages. It should be controlled by the CSS (lucnade.css) but any change to that file has no effect. I tried to change the text color to red...no change. It seems the CSS as no effect on (at least) that section of the page. I even suspended the background-color settings in the CSS

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

to no avail.

Last edited by Daniel Leu (2018-04-23 21:57:26)

Daniel Leu · 2018-04-23 22:02:32

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;
	}

rod barbee · 2018-04-23 22:05:34

look starting at line 524 of your css file. that's where the purple is coming from

rod barbee · 2018-04-23 22:05:59

looks like Daniel beat me to it.

Community @ The Turning Gate

#1 2018-04-22 06:37:29

Vegas slide show discrepancies

#2 2018-04-22 07:14:43

Re: Vegas slide show discrepancies

#3 2018-04-22 07:30:57

Re: Vegas slide show discrepancies

#4 2018-04-22 07:58:31

Re: Vegas slide show discrepancies

#5 2018-04-22 08:36:10

Re: Vegas slide show discrepancies

#6 2018-04-22 08:52:57

Re: Vegas slide show discrepancies

#7 2018-04-22 09:06:42

Re: Vegas slide show discrepancies

#8 2018-04-22 09:15:05

Re: Vegas slide show discrepancies

#9 2018-04-22 09:19:31

Re: Vegas slide show discrepancies

#10 2018-04-22 18:45:17

Re: Vegas slide show discrepancies

#11 2018-04-22 22:18:51

Re: Vegas slide show discrepancies

#12 2018-04-22 23:56:47

Re: Vegas slide show discrepancies

#13 2018-04-23 01:21:15

Re: Vegas slide show discrepancies

#14 2018-04-23 01:35:31

Re: Vegas slide show discrepancies

#15 2018-04-23 03:00:23

Re: Vegas slide show discrepancies

#16 2018-04-23 03:07:52

Re: Vegas slide show discrepancies

#17 2018-04-23 03:14:40

Re: Vegas slide show discrepancies

#18 2018-04-23 03:42:55

Re: Vegas slide show discrepancies

#19 2018-04-23 04:00:13

Re: Vegas slide show discrepancies

#20 2018-04-23 04:25:25

Re: Vegas slide show discrepancies

#21 2018-04-23 05:15:59

Re: Vegas slide show discrepancies

#22 2018-04-23 21:40:05

Re: Vegas slide show discrepancies

#23 2018-04-23 22:02:32

Re: Vegas slide show discrepancies

#24 2018-04-23 22:05:34

Re: Vegas slide show discrepancies

#25 2018-04-23 22:05:59

Re: Vegas slide show discrepancies

Board footer