Community @ The Turning Gate
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.
- New user registrations are disabled.
- Users cannot create new topics.
- Users cannot reply to existing topics.
You are not logged in.
- Topics: Active | Unanswered
#651 Re: Backlight 2 Support » Theater based template not converted when upgrading » 2018-09-14 03:52:38
I thought everything in Backlight 1 was supposed to convert to Backlight 2?
Now I have to revert back to Backlight 1 (again) to see how I designed all of my theater templates, then I have to re-install backlight 2 and create new templates.
Are you sure there isn't an easier way to do this?
I would wait until Matt chips in. In the meantime, you could setup a subdomain/subdirectory where you install BL1 so you could switch back and forth between the two.
#652 Re: Backlight 2 Support » Theater based template not converted when upgrading » 2018-09-14 03:36:58
The template you shared is Okapi based. You need to created a new Theater template that is based on the Pangolin engine.
#653 Re: Backlight Support » Album disappears » 2018-09-14 03:33:56
I don't see any issues here.
#654 Re: Backlight 2 Support » LR publisher » 2018-09-14 01:04:35
As a precaution, you always can copy your current Publisher to a different location and recover it from there if needed.
#655 Re: Backlight 2 Support » Backlight 2 Install Troubles » 2018-09-14 00:57:03
Yes, it is correct to delete the 'reluctant to delete' directories. Those are all application directories that are replaced by new ones located in the modules folder. All data is in the 'data' directory. So this you are good!
Did you install the other modules such as CRG and Cart? Backlight > Admin > Backlight Modules
#657 Re: Backlight Support » Standard album slideshow image duration » 2018-09-13 07:49:43
If I remember correctly, Matt mentioned yesterday, that this is on the list of things he likes to address.
#658 Re: Backlight 2 Support » multiple menus » 2018-09-13 04:53:41
Cool!
#659 Re: Backlight 2 Support » multiple menus » 2018-09-13 03:14:21
No, don't create an empty file. Just copy the sample phplugins file (phplugins-pangolin-sample.php) and rename it something more like mysite.php and then select this in the page template under advanced setup.
Following menu works for me.
function pallet02_top(){
echo '
<nav class="nav nav_v">
<ul class="primary-menu menu mouseable">
<li class="menu-item"><a href="#1">Menu item 1</a></li>
<li class="menu-item"><a href="#2">Menu item 2</a></li>
<li class="menu-item"><a href="#3">Menu item 3</a></li>
<li class="menu-item"><a href="#4">Menu item 4</a></li>
<li class="menu-item"><a href="#5">Menu item 5</a></li>
</ul>
</nav>
';
}#660 Backlight 2 Customization » Updating phplugins » 2018-09-13 02:35:31
- Daniel Leu
- Replies: 5
This is just a short summary on how to update phplugins from Backlight 1 to Backlight 2.
It's a good idea to look at the new sample file (backlight/custom/phplugins/phplugins-pangolin-sample.php) to see all the available functions and how the file structure is.
1) Phplugins are now class based. So all functions need to be defined within a class context. This is well seen in the example file.
class PHPlugins extends APHPlugins {
// put your functions here
}2) Function names changed and lost their arguments. You only need to remove the ttg_ prefix and whatever is between parentheses.
Before:
function ttg_pallet_top_title( $style, $path ) {
echo '
// ......
';
return false;
} // END /**/After:
// Basic structure for a PHPlugins function
function pallet_top_title() {
echo '
// ......
';
return false;
} // END /**/3) If you call another function within the PHPlugins class, you need to use
$this->my_function()instead of just
my_function()4) Backlight 1 $style and $path arguments are accessible as
$this->styleand
$this->pathTip:
Please first make a copy of either /backlight/custom/phplugins/phplugins-pangolin-sample.php or /backlight/custom/phplugins/phplugins-okapi-sample.php and give it a good name: let's call it /backlight/custom/phplugins/site-phplugins.php. Then select this file in your template editor as your site's phplugins file. Add your custom functions from your Backlight 1 phplugins file and adjust them accordingly.
#661 Re: Backlight 2 Support » multiple menus » 2018-09-12 23:54:32
What do you mean by "pages I create"? Single image pages? Yes, there is an option for that: Designer > Template >...> Design Template > Photo Presentation: Single-Image Pages.
#662 Re: Backlight 2 Support » Problem with Upgrade to BL2 » 2018-09-12 13:48:19
And all your functions need to be part of a class as shown in phplugins-pangolin-sample.php:
class PHPlugins extends APHPlugins {
// put user functions here
}#663 Re: General » CE3 to Backlight 2 » 2018-09-12 07:34:44
It makes a lot of sense to ask questions before you start! I like to work in subdomains since it is really separate to the main site. So I won't just mess up my main site by mistake... Both approaches work.
#664 Re: General » CE3 to Backlight 2 » 2018-09-12 06:31:11
You can either do your development work in a subdirectory or in a subdomain. Both ways work.
Rod has an article talking about migrating CE4 or earlier to Backlight. Please have a look at http://ttg-tips-and-tricks.barbeephoto. … backlight/
#665 Re: Backlight 2 Support » BL2 Web Publisher - Drag and Drop? » 2018-09-12 02:47:12
FYI: Drag-and-Drop from ON1 Photo Raw to Backlight 2 Publisher works on the Mac!
#666 Re: Backlight 2 Support » Tokens displaying in BL2 » 2018-09-12 02:26:26
Hi Tom.
Please check if there are any module updates pending. There was a minor update coming in last night:
Fixes issues with handling missing metadata on Backlight Publisher
This might fix what you are seeing.
#667 Re: Backlight 2 Support » Unsafe Scripts Warning Message on Blog » 2018-09-12 02:22:45
You might want to add an automatic redirect from http to https in your .htaccess file. Check with your host for the required format.
#668 Re: Backlight 2 Support » BL2 Web Publisher - Drag and Drop? » 2018-09-12 02:09:12
ACDSee only works on Windows. Since I'm on a Mac, I can't try the evaluation version (https://www.acdsee.com/en/free-trials). Sorry.
But if you can drag files to another application, you can drag them onto your Desktop too? Then just drag them from there to Backlight 2.
#669 Re: Backlight 2 Support » Unsafe Scripts Warning Message on Blog » 2018-09-12 01:52:26
Your site uses https. But you still have some references to resources loaded with http. You should set the URL in Backlight settings to use https://bobleggettphotography.com instead of http:/bobleggettphotography.com as well. This should clear this up. Oh, don't forget to force an update to the wordpress template files in Backlight/Designer.
#670 Re: Backlight 2 Support » BL2 Web Publisher - Drag and Drop? » 2018-09-11 23:45:16
To upload new images, you can used drag+drop.
#671 Re: Backlight 2 Support » Upgrading from Backlight 1 or CE4 to Backlight 2 » 2018-09-11 23:44:21
Backlight 1 pages will continue to work as they were before, no re-publishing needed. But if you use phplugins, that needs to be updated. For CE4 based sites, they need to be re-designed.
#672 Re: Backlight 2 Support » White blank page after upgrade » 2018-09-11 05:55:42
Yes I did the update of the albums and I have the Okapi modules installed
Good! I guess you have removed /backlight/framework|admin|cart|.. as per the upgrade instructions.
#673 Re: Backlight 2 Support » White blank page after upgrade » 2018-09-11 04:24:58
Did you upgrade the album files? Backlight Dashboard > Update Album Files.
Based on your galleries code, I think you need to install the Okapi modules as well Backight2 > Admin > Backlight Modules > Okapi Web Modules > Install All.
#674 Re: Backlight Support » CentOS 7.5: You don´t have permission to access /backlight ... » 2018-09-07 06:11:02
5. .htaccess exists also in the web root folder
Is this the .htaccess file from the zip file or another one?