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
#251 Re: Backlight Support » No access to Backlight frontend nor backend » 2019-07-23 23:48:41
I've installed BL2. Everything is back to normal. Thx
#252 Re: Backlight Support » No access to Backlight frontend nor backend » 2019-07-23 02:12:31
I'm using Backlight-123-Release6 with PHP 7.2. I haven't received any other upgrade notification.
It looks like Release 7 is the latest. Just use the last link you have to download the latest version.
Should I upgrade to Backlight 2?
I like Backlight 2. Many things such as upgrades are so much easier. If you can, I definitely would recommend to upgrade.
#253 Re: Backlight Support » No access to Backlight frontend nor backend » 2019-07-23 00:54:04
Are you using the latest version of Backlight? I would download the modules again and install them to see if this fixes the issue.
The reason for this message is most likely a PHP version change done by your host.
#254 Re: Backlight 2 Support » What Does this mean? » 2019-07-18 07:41:57
This site,http://marccharlebois.com/was built at the same time and it still works.
This site is based on CE3.
The issue you are having is a PHP version change. You can log into your host's admin panel and change the PHP version to an older one. Or, as Ben has pointed out, download the latest Backlight version AGAIN** and install it. Then the site will work again. No changes are needed.
** I is important that you download it again since there were some under-the-hood changes to fix, among others, the issue you are currently seeing.
#255 Re: Backlight 2 Support » What Does this mean? » 2019-07-18 04:19:09
The reason for the error is most likely a change in the php version done by your host.
I think this site is running backlight 1. If this is the case, install the latest backlight 1 modules.
#256 Re: Backlight 2 Support » Cleint responce ok in one site, don't work in 2° site » 2019-07-17 01:04:06
fotmaesron wrote:i have an https certificate ?
Even so, I'm seeing warnings in Safari for iOS and I'm getting warnings from Kaspersky on my desktop PC. If I'm seeing it, could be others will too. I don't know why warnings like this pop up but thought you'd want to know.
Both Chrome and Safari on the Mac show a valid certificate.
#257 Re: Backlight Support » Top of Page Button » 2019-06-30 03:01:16
Looks like you got it working now.
#258 Re: Backlight 2 Support » Top Pallet Logo » 2019-06-25 03:58:47
Pierre, to check your css code, just run it through a validator such as https://jigsaw.w3.org/css-validator/val … pideja.css
#259 Re: Backlight 2 Customization » Lazy-Loading of Thumbnails with Custom album/page load » 2019-06-24 03:26:58
Hi Michael,
Looking at the rendered gallery source code, it looks like Matt is using lazysizes as the lazy loader. Adding
class="lazyload"to the thumbnails and using data-src instead of src should do the trick.
#260 Re: Backlight 2 Support » Top Pallet Logo » 2019-06-23 05:50:23
You are missing a curly closing bracket to close the class before the php closing tag.
#261 Re: Backlight Showcase » Photo stock with Backlight 2 - Cart module » 2019-06-22 03:02:00
This looks great! Nice job, Nico!
#262 Re: Backlight 2 Support » error sending mail » 2019-06-21 23:44:16
Your system is not properly configured. You need to talk to your host. See http://community.theturninggate.net/vie … 032#p59032
#263 Re: Backlight 2 Support » Update to 2.0.9 cut my page layout to half what it used to be » 2019-06-18 05:06:54
I've had no problems with my sites or with any WordPress installations on those sites. I'm also using a custom footer via phplugins, so that may be why I'm not seeing any footer issues in WordPress.
On one test site I disabled phplugins for the custom footer. Still no issues in the Backlight or WordPress portions of the site.
Hi Rod,
This is independent of a custom footer (I'm using one too). Did you export the WP theme after the Backlight update? It might only happen when the cart is enabled.
#264 Re: Backlight 2 Support » Update to 2.0.9 cut my page layout to half what it used to be » 2019-06-18 02:36:57
Workaround: I modified the file ~/blog/wp-content/themes/my-theme/footer.php. This reverts a v2.0.9 code change back to the previous version.
For me, this change starts at line 385:
<?php
// $moduleURL = shortSiteURL().'backlight/modules/module-cart/';
$shortSiteURL = '/';
$moduleURL = $shortSiteURL.'backlight/modules/module-cart/';
?>Please note that this change is overwritten whenever the Wordpress theme is exported again.
#265 Re: Backlight 2 Support » Update to 2.0.9 cut my page layout to half what it used to be » 2019-06-18 02:20:41
Bingo, got the same error!
#266 Re: Backlight 2 Support » Update to 2.0.9 cut my page layout to half what it used to be » 2019-06-18 02:19:05
Blog is the only thing I've updated to 2.0.9. Blog is in it's own domain and backlight resides there with it. Site worked great until the 2.0.9 update so there must be something screwy with one of the modules that were changed as nothing else was modified. I'm examining ways to backtrack to the site's state before the update. Looks tricky.
The theme is exported from the blog's domain not the main domain. What steps are you referring to after exporting? I use a child theme to link the exported pangolin theme.
Sorry, I have mistaken your installation for somebody else's.
#267 Re: Backlight 2 Support » Update to 2.0.9 cut my page layout to half what it used to be » 2019-06-18 01:21:04
The site look is a result of code inserted by Wordpress due to the error you have. shortSiteURL() is a Backlight function and Wordpress can't find it.
I think to remember that you have a very special setup where Backlight resides in your main domain and the blog is in a subdomain, but you still export the theme from the main domain. Is this correct? Did you follow all the steps necessary after you exported the theme?
#268 Re: Backlight 2 Support » Update to 2.0.9 cut my page layout to half what it used to be » 2019-06-18 01:13:02
So this affects only your blog?
#269 Re: Backlight 2 Support » Update to 2.0.9 cut my page layout to half what it used to be » 2019-06-18 00:07:36
There is another error:
<b>Fatal error</b>: Uncaught Error: Call to undefined function shortSiteURL() in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/footer.php:393Is the Backlight Wordpress module up-to-date? Maybe export the theme again.
Don't know about the site appearance, apart there is a 700px width setting screwing up the layout. No idea from where this comes.
#270 Re: Backlight 2 Support » Framework Required » 2019-06-17 23:55:33
#271 Re: Backlight 2 Support » Framework Required » 2019-06-14 15:50:50
Did you execute step 5?
#272 Re: Backlight Support » Search Page Corrupted » 2019-06-13 14:26:28
Good morning,
Our Search page has recently stopped showing correctly, see link below:
https://www.piktour.uk/backlight/search/
Our web hosts recently upgraded our site to https so this may be the reason but the rest of the site and the Lightroom connections are all working properly.
I've looked through all the settings and cannot find anything for 'Search' that seems to need changing.
Any ideas?
Thanks,
Neville
The issue is that your search page calls a style sheet with http instead of https. Usually this indicates that the site url points to http://xxx instead of https://xxx. But your site's galleries are correct. So it has to be something else.
Are you using the latest version of Backlight?
#273 Re: Backlight 2 Support » "Something went wrong" » 2019-06-12 23:47:06
#274 Re: Backlight 2 Support » Cart don't work in search module on the results page (Resolved) » 2019-06-12 03:24:41
Thanks!
#275 Re: Backlight 2 Support » "Something went wrong" » 2019-06-12 03:24:24
A newer php version is usually the cause for this error. Just checking, are you indeed using Backlight 2 and not Backlight 1?
If you are using Backlight 1, download the latest version again and install it.