Menu

#2971 "Cannot unset string offsets" when session expired.

3.2.5
fixed
nobody
5
2013-06-11
2010-01-27
hosstito
No

PMA Version: phpMyAdmin-3.2.5-all-languages
PHP Version: 5.2.3

When using Cookie authentication, an expired session will lead to the following error when you log back in and try to modify a record:

Fatal error: Cannot unset string offsets in /phpMyAdmin-3.2.5-all-languages/libraries/common.inc.php on line 947

To reproduce it, login to a PMA install using cookie authentication and leave it open in your browser for a time period longer than whatever is set for "LoginCookieValidity" and "session.gc_maxlifetime". When you then click on a table name, it will pop you back to the main login screen (correctly). After you log back in, you will be able to click a table and browse it's contents, but when you click on the "Edit" link for a record, the right frame just loads the above Fatal error.

Nothing is generated in the Apache error_log at the time that this occurs. Closing and re-opening the browser and/or clearing your browser cookies for the phpMyAdmin server usually fixes the problem.

I think that's everything important, but let me know if you need any other information.

Discussion

  • Herman van Rink

    Herman van Rink - 2010-02-03

    Proposed patch

     
  • Herman van Rink

    Herman van Rink - 2010-02-03

    3.2.5 is not really the latest svn version, we're working hard on 3.3 and 3.4 already ;)

    Some experimentation never resulted for me in the error you mention.
    But does the attached patch resolve your situation?

     
  • hosstito

    hosstito - 2010-02-12
    • milestone: 284140 --> 3.2.5
     
  • hosstito

    hosstito - 2010-02-12

    Thanks for the info Helmo. I have been testing the patch for the past few days and I thought it had fixed it, until I tried leaving a login open from my work computer. Then, when I came home and tried logging in and viewing a record, the same "Cannot unset string offsets in common.inc.php on line 949" occurred again.

    So it seems that it might not be directly related to LoginCookieValidity or session.gc_maxlifetime, but something to do with logging into the same DB with different computers possibly? I guess it could still be related to cookie management though.

    Thanks again for the help and information :)

     
  • Herman van Rink

    Herman van Rink - 2010-02-12

    I doubt that logging in on another computer is really related as every browser maintains it's own session with the server. Or are you working on a laptop that you take with you?

     
  • Marc Delisle

    Marc Delisle - 2010-03-06
    • status: open --> pending
     
  • SourceForge Robot

    • status: pending --> closed
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • Michal Čihař

    Michal Čihař - 2013-06-11
    • Status: closed --> fixed
     
MongoDB Logo MongoDB