Hi,

one or two of my users athttp://www.hififorum.co.uk are complaining that they get logged out when they take too long to reply to a topic. Here's what apparently happens...

Quote:
My XOOPS session timeout is set to 240 minutes, but this apparently happens after around 30 minutes, if not less.

Is this a bug? Is there a setting somewhere that i have not yet found that fixes this?

Thanks in advance, people!

Mine does that. I went to
Admin - System Admin - Preferances and turned off "Use custom session"

OK, well my XOOPS settings are currently as follows:


Surely these settings are system-wide - why should the forum have a shorter session timeout, when the XOOPS site-wide timeout is set to 240 minutes?

i'm confused...

Try going to Admin and selecting "Preferences" from the pop-up menu.

Scroll down to the setting called "Time limit for edit a post". Sounds like this is set to "30". Change it to "0" (zero) and click on "Go" at the bottom of the page.

Given your other posts, I think you need to take a little time to look through the Forums Admin/set-up

JAVesy,
For fun I checked my setting for "Time limit for edit a post", and it is set to 0 Zero. My error was fixed when I turned off Custom session.
I have read a lot of posts and threads here. Usually when I find a post that might answer the question, it will point to

www.LOLThisLinkDoesNotWork.com
or
www.ROFLIGotYouAgainThisDontWorkEither.com

But for fun, check this thread.

Now last night, goofing around I screwed up my test site, after I got Koivi installed into the news module. Now I cant get it installed and I can't remove the editors from CBB (so I only have one) previously.
I am banking that most of XOOPS problems are in the XOOPS Version and frameworks modules. Frameworks being a thorn in my side.
The xoopseditor brought up more issues, I now have
XOOPS/Frameworks/xoops22/class/xoopseditor/dhtmlext
XOOPS/Frameworks/xoops22/class/xoopseditor/dhtmltextarea
XOOPS/Frameworks/xoops22/class/xoopseditor/FCKeditor
XOOPS/Frameworks/xoops22/class/xoopseditor/koivi
XOOPS/Frameworks/xoops22/class/xoopseditor/textarea
XOOPS/Frameworks/xoops22/class/xoopseditor/tinymce
Were I normally just had
XOOPS/class/xoopseditor/dhtmltextarea
XOOPS/class/xoopseditor/koivi
XOOPS/class/xoopseditor/textarea
Why did this happen? I followed what I though was a more up to date link!

This makes me wonder if certain versions of Frameworks and xoopeditor are screwing up sessions.

The 'Time limit for edit post' is the time a user is allowed to edit an already posted reply, not for prolonging posting session. Once the time expires the post is permanent and cannot be edited.

so the solution is... ??

LOL, I'm telling you, Turn off custom sessions.

Admin - System Admin - Preferances and turned off "Use custom session"

As soon as I shut that off, I never got the error any more.

thanks for the advice, but a few questions...

what effect will this have on the session idle timeout? what will it be set to now that my value of 240 is being ignored?

Also, what is the advantage of customizing the session in the first place?

Honestly, I have no clue. I have more issues site wide with "Custom Sessions" than anything else.