Community @ The Turning Gate

Support community for TTG plugins and products.

You are not logged in.

#1 Re: Backlight 2 Support » Vanilla Form custom php » Yesterday 02:04:07

Crizz wrote:

I send you an email by clicking on the Email link in your profile...
Could you DM me your email address please? Thank you.

I received the email today and replied to it.

#2 Re: Backlight 2 Support » Vanilla Form custom php » 2019-02-10 03:08:29

Crizz wrote:

Did you got my mail Daniel?

No, I haven't received anything. The spam folder is empty too.

#3 Re: Backlight 2 Support » Meta Description ? » 2019-02-08 03:41:42

Jim, did you try the find & replace plugin? It looks like you can achieve a populated Title field in two steps: 1) copy filename to title field followed by 2) replacing unwanted characters by spaces.

Obviously this takes a bit more time than having an automated solution. But this way, you could have your title field populated within 'minutes'. Don't forget to select 'publish metadata only' in Lr Publisher when updating your images.

#4 Re: Backlight 2 Support » Meta Description ? » 2019-02-06 14:52:33

Matthew wrote:
Daniel Leu wrote:

How about a simple phplugins function that overwrites the value currently used? This way, one could even include the album title, if desired.

For clarity, are you suggesting a PHPlugins hook to replace the page's TITLE element in the document head?

The title could easily be replaced via Javascript, using document.title via the existing PHPlugins hook for scripts.
https://developer.mozilla.org/en-US/doc … ment/title

Ben proposed a new Publisher setting which would mean a hardcoded implementation. So instead of going this way, I think that a phplugins hook would be more versatile. AFAIK this would affect <title> as well as og:title and twitter:title. Having a matching crumb would make sense to me as well. This is a feature request from Jim, so he might be better to specify/clarify this.

I don't know whether one approach or the other would yield greater SEO benefit. Google is supposedly good about parsing JavaScript for SEO. Supposedly ...

I'd rather have my page ready on load and not depend on Google's capability to parse my JavaScript code.

#5 Re: Backlight 2 Support » Meta Description ? » 2019-02-06 11:32:36

Ben wrote:

Hi Jim, from a Backlight perspective that could probably be done by adding a new setting within the Publisher section of Backlight Settings, e.g. Single Image Page Title Format with options such as Image Title (the current behaviour), Filename (forced to used the filename, whether the Title metadata existed or not) and Filename Converted to Title (for want of a better name - where Backlight code would convert any textual part of a filename to a Title, as you've described).
The filename-to-Title functionality would be easy enough to code.  We already have similar conversions in other places such as a slugToTitle utility function.

Does that sound like it would fit the bill?

Ben, if you add a filename-to-Title function, then slugToTitle should be updated too, shouldn't it?

How about a simple phplugins function that overwrites the value currently used? This way, one could even include the album title, if desired.

#6 Re: Backlight 2 Support » Meta Description ? » 2019-02-06 11:24:31

JimR wrote:
Daniel wrote:

Jim, can you provide a link to what you refer to as "photo page"?

What I'm calling the "photo page" is the page with just the one photo on it. It's the page with the unique URL to the one photo.

I'm using albums with slide shows, which show as a gallery. From there I can do into the slide show, get to the sharing bar and select the permalink. That URL is the type that ends with ...single.php

I thought that you were looking at a different page since my titles are propagate (as long as I put a title in there).

#7 Re: Backlight 2 Support » Why is my Backlight page so gigantic? » 2019-02-06 03:50:39

I was able to reproduce the same look and feel from my CE4 days.

A few comments, and yes, I'm going for the low-hanging fruits:

- Your logo is now 60px high vs 40px with CE4. To make the masthead smaller, you could remove the top and bottom padding from 24px to something smaller (.masthead-primary {padding: 24px 0 24px;}).

- The font you use is bigger than the one from CE4.

BTW, the links should be http://jwlimages.com/Temp/Backlight_on_iPad.PNG

#8 Re: Backlight 2 Support » Meta Description ? » 2019-02-06 03:38:26

Jim, can you provide a link to what you refer to as "photo page"?

#9 Re: Backlight 2 Support » BL1 -> BL2 on staging site » 2019-02-05 12:17:10

Do you have a link to your site?

There is a small error: /wp/wp-content/themes/backlight-child/styles.css should be  /wp/wp-content/themes/backlight-child/style.css

style.css and functions.php are used by Wp. You will not find any references to them in Backlight.

#10 Re: Backlight 2 Support » BL1 -> BL2 on staging site » 2019-02-05 10:27:01

To check if the child theme is working, I used following code in my child theme's style.css:

   body {background-color: red !important}

#12 Re: Backlight 2 Support » Vegas Slideshow questions » 2019-02-04 16:34:59

jwlimages wrote:

Yes, but if I have more than one album template, how do I determine which gets used? I inserted an album, set up the inline Vegas slideshow, but can't identify which album template is active. (it should be the Pangolin Theater one I created) Maybe worse - if I toggle "show captions" on/off for either of the 2 album templates, no effect on the home page - no captions show. Also tried toggling settings like transition, presentation type, in each album template, just to see which one is at work - again no effect. ???

In Backlight Publisher, when you click on Edit Album, you have the option to select the desired album template. Or you can do it with Lightroom Publisher, control-click (or right mouse button) on the album name and then select Edit Album.

#14 Re: Backlight 2 Support » Vegas Slideshow questions » 2019-02-04 16:26:38

jwlimages wrote:

One final oddity - the gallery for the home page (00_HomePage…) shows in the Galleries pull-down, despite my setting the Features tab in the album to Hide from Album Set & Hide from Search. Isn't this supposed to keep the album "invisible" from the browser UI or to not clutter up pull-down menus, or am I misunderstanding (again)?

Hidden albums are visible when you are logged in as admin. Try it with a different browser and it should not be there. If you look at your top level gallery (eg /galleries), your hidden albums have an eye symbol to indicate that they are hidden.

#15 Re: Backlight 2 Support » BL1 -> BL2 on staging site » 2019-02-04 11:42:46

Hmmm.... You got me thinking.... and a few minutes later, I have my solution smile

I use a WP child theme and added this to my functions.php file:

add_action('wp_head', 'change_bar_color');
add_action('admin_head', 'change_bar_color');

function change_bar_color() {
	echo '
		<style>
		#wpadminbar{
		    background: #7B0202;
		    color: #fff;
		}

		#adminmenu, 
		#adminmenu .wp-submenu, 
		#adminmenu .wp-has-current-submenu .wp-submenu,
		#adminmenuback, #adminmenuwrap {
		    width: 160px;
		    background-color: #7B0202;
		}
		</style>
	';
}

