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.
Finally got to the bottom of this and, of course, it was my fault. In my custom CSS, I was hiding a button on the search form and it carried over to the Cart form. All better now. Everything is working fine so no follow-up is needed. My screw-up!
Will give it another try. I just re-upgraded to Backlight-Pages-104 and Cart-401 and nothing has changed. The "Proceed to Checkout" button never appears.
I reset the cart several times. No "Proceed to Checkout" button ever appears. Has anyone got this to work in Backlight? On the surface, it looks to me like "Invoiced checkout" is not working in Backlight.
That's what I suspected, but when I turn on the Invoiced Checkout option, the interface shows no change. I see no means for a customer to specify Invoiced as an option at check-out no matter what I try. What am I missing? Do they still have to press the PayPal button to initiate an invoiced transaction? It's certainly not obvious. No "Proceed to Checkout" button appears -- only the PayPal button.
OK, I'll see if I can find anything on the "transactionless" method from V4.
OK, got it. The key here is that it has to be relative to THIS page. I was making the reference relative to the root folder. Thanks!
I'm trying to allow clients to pay via check instead of PayPal. Is that the Invoice checkout method? I see no documentation on that option and have played with it to no effect. Is it explaiend anywhere? How does it work? I see no behavior change on checkout when the option is turned on.
When adding a custom Cart button, relative references in the data-thumbnail field do not seem to work. I'm forced to enter an absolute reference to make this work. For example, the following code does not find the button in spite of the fact that it's in the "images" folder at the root of the site.
<button class="add-to-cart" data-item="2017-calendar" data-name="New England Lighthouses" data-price="Calendar" data-thumbnail="/images/calendar-cover-light.jpg">Buy This Calendar</button>
Well, I think I may do the same.
I was previously using the same approach but Matt seemed very opposed to using custom stylesheets to override default behavor. Not sure why but he left me with the distinct impression that this could cause problems with Backlight down the road.
Is there any "safe" way to add a border to large photos in the galleries? Without a border, I find the images look rather flat and would like to spiff them up a bit with at least a single-line border. I was doing that in my custom stylesheet, but was told that this was not a safe thing to do in Backlight. Any suggestions that would work to improve appearance without stepping on the feet of Backlight?
If I create a product with a title like 8" x 10" Luster Print, Backlight chokes on this error:
Query21301308561370242387_1468782723025'
I think I've gone as far as I can with the Backlight test site for now. You can see it here: http://www.mabtesting.dreamhosters.com. It has not gone into production yet because I'm trying to decide whether I wait on Blog support or not.
Anyway, I chose to place the Search function in the menu bar itself and use masonry for all large photo displays. I did include the CE4 blog to complete the site and it works fine with a few adjustments. I had to create separate phplugins.php and custom.css files for the blog because it cannot share the Backlight equivalents. The two notable differences discernible in the blog is that I could not reproduce the menu precisely due to basic implementation differences, although it comes close. Also, the Search function is not present in CE4, hence missing from the blog menu.
I have to add that creating and maintaining the site with Backlight is SO MUCH easier than plucking through Lightroom with its slow refresh rate. This is huge improvement, so congrats to the team for making our lives easier.
Thanks. Yep, separating the two phplugins and css files works fine. Need to rework the menu on the blog page though because the auto-index drop menu no longer works with the Backlight gallery strucutre. But other than that, it should solve my problem
Since the blog is a ways off, I'm wondering about the co-existence of a CE4 blog with a Backlight framework. More specifically, I'm assuming that the two cannot share phplugins.php and custom.css files? I made a quick test and the CE4 blog seems to benignly ignore the Backlight versions. I guess that means all formatting has to be done inside the template. Thoughts?
Clearing the template cache didn't fix the problem but ?reloadModel solved it. Thanks!
I just upgraded my test site to the latest version. Some very nice improvements and fixes here. But one feature that has degraded is the masonry alignment in the galleries. I use masonry in all my gallery pages and there seems to be something wrong with the algorithm in this latest version. The positioning leaves ugly gaps in the display whereas v101 worked fine.
I've reset all the templates and pages, and deleted the template cache. Am I mising something? You can see my test site here: http://www.mabtesting.dreamhosters.com
I currently have Search at the top of my Gallery page, but I'd like to see how it looks and behaves in the menu bar. Are there implementations of Search in the menu bar that you can point me to?
If you’re in a rush to add social media icons to your Backlight site (without having to wait for later versions), you can easily add your own custom social media bar using PHPlugins and a custom stylesheet (just like the good old days).
On my test site (http://www.mabtesting.dreamhosters.com/home/), I added social media buttons at the top of the footer, above the copyright notice. In my case, I’m using 32x32 pixel icons, but you can choose any size you like as long as you change the width and length parameters in the PHPlugins code. And you can also revise the CSS code to align the buttons however you choose, although mine are centered on the page.
Below is the code I added to my PHPlugins file to support Facebook, Google Plus, Twitter, 500px, Instagram, and Flickr. I used the ttg_footer_top hook to add the buttons, but you can use any of the available hooks to locate the social media bar elsewhere on your pages. This code assumes a top-level folder on your site named “icons” to hold the social media buttons. And you’ll obviously have to change all links to social media sites. The sites are always opened in a separate window, but if you prefer to open them in the same window, just remove “target=_blank” from each of the lines below.
function ttg_footer_top( $style, $path ) {
echo '
<div id=“socialbar">
<a href="https://www.facebook.com/yourfacebook/" target="_blank"><img src="/icons/facebook.png" title="Facebook" width="32" height="32"/></a>
<a href="https://plus.google.com/+yourgoogleplus” target="_blank"><img src="/icons/google.png" title="Google Plus" width="32" height="32"/></a>
<a href="https://twitter.com/your twitter“ target="_blank"><img src="/icons/twitter.png" title="Twitter" width="32" height="32"/></a>
<a href="https://500px.com/your500px” target="_blank"><img src="/icons/500px.png" title="500px" width="32" height="32/"></a>
<a href="https://www.instagram.com/yourinstagram/“ target="_blank"><img src="/icons/instagram.png" title="Instagram" width="32" height="32"/></a>
<a href="https://www.flickr.com/photos/yourflickr/“ target="_blank"><img src="/icons/flickr.png" title="Flickr" width="32" height="32"/></a></div>
';
return true;
} // END ttg_footer_top
Below is the code I added to my custom CSS. I start by centering the standard copyright notice on the page.
div.copyright p
{
text-align: center;
}
And then, I add code to center the social media bar, adding a margin at top to separate the buttons from the rest of the page.
#socialbar {
text-align: center;
margin-top: 24px;
display: block;
}
I'm glad it's not just me. I was beginning to think I had a corrupt installation.
OK, here's the latest on the Google Fonts saga. I used the ttg_head hook (added to Backlight 1.01) in phplugins to explicity link the Google Fonts and that works fine as a fallback. Then I'm able to assign the family names in Backlight using Prepend Font Family w/. This seems to suggest that the @import statements are not being processed on my configuration for some reason.
Be aware that if you copy the Google Fonts "link" statement directly from their website, you need to replace all single quotes with double quotes, else phplugins returns a fatal error on load.
I tried it again after the update and still not able to load Google Fonts for some reason. I'm stumped as to why. Even using the exact syntax in Matt's post yields no result. Something weird is going on with my configuration. I've tried it on two different browsers for kicks and get the same results (or lack of). As a workaround, are we still able to link the fonts from phplugins and assign them in a custom CSS? In the past, we loaded the fonts in function ttg_head_end but that seems to have gone away in Backlight. Is there another function that would allow me to do the equivalent loads?
I had no problem whatsoever with the update -- all my settings were intact. But you need to look at the README to only copy selected folders.
I installed the update and the sub-menus are now sorted on name as expected. Looks much better. As far as the album sets are concerned, will they always show up at the top as opposed to showing up in name order along with the rest of the menu? In my opinion, that makes for an awkward-looking menu, where all the sets are bunched up at the top for no apparent reason.
I verified that the update fixed all issues related to the masony gallery on my home page. Thanks.