Try searching the forums. I know at least two others have raised this same issue. The other discussions should give some details or at least give you the names of those individuals, who are probably willing to help you out.

Good luck

Sounds like you've missed the template. In modules/system/templates/blocks/system_block_login.html you need to remove the HTML comments. Also make sure you update modules/system/blocks/system_blocks.php and uncomment the 'rememberme' part. Then update the system module once again.

blopy:

When you say 'doesn't work', what do you mean? Does the 'remember me' text start showing up in the login block?

Have you guys 'updated' the system module? There are a couple of template changes which won't take effect until you do so. I think more than 3 files are affected by this hack... search for text 'autologin' and 'remember' in the files.

Catz:

Yes, it is the same one. I notice now that it has been removed from xoops.org. It was committed to XOOPS 2 CVS a couple of days ago, but I think there are still a couple of issues to resolve before it is functioning 100% correctly.

Quote:

What should happen is that the cookie will be set for a week. That means if you visit the site within a week of your last visit, you will automatically be logged in. If you wait more than a week you have to enter your info again. If you explicitly "log out", then you will have to enter you info on the next visit even if it is 5 mins later. Hope this clears it up...

Quote:

Yes, agree with all of this. i.e. Extra preference options for 'enable auto-login' and 'auto-login cookie lifetime'.

I wonder if it would also be useful to have the following - some sites have a link 'click here to learn more about cookies' where they explain the purpose of the cookie, the security risks, and also a bit about the site 'privacy policy'. I have a feeling a lot of people will just blindly use the auto-login feature, but it is very true that it is a security risk, especially on shared computers or for users with admin/moderator access to the XOOPS site.

Quote:
David, sorry, I guess I missed that in the last thread. You posted some other message from phpmyadmin which I did not understand because I've never seen it before.

If I run 'check table xoops_bb_posts' from MySQL command line or phpmyadmin, I get the following output:

Quote:

If there is a problem, I see something about how many rows are indexed and how many rows of data there are. If there's a problem, run the query 'repair table xoops_bb_posts' and then 'check table xoops_bb_posts' to see if it worked.

It could potentially be a problem with *ANY* of the newbb tables (xoops_bb_categories, xoops_forum_access, xoops_forum_mods, xoops_bb_forums, xoops_bb_posts, xoops_bb_posts_text, xoops_bb_topics, but it is probably one of the last three.

Catz,

Good idea. I've only seen 2-3 cases of this, but maybe that is already common enough to warrant doing something about it. As far as I can tell, there is nothing inherently 'wrong' with how XOOPS interacts with the database to be causing this. I suspect certain versions of PHP/mysql on certain platforms have bugs which allow tables to become corrupted when things are not shut down correctly or when multiple users post simultaneously. This is just a guess. Personally I have had this problem not with XOOPS but with another script (phpwiki running under linux, MySQL 3.23, php 4.1.2), where a table suddenly is corrupted for no obvious reason.

We could add an admin link to 'check' and 'repair' the tables (probably ALL XOOPS tables, not just forums). But I've observed that 'repair table' can sometimes lose a significant amount of data (mysql command-line will tell you this ahead of time). In these situations you really need to go through *all* the e.g. forums tables and make sure everything is properly cross-referenced and delete data for partially lost records (e.g. if you have the post title but the 'text' is gone). I'm not sure an admin 'button' can be written sufficiently well that it does the right thing in the general case.

Anyone else who has had this issue, could you post a brief summary of the problem and your fix, and whether you lost any database records or experienced other symptoms after the fix? Anyone have any ideas *why* this sometimes happens?

Thanks!

Just a quick question about this hack:

It seems that the 'remember-me cookie' lifetime and the session lifetime have the same value. Would it be better to separate these so that someone can remain 'logged in' for a long time (e.g. 1 year) without tying up resources (HTTP_SESSION_VARS) for that user. Or have I misinterpretted something? (I haven't had a chance to look at all the modifications very carefully yet.)