Community @ The Turning Gate

Support community for TTG plugins and products.

You are not logged in.

#1 Re: Backlight Support » Publisher can't publish new album - Disk Error » 2018-06-20 22:04:50

Ben

Hi Alfred and Michael, that sounds like some promising progress on the issue.  Michael, are you able to ask your host for a similar change, or ask where in your control panel or files you could make a similar change?  I can't see it being a change anywhere in Alfred's hosted files.


EDIT: Michael, looking at your phpinfo page, it looks like the TMPDIR is already set in the same way as it has been for Alfred.  Is this the result of you contacting support?  If not, they may have provided a global fix.  Are you still getting errors?


To be honest, I'm not impressed with your host's remarks on this.
A properly-configured PHP environment should have SQLite writing to the correct locations, without any need to configure this.  This "one time courtesy" is fixing something that should not have been broken.
We have been very pleased with SQLite as a technology, which has exceeded our expectations.  It is fast and robust.  We have had thousands of supported installations over the years, with some sites having tens of thousands of photos, without any noticeable degradation of performance, or any loss of data integrity.
MySQL would be a more performant and robust solution, but I see nothing lacking in SQLite for what we need in Backlight.  The huge benefit of using SQLite is that the data is managed through files, and requires no setup of databases and users through the control panel, which would be a massive headache for us to advise across the various hosts that our customers use.

#2 Re: Backlight Support » Publisher can't publish new album - Disk Error » 2018-06-20 18:27:03

Ben

Hi Michael, that is strange. Can you email me with the names of the files on the server or the two files themselves?

#3 Re: Backlight Support » Publisher can't publish new album - Disk Error » 2018-06-20 07:15:09

Ben

Hi Michael, I don't think it's a sign of a corrupt database, unless that is another issue again.  When I looked at your site, I made a copy of the database, exported it as SQL and re-imported that SQL into a new database.  Doing that ensures that the integrity of the master.sq3 file itself and internal structure isn't an issue.  That didn't help the problem.
Your method may have found a way of unlocking the file as far as the file system or SQLite management is concerned.

#4 Re: Backlight Support » Publisher can't publish new album - Disk Error » 2018-06-19 07:23:56

Ben

Hi Michael and Alfred, I'm pretty sure you're both using the same host.  Can you share the name of the host? 
Michael, were you able to get this resolved for your site?

#5 Re: Backlight Support » Can't update this collection error » 2018-06-16 09:12:32

Ben

The error you encountered was because the server didn't receive the 'cs' parameter from Lightroom.  That's a checksum that ensures the request was signed with your API Key, and is sent on every request.  If it doesn't happen again I'd put this down to a quirk in LR not sending things properly or the parameter getting lost somewhere along the way.

If it does happen again, can you zip up the ttg.log file (found in your Documents folder on your PC or Mac) and email it to me with the address in my signature?

#6 Re: Backlight Support » EU Data Protection and Google fonts » 2018-06-09 06:51:02

Ben
Matthew wrote:

Have gotta say, though, that aspect of the EU regulation is bloody stupid.

Apparently this is in response to Google logging IP addresses of font requests and using it for analytics.  In that case, relying on picking up the fonts from local edge servers probably wouldn't help.  Keeping a copy on your own site would be the solution.

#7 Re: Backlight Support » Any news/update on a standalone Backlight? » 2018-06-08 11:08:48

Ben

Not all functionality will be supported from day one though.  Of note, watermarks won't be supported.  Support for metadata will be limited and built on over time.

#8 Re: Backlight Support » Any news/update on a standalone Backlight? » 2018-06-07 08:05:02

Ben

Backlight will support the management of albums and upload of photos within the admin webpage itself.  No 'ingestion' as such.

#10 Re: Backlight Support » Publisher can't publish new album - Disk Error » 2018-06-07 07:55:16

Ben

Hi Michael, I've only now had a chance to look into this.  I'll have a go at creating a hidden album tonight to see whether I can see the problem.
Looking into database locking, this sounds like a database that hasn't been closed properly.  Backlight does not explicitly close database connections, as PHP is meant to automatically close them at the end of each response.  There's an extra measure I can take to try and close them just before that is meant to happen automatically.  That *may* help the problem from happening again, but probably won't solve the current locking.

Publisher touches Wordpress themes due to menus that may be affected by changes to the album structure.

#11 Re: Backlight Support » Backlight response file list typo? » 2018-06-05 06:17:24

Ben

It’s a quirk of the email system. The spaces get added in transit, somewhere between Backlight sending the email and ending up in an inbox.

#12 Re: Backlight Support » Publisher can't publish new album - Disk Error » 2018-06-04 16:31:11

Ben

That looks like a server error. Perhaps a full disk on the server. Can you download the file backlight/data/designer/master.sq3 and email it to me, so that I can check that the file itself isn’t corrupted?

#13 Re: Backlight Support » 503 error » 2018-06-02 09:24:55

Ben

This looks to be a server issue.  Your host is blocking requests.  Have you tried contacting them about this?

It's possibly a denial-of-service detection that's blocking the publisher after too many calls.  We added a delay field in the latest LR Publisher module that can be used to space out requests to the server in case the frequency of requests is causing them to be blocked.  If you double-click on the Publisher instance, you should see a setting 'Delay API Requests by [5.0] seconds', underneath the 'Publish thumbnails without updating other renditions' checkbox.
If that setting isn't there, then download the latest version of Backlight and re-install the LR Publisher.

Try enabling that, to see whether it helps.  You may need to change the duration to something that is effective in avoiding the problem but not too long to make publishing tedious.

#14 Re: General » Charlie Choc » 2018-05-19 15:16:16

Ben

That's very sad news.  Looking at his blog, he had a really tough final few months.  Thanks for sharing, Rod.

#15 Re: Backlight Support » GDPR » 2018-05-16 16:41:37

Ben

I’m not sure that the contact form is an issue. Nothing is saved on the server. What do you think?

#16 Re: Backlight Support » Slow Loading Home Page. » 2018-05-05 21:28:38

Ben

Hi Evagoras, I've found the problem and fixed it.  It looks like the wrong index.php had been copied to the top of your site.  That meant that the individual page requests weren't being forwarded to the application.  Do you know which file you may have copied in?
In any case, this is fixed.

#17 Re: Backlight Support » API Keys, Test and Live » 2018-05-03 06:11:24

Ben

I haven’t looked at the PayPal side for a while. What are the four choices?

#18 Re: Backlight Support » GDPR » 2018-04-28 07:41:11

Ben

Gravity Forms is a Wordpress plugin.  Backlight is not a Wordpress system, so I don't see how that would work.

Thinking through this, there aren't many holes left in Backlight for GDPR compliance:

* Clear inline GDPR terms with checkboxes can be added for both transactionless and paypal checkouts
* The contact form does not save data on the website, so should not be affected.  This instead only emails the contact details.
* Managed Client Response information is entered by the photographer/site owner.  I'm not sure how this point of data entry would need to comply, as it's not entered by the customer, so does not present an opportunity for a customer to agree to anything.
* Cart orders and CR responses can be deleted with the admin function

Where Backlight falls short then is in:

* Standalone client response submissions.  There is no facility for checkboxes or terms here.  I suggest for now that you don't use this function.
* Deep deletion of customer details from backups.  The brute force approach is to delete the sq3 files from backlight/data/cart/database_backups and backlight/data/client-response/database_backups.  I would imagine that a request from customers to remove data will be rare, so this isn't something you would be doing often.

Have I missed anything?

#19 Re: Backlight Support » Customer information access » 2018-04-27 06:52:53

Ben

It would be better to continue existing topics on GDPR than create new ones.

As Rod said, order information can be deleted from backlight > Cart > Orders.  Find your order, click the order number, then click Delete Order.

Backlight makes database backups for each upgrade.  To delete customer records from these, the most straightforward and blunt way would be to delete all orders*sq3, (e.g. orders_3_0_4.sq3, etc.) files under backlight/data/cart/database_backups/.  The backup mechanism is to provide a recovery path should a backup fail completely.  If your site is operating correctly, then there's no need to keep past backups.

Beyond the scope of anything we can do on this is customer data on server backups that your host has made.  I'm sure that that will be a headache for hosts operating in the EU.

#20 Re: Backlight Support » GDPR » 2018-04-23 07:22:40

Ben

TTG is not working on this for existing products.  I'm not yet sure the best way to handle this, considering these are changing business requirements for a product already functionally complete.  Our pricing model simply can't cover retrospective updates to products that were fit-for-purpose at the time of sale. Perhaps a software bounty might work.

#21 Re: Backlight Support » Not a Secure Website » 2018-04-22 07:47:50

Ben

To make the Not Secure message go away, you'll need to set up SSL on your site.  That's likely something you can configure via your host's control panel.  It will typically incur additional costs.  After setting that up, you would need to change your Site URL so that the http portion of the URL is https.

I'm not sure whether that would prevent anybody from accessing the site.  I was able to login without issue, which suggests there's nothing wrong with the site itself.  What exactly does the client see when it 'does not work'?

#22 Re: Backlight Support » cart popup doesn't load » 2018-04-19 18:30:53

Ben

Hi Thom, this is something for me to look into.  The behaviour of PHP and errors thrown keeps changing for each minor version, since 7 came out.  We've had problems with 7.1 and now 7.2.

#23 Re: Backlight Support » Login first time trouble » 2018-04-17 20:01:38

Ben

The 'backlight' link assumes that the backlight directory is at the root of your site.  Your 'backlight' directory is instead at http://brogaard.com/backlight/backlight/

Is that intentional to have placed the 'backlight' directory within your own backlight directory?  Using 'backlight' as the name of directories other than the one that ships in the zip file can cause problems.

#24 Re: Backlight Support » Unable to save settings Error 200 » 2018-04-14 07:02:30

Ben

Can you provide me with a Backlight admin login via Email so that I can look into this?

#25 Re: Backlight Support » Protected Album [Again!] » 2018-04-13 21:50:22

Ben

Can you provide me with a Backlight admin login via email so that I can try and look into this?

FTP access would probably be helpful too.

Board footer

Powered by FluxBB