Bug #51061
closedExtension manager uninstall extension when suggestions are not installed
0%
Description
When an extension is updated from TER or uploaded file and some suggestions are defined but not installed, extensions manager remove it.
This is defined on line 669 in file typo3/sysext/em/classes/install/class.tx_em_install.php :
} elseif ($this->parentObject instanceof tx_em_Connection_ExtDirectServer) { // with ExtDirect, we are in a context, where we cannot ask the user for feedback // thus we silently uninstall the newly uploaded extension $this->parentObject->disableExtension($extKey); }
- One big problem with this is that if an extension depends on the updated extension, the manager can't handle it and trow this exception:
PHP Fatal error: Call to a member function section() on a non-object in typo3/sysext/em/classes/extensions/class.tx_em_extensions_list.php on line 922, referer: http://typo3package.localhost/typo3/mod.php?M=tools_em
(This is a bug that has been closed because "Fixing this in 4.5 is IMO not needed") [[http://forge.typo3.org/issues/37905]]
- The second problem is that this extension is certainly used to render some content on website and will no render it until we re-install it.
- The third problem (not fully verified) is that it seems that static templates from the extension are removed from inclusion on uninstallation, so after re-installing it we have to set back all inclusions.
If we refer to documentation, suggestions are not required: [[http://docs.typo3.org/typo3cms/CoreApiReference/ExtensionArchitecture/DeclarationFile/Index.html]] (Section constraints)
So there is no reason to remove an extension that have his suggestions not installed.
I checked it on version 6.x and it seems the problem still exists, because "suggests" is defined as dependency and is handle as "depends" or "conflicts".
typo3/sysext/extensionmanager/Classes/Domain/Model/Dependency.php
Updated by Philipp Gampe over 11 years ago
- Status changed from New to Needs Feedback
I do not think that it makes sense to modify the code in the old extension managers. Those branches are in security and priority bugfix period and should not recieve large modifications.
I think that this cannot be fixed by a few lines, but would require a larger rewrite of some functions.
Can you verify this for 6.x? We should fix it in the new EM then.
Updated by Alexander Opitz over 10 years ago
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.2)?
Updated by Matthias Toscanelli over 10 years ago
Hi,
I will check when i have time.
Updated by Matthias Toscanelli about 10 years ago
Hi,
I tested it with TYPO3 6.2.4.
We can close this issue, in version 6.2.4 this bug is resolved.
Updated by Wouter Wolters about 10 years ago
- Status changed from Needs Feedback to Closed