Admin Login Keeps Reseting - Can't Stay Logged In

I have Sytist 3.4.2 and it keeps logging me out of Admin whenever I try a command or menu selection. I keep logging in, sometimes can get one or two steps in and it sends me back to the login page. Is this something that would be corrected if I update to 3.6? Or is there someother issue that is causing this?

Edited by

I also notice the website doesn't seem to retain access code for each gallery. It keeps asking for the access code over and over, eventually it does accept it and let's you into see the gallery. This must be a server issue? Do I need to contact the hosting company, and if so what should I ask them to fix?

Edited Sun Sep 08, 19 2:46 PM by Robert Welch

It sounds like you are out of space on your hosting. It is unable to create the session file to get logged in. You can check in your hosting control panel with your host on your available space. If you are out, you will need to delete some old content from the file manager in your hosting control panel or have your host add some more space to your account. If you see large error logs in your file manager (error_log, errors.txt), you can delete those to free up some space.

Edited by

Thank Tim,

I deleted all the expired galleries I could, and deleted the error.txt file. The database manager for my hosting site says I have 106mb used of 300mb available, so it seems it shouldn't be maxed out at this point. However, I'm still experiencing the same problem of having to constantly log back in as the admin after I click a command or sometimes after clicking a few commands.

Is there something that needs to be reset on the server? Do I need to upgrade for more memory available on the server? It functioned well for almost a year, up until maybe a few weeks ago when it started doing this. Will upgrading to Sytist 3.6 help? I plan to anyway, but if it won't resolve this problem I'd rather get the problem resolved first.

Any suggestions or ideas are appreciated.

Edited by

Updating Sytist won't make a difference. I don't know what the issue is but something on the server. Could be something changed with the PHP session handling.

Try this. In your Sytist admin click Settings in the main menu. Then underneath the left menu click edit config file.

Remove these 2 lines:

ini_set('session.gc_maxlifetime', 3600);
ini_set('session.save_path', $setup['path']."/sy-phpsessions");

Then save and see if that makes a difference. If you can't edit it from the admin for some reason, you can edit that file (sy-config.php) through the file manager in your hosting control panel.

Edited by

Thanks Tim,

I was able to change the config file, but it didn't seem to change anything.

I'll contact my hosting company then. Is there a specific question I should ask them? I guess I can explain what is happening to them, but since they don't know the Sytist software likely, it may help if I could tell them in technical terms what they need to know to fix the problem.

Edited by

I would ask them if you are possibly out of space on your hosting account. It wouldn't be the same as the database space you mentioned before.

Edited by

I was on vacation and just got a chance to get back to this issue. I talked to tech support with my hosting company and he said I'm no where near the data limit on storage, so that wouldn't be the issue here. It's still requiring me to re-enter my log in repeatedly, though it's not as bad as it was.

The tech rep suggested it might have to do with the program requiring me to change my password periodically. I don't guess such a thing is built in the Sytist? Otherwise, he said the problem wasn't on their end, had to be in the database program. Any other ideas?

Edited by

Sytist will not make you change the password.

Email me the link to your Sytist admin, the admin username and password (or create me an admin account by clicking Admins in the upper right corner of the admin pages) so I can look.

Edited by

Thanks Tim, I just setup an admin and emailed you the info to login. Thanks.

Edited by

Same thing happening to me. Was it resolved?

Edited by

Patrick,

Yes, it was the PHP on the server needed to be upgraded. If I remember it was v5.5 and got upgraded to 7.0, but I'm not sure what versions they were.

Edited by