I didn't see myself wanting to go back to the previous version of XOOPS but since I can't get an Autologin for 2.0.14RC1 I'm wanting to go back to 2.0.13.2 and I didn't save my database. I'm wondering if there's a downgrade script available to roll the installation back to 2.0.13.2 so I can get my autologin to work again. I hate having to log back in every 15 to 20 minutes.

Or, is there a "remember me" checkbox hack for 2.0.14RC1 anywhere? I've noticed some sites have the "remember me" login feature but I can't find that anywhere for 2.0.14RC1.

The following link may have some information that will help:

https://xoops.org/modules/newbb/viewtopic.php?topic_id=50958&forum=27&post_id=224810#forumpost224810

Also, have you set the expiration of your session? You can set it to a custom length of time: ADMIN|PREFERENCES MAIN | GENERAL PREFERNCES|SESSION EXPIRATION

Until there is a working autologin, this may at least help.

Thanks Chappy
I'll check that out.

I set the custom session to "yes" and my server is using PHP v4.4 so it should work but I just now went to my site and had to log back in from just an hour ago. The custom session I think only works if you stay connected and on the site but I may be wrong on that. Anyhow, it's not like I want it but I'll figure out something I suppose. I hope I don't have to go back and reinstall everything as I've already got probably 100 users reregistered since my phpnuke site was hacked on the 24th. of last month. the previous site I had up had over 3000 users and when it got hacked I couldn't restore my backup due to junky phone lines disconnecting me and my database was over 14meg but I'm kind of glad it did as I like the XOOPS and XOOPS modules and forum a lot better. Once I get the autologin figured out again I'll be extremely happy with it. I've also installed the Protector module which I think will help a lot in keeping that stuff from happening again.

okay I overwrote all the files from 2.0.14 back to 2.0.13.2 exept for the mainfile.php and some of the modules/system then overwrote the files for the autologin hack then went to modules administration and clicked on update and it all seems to be working properly ... thanks for the help.

there evidently wasn't any database changes from 2.0.14 to 2.0.13.2 so it's all good now.