Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI'm using the standard file-based sessions provided by the default PHP session handler, so this information is purely server-side. And no, you are incorrect. The class definition IS loaded. It is trying to load the WRONG definition. As proof, sometimes it picks a random string that actually DOES match with a defined class. In these cases, it creates an instance of that class from the session content, and then (our code) proceeds operate on it with functions that don't exist in that incorrect class, which is where we get some error logs as well.
      singulars
    2. CO@VexedPanda try logging the object to a file (use var_export on the object and save it) right before you serialize it with a timestamp. The next time you see the error, check the log to see the state of the object prior to serializing to confirm the object is as expected going into the session.
      singulars
    3. CO@VexedPanda also, you mention you have a FM_LoginLogging class... I use zend framework 1.x. Before php 5.3, Zend had a bunch of work arounds for namespacing and autoloading. I know it allowed you to namespace and autoload without class prefixes... so for example a class FM_LoginLogging could be set to autoload sans the "FM_" prefix. In this case you'djust use 'LoginLogging' and it would map the class. Something like this could be a problem if PHP saves the object with it's true class name, but an internal object reference inside the framework uses the shortend class name (or vice versa).
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload