Bug #30913
closedCaching framework should load exceptions explictly.
100%
Description
As th caching framework is started before autoload setup, it should not rely on autoloading its exceptions.
See news://lists.typo3.org:119/mailman.1.1318536482.28266.typo3-dev@lists.typo3.org for the effect.
Updated by Steffen Gebert over 13 years ago
- Priority changed from Should have to Must have
- Target version set to 4.6.0-RC1
Updated by Markus Klein over 13 years ago
Maybe related: http://forge.typo3.org/issues/30827
Please read my suggestions to autoload Core specific stuff before touching any extension.
For this case, autoloading of Core classes should be even earlier.
Updated by Christian Kuhn over 13 years ago
nosuchcache exception class file should be required in config_default.php in initializeCachingFramework()
Updated by Mr. Hudson over 13 years ago
- Status changed from New to Under Review
Patch set 1 of change I42ac66457776e1b4a4f8dca40e41f364d9496eed has been pushed to the review server.
It is available at http://review.typo3.org/5881
Updated by Christian Kuhn over 13 years ago
Pushed a patch to fix this:
The thrown exception class is now required in bootstrap, so a proper exception is thrown (still fatal) to hint the administrator about the borked setup. The exception handler is still not initialized at this point, so there is no beautified exception, but should give enough information for any administrator to see what is wrong. The rest can not be solved at this point, since the exception handling is not initialized before autoloader and any patch in this direction would be far to intrusive for 4.6.
We could add a section to the caching framework documentation wiki giving a specific problem and solution description for administrators who upgrade TYPO3.
Updated by Christian Kuhn over 13 years ago
Updated by Xavier Perseguers over 13 years ago
- Target version changed from 4.6.0-RC1 to 4.6.0
Updated by Christian Kuhn over 13 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset f8cc8b307c1fcd54c826434388eca5d54eda8aaf.
Updated by Riccardo De Contardi over 7 years ago
- Status changed from Resolved to Closed