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.
To check if the child theme is working, I used following code in my child theme's style.css:
body {background-color: red !important}Is your WP child theme active?
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.
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.
Hmmm.... You got me thinking.... and a few minutes later, I have my solution ![]()
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!
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.
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 537This is making me nuts...
If you don't mind, you can email the script and I'll have a look at it.
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;
}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 '}'.
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.
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.
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().
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.
The path is not correct. It is /backlight/vanilla-form/css/vanilla-form.min.css, starting with a slash.
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.
Okay guys, all done, I was expecting a word of pain sorting this out but even a clueless old fool like me has managed this.
Thanks again. Good work chaps
![]()
Hi, I tried that first but I had a message that said it couldn’t delete from the server.
That's strange.
In this case I would send your Backlight login along with a link to this thread to Ben so he can have a look at it.
You never should have to delete galleries using the c-panel. Backlight is database driven and galleries need either be deleted from Lightroom or from Backlight > Publisher > Galleries > Albums. Click on the album name in question and then select Delete Album.
Since you upgraded your site to use Backlight, I would get the Wordpress for Backlight module as well. This way you have the same look&feel of your main site and get all other Backlight 2 benefits.
From phplugins-pangolin-sample.php:
* head
* - return value ignored
* - called immediately before </head>
* - encompasses nothing; use to insert content into the <head>Maybe something like this:
function head() {
echo '<link rel="stylesheet" type="text/css" media="all" href="/path/to/css/vanilla-form.min.css">';
echo '<script src="/path/to/css/vanilla-form.min.js"></script>';
}Just tried it on my installation and I can scroll the long list all the way down. There is a 'down' arrow at the bottom and when I hover my mouse over it, the list scrolls down.
This looks nice, Lisa.
There is one thing I would change: I would move the BACK option to the blank menu of the instruction and help pages. A benefit is that the user doesn't have to move the mouse.
The issue was that Lisa wanted her clients to click on a menu link in those pages that would go back to their personal album. Using the same menu set for each album would then be impossible because the "My Gallery" link would by necessity have to go to the same place for all albums. She wanted them to be able to read the instructions and trouble shooting and go directly back into their album.
The pop-up boxes seemed a better solution than creating multiple page templates, each using a different menu set tailored to a single client. And it keep the client in their album.
Ahh... didn't think of that! Pop-up boxes seem to be a nice approach. Specially they can be part of the template.
I'm a bit confused.... you always can have shared pages located at http://lisalphotography.com/BL2/name_of_shared_page, manage them with Backlight and have a menu inside your gallery pointing to them. There is no need to redo them when you are posting a new client gallery. But I guess I miss something ![]()