Loading...
 
Skip to main content

Features / Usability


Why does it forget that I'm logged in?

Why is that "Remember me" box on the login form if the Wiki is going to forget about me after a few hours and make me log in again?

Why is caching off so that, if it does forget about me after I type but before I post, I can't hit the Back button and retrieve my text if it decides I'm not logged in and disallows the post?

This is one of the few frustrations I have with this program... we have been using it as a work status blog and wiki for our development effort, and it works famously. If it would just truly "Remember me."

The other thing I guess I ought to go log in bugs is how it destroys the text formatting when you enter notes. It would be nice to keep my development blog in a Note all day, then paste it as one blog entry at the end of the day. As it is I update the blog entry all day because it at least realizes when I have hit a carriage return.

Keep up the good work... It is a fantastic product so far...

Another vote against the caching... for some reason I got a server error when I posted that. I hit the back button to try again, but naturally the page had expired. Happily enough the post had succeeded. I have not learned the habit of always copying my post before submitting, just in case. Maybe this one will have convinced me... 😢

I only seem to get the server error if I preview first. Maybe I have found another bug.

I had this as a common complaint until I saw that the cookie expiration was set to be only 2 hours. The max setting that is available in the drop-down (which is in the 'login' section of the 'admin home' page) is 1 week, but that just sets it to 72000 seconds, which is nowhere near 1 week. I had to manually edit the page so the numbers worked for me.

I'm experiencing similar timeouts that are very confusing to my users. It seems to expire the cookies much sooner than the 2 hours that I've set - something along the lines of 15 minutes of inactivity is enough to "forget" a session.
Same for me. Using 1.8.5 multitiki (I thought it could be some mixing of cookies and domains from differetns subtikis).

I guess I missed the admin setting that determines how long it remembers you. Glad I didn't file it as a bug. 😡

The caching thing is still a problem because it can actually cause lost data.

I would think that the cookie would reset itself on every page load, rather than once per session. That would give me X hours after each action, not just after logging in.

Thanks for the help, everyone. I'm off to look at my timeout settings.


I just typed a long reply that got lost because of a db error.

I'll go look at the timeout admin setting, didn't know it was there.

The caching truly sucks because it makes you lose data. I should not have had to type this again. My tone was much happier the first time.

This time I'm using Ctl-A Ctl-C before I submit. I just have to remember to do that on every page, I suppose.

Here's the error I got: Invalid db object passed to CommentsLib constructor