Feature #70049
closed
Show permanently a warning in EM that dependency check has been disabled
0%
Description
Hi,
what happens if there are more admins and one deactivates the dependency check?
The next admin will not know that and possibly rely on that feature.
So he could install an extension that will not work and crash the system...
The most important feature request of this issue: show deactivated dependency check in EM.
As quick hint: where can I find lowlevel the necessary information?
Is it possible to show violating extensions and restore a state with active dependency check?
This could be the state of active extensions in the moment where the dependency check has been disabled.
Or more advanced inactivate all violating extensions and enable the dependency check again.
BTW: I installed an ext with a dep to another ext the update of which should be blocked by excludeFromUpdates. It was possible! Either it's a bug or the dependency check was disabled. I want to reproduce the bug therefore I have to know if the check is disabled and how can I restore the check. (Or take a fresh system.)
Updated by Daniel Wagner about 9 years ago
- Target version set to next-patchlevel
Updated by Daniel Wagner about 9 years ago
- Target version deleted (
next-patchlevel)
Updated by Nicole Cordes almost 9 years ago
- Status changed from New to Needs Feedback
There isn't any option to disable the dependency check for the Extension Manager. You can only disable it for one installation request. How do you come up with such a thought? Can you describe your case a bit more?
Updated by Daniel Wagner almost 9 years ago
There isn't any option to disable the dependency check for the Extension Manager.
There is no option in general, but every time you install an extension the requirements of which cannot be met a dialog appears where you can disable the system dependency check.
You can only disable it for one installation request.
And this mechanism is not explained good enough - or I have not found the documentation yet ;)
How do you come up with such a thought?
To realize a dependency management that checks and assists every change of extension states the dependency graph has to be evaluated with every install and uninstall in the extension manager. If you allow to install one extension with "invalid dependencies" the dependency manager could possibly not create a valid state with the next install/uninstall. So you have some special rules to handle this case which needs some state / storage, right?
Consequence: extensions ignored by/overriding the dependency management should be marked in the extension manager.
I am sorry for my bad explanation, but it's nearly 5 months ago and this how I understood my explanation today (not sure anymore, really sorry):Can you describe your case a bit more?
- There were two extensions A and B
- Extension A had been installed
- Extension A had been set to excludeFromUpdates
- Extension B was dependend on A (B->A)
- Extension B has been installed freshly
- Extension A has been updated automatically to meet the dependencies although updates were forbidden
This must have happened in a TYPO3 6.2.x.
Updated by Alexander Opitz over 8 years ago
- Status changed from Needs Feedback to Closed
The information if an extension was installed/updated with "disabled dependency check" isn't saved anywhere. The question will pop up every time if you try to install/update an extension which runs in the same dependency tree.
If you encounter a problem, that an extension which was marked as "excludeFromUpdate", was updated without the "disabled dependency check", then please create a new issue and provide steps to reproduce.
So I'll close this issue. Thanks for your comments.