I'm new the the whole Elgg platform. I've had it in mind for a few years, but never had the chance to really use it. Now that I've been let loose, I'm loving it.
I have however, think I may have discovered a redirect issue - developers may be aware, but this is just an explanation as to how I came across it.
I'm running Elgg 2.3.15 on Ubuntu 18.04 and PHP 7 via a reverse proxy
I got the site up really easily, but after adjusting a few options in the admin dashboard, I received errors from both Firefox and Chrome about too many redirects - this is when I logged out and attempted to visit the site again
After deleting my test site and starting again, I've identified the issue and can replicate it on demand.
On the admin dashboard under advanced settings I've set the default access permissions to Friends.
Under the site access heading, if you uncheck the Allow new users to register and check the Restrict pages to logged-in users option, this causes multiple redirects and the site crashes.
If you then swap these two options around, the site loads, but will show multiple warnings (in the default theme) down the right hand side 'You must be logged in to view this page'
The way to work around the issue is to either check both options or uncheck both options.... I hope this helps
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Nikolai Shcherbin@rivervanrain
Nikolai Shcherbin - 0 likes
- Jerome Bakker@jeabakker
Jerome Bakker - 0 likes
- Matt H@mattaitch
Matt H - 0 likes
You must log in to post replies.It's not a bug but feature ;)
I haven't encountered a problem like this before.
Maybe it has something to do with the setup (it being behind a reverse proxy)
- the site url configured in the site settings is correct (even http vs https matters). If for example the reverse proxy is handling the ssl encryption it'll send an http request to the webserver. However Elgg still needs to know it's https
- is the website installed in a subdirectory (like http://example.com/elgg/), then please check the RewriteBase in the .htaccess
PS: please check if you can update to Elgg 3.3 as Elgg 2.3 is in LTS and will not get any bugfixes anymore (except security fixes). See http://learn.elgg.org/en/stable/appendix/support.html
Thanks Jerome,
I had added the https, and amended the .htaccess as it's in a subdirectory.
Good shout about upgrading to 3.3 - I'll make that my next step forward as I'm still exploring and learning.