It's not perfect, but does the job for me. No more editing the wrong Wordpress installation! Yeah!

#16 Re: Backlight 2 Support » BL1 -> BL2 on staging site » 2019-02-04 06:36:36

JimR wrote:
  • The WP staging/development site needs it's own copy of the WP DB. Clone the DB, and then modify the WP config file in the staging site to point at the clone.

I cloned the WP database in the past as well, but then it happened that I added new content to the staging area instead of my main site. Now I use a new WP database with just a few dummy entries. This way I see my changes, but it is obvious that this is the staging area.

#17 Re: Backlight 2 Support » Vanilla Form custom php » 2019-02-04 04:16:52

Crizz wrote:

Is there anything after that?

No

When I add } to the end it says: Unexpected error: syntax error, unexpected end of file in my-phplugins.php on line 537
When I add '}' to the end is says: Unexpected error: syntax error, unexpected end of file, expecting function (T_FUNCTION) in my-phplugins.php on line 537

This is making me nuts...

If you don't mind, you can email the script and I'll have a look at it.

#18 Re: Backlight 2 Support » Contact Form to the center and shadow / border around image view » 2019-02-04 03:34:44

christopherhauser wrote:

Thanks a lot! One last thing, is there a way to center the "text/labels" and send button as well? I am slowly getting back to CSS with inspecting and changing, but some things just won't work :Q

This seems to work for me:

.contact-form p {
    text-align: center;
}

.contact-form .actions {
    text-align: center;
}

#19 Re: Backlight 2 Support » Vanilla Form custom php » 2019-02-03 02:53:19

Crizz wrote:

function scripts()  {
      echo'
          <script>$(document).ready(function() {
    var myForm;
    myForm = new VanillaForm($("form.vanilla-form"));
});</script>
';

This script gives an error on my contact page saying the following:
Unexpected error: syntax error, unexpected '?>', expecting function (T_FUNCTION) in my-phplugins.php on line 538

The function is not closed. There is a missing curly closing bracket '}'.

#20 Re: Backlight 2 Support » Contact Form to the center and shadow / border around image view » 2019-02-03 02:39:17

Line 17 of your local css file chauser.css defines a max-width for form fields:

form input[type="color"], form input[type="date"], form input[type="datetime"], form input[type="datetime-local"], form input[type="email"], form input[type="month"], form input[type="number"], form input[type="password"], form input[type="search"], form input[type="tel"], form input[type="text"], form input[type="time"], form input[type="url"], form input[type="week"], form input:not([type]), form select, form textarea, .form input[type="color"], .form input[type="date"], .form input[type="datetime"], .form input[type="datetime-local"], .form input[type="email"], .form input[type="month"], .form input[type="number"], .form input[type="password"], .form input[type="search"], .form input[type="tel"], .form input[type="text"], .form input[type="time"], .form input[type="url"], .form input[type="week"], .form input:not([type]), .form select, .form textarea {
    max-width: 450px;
}

Once you increase it, it looks better. But this affects many other fields and might have unintended side effect. You might want to add the .slug-contact class to the selector.

#21 Re: Backlight 2 Support » Running a non-phplugin php file from Pangolin Page » 2019-02-01 06:18:02

I did a quick test on my site and I get this working when I disable /backlight/custom/phplugins/.htaccess or when I move my script to the root directory.  Best might be to add an additional rule to this .htaccess file to allow accessing your script or host your file-upload infrastructure separate of /backlight.

#22 Re: Backlight 2 Support » Running a non-phplugin php file from Pangolin Page » 2019-02-01 02:53:35

You would need to use phplugins to call your custom php code. Depending on what your custom code does, select the most appropriate hook, maybe copy_bottom().

#23 Re: Backlight 2 Support » Vanilla Form custom php » 2019-01-31 01:40:53

I'm looking at http://www.aimhigh.aero/contact/. The path to the css and javascript file are now correct, and I second Rod's recommendation to move the vanilla folder inside /backlight/custom.

But when I look at the source code of that contact page, I don't see the Vanilla Form markup. You can add this in the page copy section of your contact page. But maybe you are testing this on another page. In this case, a link would be helpful.

#24 Re: Backlight 2 Support » Vanilla Form custom php » 2019-01-30 04:47:20

The path is not correct. It is /backlight/vanilla-form/css/vanilla-form.min.css, starting with a slash.

#25 Re: Backlight 2 Support » Deleting a CRG » 2019-01-29 07:00:39

Ben wrote:

There isn't anything for me to find by looking into this.  If something like that happens, just go in and remove the album in the Backlight Admin login.

Ben, he mentioned that he tried this but got an error:

I tried that first but I had a message that said it couldn’t delete from the server.

Board footer

Powered by FluxBB