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.
Pages: 1
Hi Backlighters,
After updating to BL2, I get the following error in LR publisher:
JSON.lua:458: JSON.lua:197: can't parse JSON at char 1 of: Unable to load template: ../backlight/modules/module-admin/application/views/templates/template_home.php
I use plugin version 3.2.3.1 that came with BL1.
I tried to uninstall and reinstall, but the error comes back.
Regards,
Offline
Hi, can you update to the new version of the plugin and see if that solves it? You can find the link to download the LR Publisher on the page at Backlight > Backlight Modules. In any case, you need to be using the latest version of our LR Publisher with BL2.
Offline
Updated and installed version 4.0
Still getting the error:
JSON.lua:458: JSON.lua:197: can't parse JSON at char 1 of: Unable to load template: ../backlight/modules/module-admin/application/views/templates/template_home.php
I am also getting this error when I do a authentication check in LR.
Last edited by Crizz (2018-09-10 18:05:02)
Offline
This is a similar error I was getting. A few things to check:
1. Make sure "publisher" is spelled correctly in the API path. Mine was not; I assumed it was my error, but I am not sure how that line gets loaded.
2. I reinstalled 4.0 twice. The second time that path was still spelled incorrectly; once I fixed that it worked. I do still get errors, but it is always on the first try. If I publish (or create New Album) a second time, it works and finds/loads the templates.
Dave
Offline
Can you email me a Backlight admin login and also your Publisher key? (change it to something you can share if needed).
Offline
I think the problem may be caused by BL1 files being left on your server. Is the directory /backlight/publisher still on your server? If so, it needs to be removed.
Offline
It looks like an error with the redirect tripping up Publisher. Adding www into the API URL field should fix it.
Offline
Pages: 1