Only 200 intranet users? This means there will be at max 4-10 concurrent request. HTTP is stateless protocol and even if everyone is online simultaneously, not all requests will arrive to server at the same time. XOOPS should work like charm But consider enabling caching if content permits that.

Let us know, how it goes?

Check include/version.php

Feel gfree to message me on YM - my id is 'sudhaker' (if you seek any quick help).

Thanks,

U sure you applied it over XOOPS 2.0.9.2 ?

XOOPS_ROOT_PATH is not getting translated, this smells like real problem.

Can you post your mainfile.php here (obviously after masking your db password, if problem is still there)

Does this mean, $xoops_showrblock is also redundant?



Which one will be better? Conventional or this one?

I would place it after this block



Anywhere inside outer if but before 'common.php' include will work fine.

Sorry for the confusion.

U just need one line added to mainfile (only if you are not happy with one week).

define('XOOPS_AUTOLOGIN_LIFETIME',2678400);

[ code ] and [ /code ] doesn't have any meaning in PHP context. It was added for newbb forum. See the background and border around the code in below line.



Cheers,
Sudhaker

Myths about autologin + email hack

Myth1: It increases server and database load heavily because garbage collector will not be doing clean up. I can’t afford it because my concurrent user count is huge.

Fact: It will not increase the load any significantly. Query to xoops_session table will return few extra bytes and ‘Who’s online’ block will pump more uname(s). That’s it. XOOPS always creates a record for any new sessions (no matter if the session is anonymous or member’s). So query count stays same. And we see more realistic information in ‘Who’s online’ block and members can have pleasant browsing. I’m sick of seeing ‘no permission’ as my session gets expired while typing response (may be I should type fast – hehe).

Myth2: Oooo, is it safe? We can’t compromise with security B-).

Fact: It is far safer than storing username/password in the browser. Yes, it is little less safe than normal operation, but eventually it is exactly same logic what cookie based session persistence have. The only difference is – server can release resource as usual but you get a fake feeling of extended session using saved cookies. It will be transparent to end-user as server will create new session without authentication.

Assuming possibility of session hijacking, without this hack you are vulnerable during your current session only. But with this hack the period is extended till auto-login is valid. Big vendors like gMail (2 weeks), Yahoo Mail (24 hours) also use similar mechanism with similar risks.

Myth3: Cookies are saved on user’s computer. We lost the control

Fact: Site admin can invalidate all (or some) saved auto-login. Clear up actkey column in xoops_users table, done. Those save cookie is trash now.

Myth4: You guys are great, doing awesome things

Fact: The actual credit should go to XOOPS team who has done this great work. We are just tweaking the application to satisfy our personal urge and need. Sometime hacks are worth sharing in the community. So we come up aboard

I wish, I could get more free time and opportunity to contribute more

---

I’ll not advocate this hack to any critical site dealing with big $$$. But now many of us have critical site, so IMHO this hack is a MUST HAVE for most of people .

I also request XOOPS core team to consider merging this into main distribution. Ideally, a site parameter (entry in table xoops_config or mainfile.php) can be used to enable and disable the feature and parameters.

Cheers,

Perhaps I suggested one more improvement by mistake

I couldn't see XoopsMemberHandler::getUsersByGroup() in CVS Perhaps not commited yet... But great idea !!!

I had to do batch fetch in similar situation in my last project. Some database has limit on number of criteria you can put in where block and Sybase was having limit of 255.

Surprisingly MySQL doesn’t have any problem with 100 thousands items in IN block. So, changes are even simpler...

Thanks for quick response I was almost in hibernated mode for last more than 6 months. It happens when you had to drive 70 miles one way daily to work and project has very tight dead-line.

I’m finding more free time these days so became visible in community again. I have not gone deep into CVS to track the changes (except for my suggestion), but I surely felt that XOOPS has become faster. THANKS TEAM Also community is flooded with great modules and themes. GOOD WORK

Cheers,