Thanks for the comments.
The 775 permission doesn't make any difference since the owner of the directory is the only member of the group.
The live_site ABSOLUTELY SHOULD NOT BE EMPTY. I have raised this before, and never got any response. Joomla DOES NOT WORK without live_site being specified if the environment is PHP-FPM.
"Login as user" is not a login module in the general sense. The login module for normal login was the standard Joomla version, which is what I stated. I had tested disabling "login as user", and that made no difference.
Why is it preferable to use filesystem session handler? I have found it problematic in the past.
I have now found the cause of the problem. The size of the #__sessions table was huge. Why does Joomla not deal with this? Or at least give a warning if it is very large? I guess switching to filesystem would have fixed the problem (I actually used the Joomla prune utility and added it to cron jobs). But past bad experiences discouraged me from doing that.
The 775 permission doesn't make any difference since the owner of the directory is the only member of the group.
The live_site ABSOLUTELY SHOULD NOT BE EMPTY. I have raised this before, and never got any response. Joomla DOES NOT WORK without live_site being specified if the environment is PHP-FPM.
"Login as user" is not a login module in the general sense. The login module for normal login was the standard Joomla version, which is what I stated. I had tested disabling "login as user", and that made no difference.
Why is it preferable to use filesystem session handler? I have found it problematic in the past.
I have now found the cause of the problem. The size of the #__sessions table was huge. Why does Joomla not deal with this? Or at least give a warning if it is very large? I guess switching to filesystem would have fixed the problem (I actually used the Joomla prune utility and added it to cron jobs). But past bad experiences discouraged me from doing that.
Statistics: Posted by counterpoint — Mon Nov 25, 2024 2:10 pm