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.
Thanks. That's the difference. The download.php rule in..htaccess breaks the download function for FastCGI.
If you could check your PHP Info (available via the link on the Backlight Admin home page) and see what it has for PHP handler then that would be helpful. Look for either FastCGI or Apache Handler
Without further details or access to your galleries or Backlight, I have no idea.
The two rules I asked you to comment out are redundant. They can cause problems on specific Apache setups, I suspect when PHP is handled through FPM/FastCGI.
I haven't seen that specific error related to downloading. One thing to try is to edit the .htaccess file used by Albums:
1. Visit Admin > Settings
2. Scroll down and click Show Advanced Settings
3. Click Edit Settings
4. Edit the Album .htaccess field, adding '#' at the start of the line referencing download.php, and that immediately preceding it so that those two lines look like:
#RewriteCond %{QUERY_STRING} !mod_rewrite=on
#RewriteRule ^(.*)download.php %{ENV:BASE}download.php?%{ENV:QS} [QSA,L]
5. Click Save Settings
6. On the main Backlight landing page, click Update Album Files in the Special Links section.
If that doesn't help, then please email me with album details, a Backlight admin login and FTP details, so that I can investigate further.
I've released a silent update that removes the (md) from the album/set Description field. This can be installed by clicking "Reinstall" on the module-publisher entry n the Backlight Modules page.
I’m not sure what’s going on there. Can you provide an FTP login and Backlight admin login via email, so I can look into it?
That level of logging will cause a negligible performance hit to your site. 4,500 lines correspond to a few kilobytes. Probably less work by the server than needed to process a single PHP request.
Having said that, those entries don't look to be necessary. I'll try and find where that log output is being generated and remove it from our code.
Hi Bob, have you tried changing the permissions on the backlight/modules directory?
This looks to be an issue specific to PHP on Synology NAS, and not related to Backlight. See if this helps:
https://stackoverflow.com/questions/414 … -php-error
Hi Dennis, I'm sorry to hear that you're still stuck. I am in a better position to assist than when we last emailed, but I still can't log in via FTP.
Pierre, it seems like you have installed the backlight files in a directory called backlight. The easiest is to change the MAMP server (Preferences > Web Server > Document Root) to point the root directory like ..../sites/nathaliemoliavkovisotzky/backlight.
As above, 'backlight' should not be used as the directory name of the site itself.
Can you copy and paste the contents of the MAMP config for the virtual host entry for this site.
Also, can you open a terminal, change to the directory that is specified in the DocumentRoot setting For your virtual host, run the following commands and paste the output here:
pwd ; find . -maxdepth 2 -type d
Something else to check is that the correct index.php and .htaccess files are at the top of the site and in the backlight directory respectively.
The first thing to do is change the name of the site directory. "backlight" is a special name that's used to work out paths. Naming the actual site as that can trip things up.
Can you provide a URL where we can see this issue, and also email me a Backlight admin login so that I can see what's going wrong?
Everything should work fine in MAMP. Backlight 1 and 2 were both developed with MAMP. If you encounter any issues please let us know.
As Rod mentioned, you may be exceeding the upload_max_filesize. Another limit that may be exceeded is the memory_limit. This is the amount of memory allowed per request. It's quite likely that the resizing algorithm used on the server needs to store the full uncompressed bitmap of your upload during the resize process. A third limit could be the max_execution_time. If your large uploads exceed that amount of time during upload and processing then the connection can be lost.
Are you exporting images on your PC especially for uploading through Backlight? If so, you probably don't need such large images. Consider the largest image size made available in your template, and upload files that are at least as large as those, in high quality.
This is caused by some kind of permission issue, and all things being equal would happen on both BL1 and BL2.
I'm not sure why it happens because the code successfully checks that the directory can be written to before trying to open a file in that directory, where the error occurs.
Grover, can you provide me with FTP access via email, and steps to reproduce it?
Hi Pierre, as I'm not able to access your site via FTP, can you try updating the BL1 site, following the steps to upgrade to 1.2.3 here: http://backlight.theturninggate.net/doc … _changelog
The file causing you an issue is at
backlight/framework/helpers/SimpleHTMLTag.php
If you want to just upgrade that, then it *might* solve the problem, but there are likely other fixes that will need to be made, which will need the full upgrade steps in the above document.
Editing an album causes it to be created in the server if for some reason it doesn’t exist there.
Matt built it, Rod helped test it, I got it to you
If you can share an FTP login via email I’ll have a go at fixing your BL1 site.
The latest download for BL1 solves compatibility issues.
Your certificate is valid for ronnymaes.be, ronnymaes.com and ronnymaes.eu but not for www.ronnymaes.com
Hi Thom, sorry for the late reply. I will look into this tomorrow.
Matt will need to get back to you on the modules. I believe that you haven’t purchased the BL2 versions of these.