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.
I've tested out the publisher and everything there appears to be working fine. I've just republished a single album and an album set containing 17 albums with no difficulty.
Offline
That's great to hear. Have you by chance followed the BL1 recommendation of forcing clean URLs? I haven't tested it, but I doubt that it would work, since the Backlight admin uses a more advanced URL scheme that would break without additional rules in the Nginx config. The work done on this to date is around removing the need for mod-rewrite rather than providing full support of clean URLs on servers that do not support mod-rewrite or have it enabled.
Offline
Can you share details on your server setup? I'm assuming that you're running Nginx behind a proxy of some sort? The code that had a bug in it yesterday is using logic that doesn't make sense to me -- it detects that the outward-facing URL does not include a port, and then adds the port of the backend web server to any URLs. So if you were visiting a site on a URL like this:
http://yoursite.com
That in turn proxied to Nginx on something like this:
http://127.0.0.1:8888
The web site would end up using URLs like this:
http://yoursite.com:8888
Which is incorrect. The logic should be the other way around: if the back-end web server indicates that it's running on a non-standard port, to omit that port from any URLs sent back to the browser.
Offline
I'm running my Nginx on port 8080 and 8443 behind a router that port forwards 80 to 8080 and 443 to 8443. The Nginx process is running as a non-root user.
Offline
Any reason you're not using Apache?
Offline
I'm running Nginx for a number of reasons:
1) It is easy to strip it down to just the functionality I need and lower the footprint that hackers can use to hack my site.
2) It has a lower resource footprint of memory, CPU, etc.
3) For static content it is significantly faster.
4) When I started self hosting a few years ago Apache use had been in decline for a while and Nginx usage had been growing. Currently Nginx is the most used web server on the net according to Netcraft. https://news.netcraft.com/archives/2019/
I don't believe the BL1 recommendations for Nginx install allowed for clean URL's. So I don't think I was using them.
My main problem right now is that I don't see the Theatre and Galleria modules. Can you check on this to see why my account does not show them? Or should I be contacting someone else?
Thank you for all your efforts.
Last edited by gkar47 (2019-07-11 10:57:00)
Offline
My mistake. I did use the BL1 recommendations for using clean URL's. I just double checked.
Offline
I
4) When I started self hosting a few years ago Apache use had been in decline for a while and Nginx usage had been growing. Currently Nginx is the most used web server on the net according to Netcraft. https://news.netcraft.com/archives/2019/
Netcraft ranking are a moot point for our products. Nginx is not at all common on shared hosts, which many if not most of our customers are using. One of the main reasons behind that is the reason we're here in this thread: lack of .htaccess support, and no way of getting rewrites going without being the web server admin.
Offline
I've updated documentation for getting clean URLs going on Nginx: http://backlight.theturninggate.net/doc … web_server
This should work across the board, both through the main site and the Backlight admin.
Offline
I've applied these changes to my setup and everything appears to be running fine.
I've sent an email through the support page on the missing modules.
Thank you for all your help.
Offline
Matt will need to get back to you on the modules. I believe that you haven’t purchased the BL2 versions of these.
Offline