Strange bugs

[aaxsplash]

Hello,

Since i've updated from 2.0.2 to 2.1, I ve noticed 2 problems :

- The mini and maxi reservation duration doesn't work. So "Reservations must be made at least" works !

- When i try to logout with user profile, it puts me on dashboard page and don't log me out. But i can log out with lots of machine gun clicks on "sign out" !

Well well.. I've tested on another v 2.0.2 (updated from 1.2.12) in the same server and i ve not that.

Thanks for help

[Nick]

- The mini and maxi reservation duration doesn't work. So "Reservations must be made at least" works !

I'll take a look!

- When i try to logout with user profile, it puts me on dashboard page and don't log me out. But i can log out with lots of machine gun clicks on "sign out" !

Any errors being logged? Are you using any authentication plugin (LDAP, etc)?

[aaxsplash]

No errors when logged. And no authentication plugin, it's a standard install and update.

I ve some précisions about this log out problem. If I click on sign out :
- 2 times slowly, i stay logged
- 2 times quickly, i stay logged
- 3 times slowly, i stay logged
- 3 times quickly, i m logged off

 

[Nick]

Are you using the "stay signed in" feature when logging in?

[aaxsplash]

No

[bille]

I am having the same logout problem with 2.1.  aaxsplash is correct, I was able to logout with three quick clicks (sometimes two).

I AM using the "Remember me" check box.  I have considered this as something that would put my user name back in the "Username" box or possibly log me in automatically but not that it would prohibit me from logging out.  How should the system respond when that checkbox is checked?

Once I was able to get back to the login screen, I logged in without the "Remember me" checked.  I still could not log out with a single click.

Different strange:  I was trying out the configurable start time restraint (thankyou!) but am not getting the results I expected.  Using "current" I created a reservation that started in the current half-hour and then tried to extend the reservation.  The system happily took my changes and gave me a success box but when I got back to the calendar the blocked time was for the original reservation.  Hovering over the block gives me the original start and stop time.  Clicking on the reservation gives me the original start and stop times.  I can not delete this reservation either (even though the system says that it has been deleted).  I have not been able to try the 'none' setting yet until the current time gets beyond the current reservation.

Thanks for a great program!
Bill

[bille]

Reservation update:

- An admin CAN delete the reservation that contains the current time that the user could not
- Using 'none' for start time constraints does not change the behavior; Can not extend reservation, can not delete the reservation even though the message box says successful.  This seems to apply only to reservations that do not contain the current time.  I was able to create and delete a reservation that was entirely in the future.

Bill

[smuasini]

Hi, any update on the logout issue? I'm using 2.1.1 and same thing happening. Cannot logout for user with single click.

Thank you

[Nick]

I'm working with Bill to dig into these issues

[smuasini]

Thank you Nick. Much appreciated