Feature #71868
closed
(Specific) error message if extensions are causing content editing problems
Added by Geg no-lastname-given over 8 years ago.
Updated over 6 years ago.
Description
I faced this problem lately when I updated the T3 core from 7.4.0 to 7.6.0: The update process went perfect, no conflict issues were shown, great. Nevertheless I was neither able to add new content elements (and save them) nor to disable or delete existing elements. Instead I got a blank content window each time I clicked the 'delete', 'disable' or 'save' icons without having any effect to content elements.
Those 'blank window errors' in general are caused by incompatible extensions. But you only know this if you have had some experiences with using incompatible extensions. So my question is:
Is it possible to make TYPO3 produce an error message saying that content editing is not possible because extension(s) xy is/are not comaptible with the TYPO3 version currently installed? I think that would help a lot of admins solving incompatibility problems.
Files
- Project changed from 3098 to TYPO3 Core
- Related to Feature #64513: Add way to installtool to disable extensions, which are not detected as faulty by installtool check added
- Status changed from New to Needs Feedback
TYPO3 8.7.x and above has "Check for broken extension" functionality in Install Tool. Could it be sufficient to consider this ticket closed?
- Status changed from Needs Feedback to Rejected
Upgrades between steps in the development towards an LTS versions need to be done in a development environment to test for issues with extensions. In such an environment a fatal PHP error will normally not produce a blank screen but either display the error or log the error in a log.
In PHP 7 many fatal errors throw an exception instead. These are also caught by the TYPO3 exception handlers starting with TYPO3 8 LTS. In earlier versions we simply can't catch the errors that cause a blank screen (TYPO3 7 LTS still supports PHP 5.5+).
In a development context the exception handlers will show a backtrace that can help you pinpoint the source of the error. In production context a more general error message will be shown (as the details are not useful for most visitors or editors).
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
