-
Notifications
You must be signed in to change notification settings - Fork 14
session gets corrupted when using "\Zend\ProgressBar\Upload\SessionProgress" #3
Comments
I've just encountered this bug (corrupt session object, using latest ZF3.0.1) and spent a few days trying to find the culprit, which turned out to be the \Zend\ProgressBar\Upload\SessionProgress. What's gotten me upset now is not the bug itself, but the fact that OP reported it August 2015 and it's still present. Is this issue ever going to be addressed ? |
@boournz We need far more information than was presented in the original report in order to reproduce it. If you can provide a reproduce test case, that will allow us to proceed. |
@weierophinney My apologies. I mistakenly presumed that because the issue had been marked as a bug by @Ocramius, it had been verified. I have created a project using the ZF Skeleton app that reproduces the issue I experienced. Two things need to exist for the issue to occur; the session must have a set property, and the view must contain the ZF Progress bar call If the To reproduce the issue, simply load the index.php in your web browser and click the Upload button. You do not need to set a file to upload. The issue results in the $_SESSION containing properties with Check the EDIT
|
any progress of this issue? i face it at 2.4.9 here. i found related PHP bug reported at https://bugs.php.net/bug.php?id=68099 my opinion: not direct relation with session or upload progress instead system can't un-serialize data anyhow [Zend/Stdlib/ArrayObject]. |
If it helps anyone, I came across this this morning, and discovered that someone had set ini_set('unserialize_callback_func','__unserialize_callback_func'); The actual function defined just error_logged the class name. But when I commented out the ini_set, the session started fine. |
This repository has been closed and moved to laminas/laminas-progressbar; a new issue has been opened at laminas/laminas-progressbar#3. |
Whenever you submit a form using "PHP session-upload-progress", and you are also using the ZF session-container object, the session becomes corrupted. It looks like the upload-progress data is being injected into the ZF session data. I can confirm this happens with all releases of the framework. Output of error below:
Stack trace:
Note: just submitting the form corrupts the session container.
The text was updated successfully, but these errors were encountered: