Community @ The Turning Gate

Do you mean to display something like -24,91 E ? (which is 71.38 percent of 34.90)

Hi Markus, we have reduced the size of the files that your server needs to download, so even the 32M limit that was failing for some users should now be sufficient.  128M will be fine.
Your custom.css and phplugins will work as before.

You’ll need to get your email configuration working first. Try setting the mail send type to ‘mail’ instead of ‘smtp’ in the main Backlight settings.

Hi Kyle, the reCAPTCHA mechanism has a timeout of two minutes. If a user opens the form and takes longer than that to submit it then they’ll fall into that bucket. The empty response means the user (or bot) made an automated submission that did not interact with the reCAPTCHA mechanism.

We provide a facility to review spam messages so that you won’t miss legitimate messages that get caught out. It’s a learning process for you as a site owner and us as developers. The recommended value of 0.7 is based on real world examples of tens of thousands of visitors on a site I manage.

If for example we get consistent feedback that legitimate messages are getting flagged as timed out then we can look at working  around the timeout or providing an option to promote those messages as not being spam. The two minute timeout is a limit imposed by Google. The workaround is to reinitialise the mechanism closer to the time the user will click submit. I don’t know if that would work if a user completed the form and waited two minutes before hitting submit.

Hi Alfred, thanks for letting us know your upgrade was successful.  That's always good to hear.

Other than you needing to copy the file manually in your case, there will be no further issue related to that.  The files at the top of your site would only usually need to be updated via FTP with the initial installer.  In that case, as the FTP user you have permission to save files there.  It was only in this rare case itself that Backlight needed to make a change to one of those top-level files during an upgrade.  It's not expected that Backlight would have permission to write there, so in your case the manual upload was needed.

This is due to an incompatibility with the version of Backlight you have installed and the version of PHP on your installer.  We put in a fix for this which applies to both Backlight 2 and 3.  Make sure your modules are all up-to-date in the Backlight Modules page.

There's no need to jump ship.  Your Backlight 2 site will continue to work.  We've put a lot of effort to keep it up-to-date with the latest version of PHP.  It should remain compatible for a year or possibly a lot longer, depending on your host.

Thanks John and Jeff.  Much appreciated

Hi Patrick, that sounds strange.  Can you email me a Backlight admin login so I can look into it?

Hi Dieter, there are a few ways to delete the albums from the database:

1) Brute force (warning, this will delete all albums from the database): remove or move away the file backlight/data/publisher/master.sq3

2) Via the Backlight admin.  Visit Publisher then navigate to the album, click on the album name then Delete Album.  This will delete entries in the database and the album files on disk.

3) Directly via the phpLiteAdmin.  That's available under Special Links on the main Backlight admin page.  The password for the phpLiteAdmin page is 'admin' (it's only there to stop users hurting themselves - that page is only available if you are already logged in as the Backlight admin).  This is a bit tricky though, as there is no cascading delete.  You'll want to take note of the album IDs you're deleting, then check the photos that are linked to the album, then also the photo_metadata, photo_rendition and photo_keyword entries linked to the photo.

If you do go into phpLiteAdmin, either to look or make changes, then let me know if you encounter any errors.  There are sometimes incompatibilities that creep in with the latest version of PHP, which I fix as I find them.  It's safest to backup the respective master.sq3 or orders.mp3 (for Cart) files before making changes in phpLiteAdmin.

I'm glad that solved it.  Backlight uses the module but doesn't load it.  That's the job of the php.ini files and system bootstrapping. I can't see how any of the changes from BL2 to BL3 would have affected this.

Can you take a look at your PHP Info (link available und Special Links on the main Backlight admin page) and make sure that there is a section for Sqlite3.  That page should also tell you where the php.ini files are located.  It may be the case though that the actual loading of sqlite3 is handled via a separate config file under conf.d of the same directory as the server's main php.ini file.

Hi Kyle, can you try disabling it there and seeing whether that solves the problem and that the site does operate?