Bug #73043
closed
TYPO3 stops working after installing the Inventory extension
0%
Description
In a clean freshly installed TYPO3 v7.6.2, I tried to install the 'inventory' extension v1.0.0 (last updated 15-07-10).
When I pressed the 'Import and Install' icon, TYPO3 stopped responding.
After that any attempt to access my my website (backend as well as frontend) gave a blank page. If I ask the browser to show the page source, it shows a blank page - not a single tag gets rendered.
I could not find a way to resurrect TYPO3, so in the end I deleted the whole thing and started from scratch.
I have repeated the procedure 3 times, with the same result every time.
My installation uses a centralized TYPO3 core and each installation sym-links to the code src.
The first time I saw the problem was on a 7.6.0 core which was used by multiple installations, but the last tests were made on a new install of v7.6.2, which wasn't used by any other installations.
Updated by Christian Kuhn almost 9 years ago
- Status changed from New to Needs Feedback
Well, core can't do much here. But it can help a bit:
If a rogue extension kill backend & frontend it can be usually resurrected by opening the install tool (web path typo3/sysext/install/Start/Install.php) and then hitting "check for broken extensions". It will often find the extension and gives you a button to unload it.
Additionally, you should switch to "development" settings in install tool in the presets and you should then get a detailed error message instead of a white page.
All in all this is not a core issue but a problem with the extension.
Updated by Mathias Schreiber almost 9 years ago
- Assignee set to Mathias Schreiber
Hi Henrik,
normally you should get a good pointer in your error logs from either PHP or the webserver.
Another good place to start is by logging into the install tool.
It offers a tool to check for incompatible extensions and will automatically unload them.
The install tool is built to survive almost any outside problems and should be able to get your installation back.
Regarding the extension itself:
It is really old and seems to actively circumvent its maximum working TYPO3 version.
I will discuss with the team how we handle this.
Updated by Mathias Schreiber almost 9 years ago
- Status changed from Needs Feedback to Closed
Hi Henrik,
we checked back with the Extension Manager Team.
The version of the extension is simply too old and does not tell anything about which TYPO3 version it works with.
I am sorry for the hassle you had with it but I will take this incident as a start to clean up the TER from such old extensions that lack compatibility information so you (and noone else) trips over these problem ever again.