Bug #65535
closedException: Serialization of 'Closure' is not allowed
0%
Description
Hello,
I wanted to test following issue https://review.typo3.org/#/c/37483/
With contained TypoScript my TYPO3 master throws following Exception:
Exception: Serialization of 'Closure' is not allowed
The exception was thrown in last line of GifBuilder->fileName():
public function fileName($pre) { /** @var $basicFileFunctions \TYPO3\CMS\Core\Utility\File\BasicFileUtility */ $basicFileFunctions = GeneralUtility::makeInstance('TYPO3\\CMS\\Core\\Utility\\File\\BasicFileUtility'); $filePrefix = implode('_', array_merge($this->combinedTextStrings, $this->combinedFileNames)); $filePrefix = $basicFileFunctions->cleanFileName($filePrefix); return $this->tempPath . $pre . $filePrefix . '_' . GeneralUtility::shortMD5(serialize($this->setup)) . '.' . $this->extension(); }
IMO the line 225 is the problem:
$this->setup[$theKey . '.']['BBOX'] = $fileInfo;
Here you fill in the complete FAL-System with all recursive/needed Objects. Again: We fill Objects into our lovely text-based TypoScript Array.
With following patch: https://review.typo3.org/#/c/37485/ the Exception will not appear anymore, but the problem is still there. The Objects are still there. After serializing this structure we have a nearly 100KB string which is needed ONLY to create a unique hash for a file.
Stefan
Updated by Gerrit Code Review almost 10 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37556
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack over 9 years ago
- Target version changed from 7.5 to 7 LTS
- Sprint Focus deleted (
Stabilization Sprint)
Updated by Riccardo De Contardi about 7 years ago
- Status changed from Under Review to Closed
- Assignee deleted (
Nicole Cordes) - Target version deleted (
7 LTS)
We think it is safe to close this issue; the patch has been abandoned as not needed anymore, thus the issue
is no more relevant.
If you think that this is the wrong decision or experience this issue again on recent TYPO3 versions like 8.7.x and 9.0.0,
please reopen it or open a new issue with a reference to this one.