* N°8761 - Assist in cleaning up data prior to uninstalling extensions - handle transaction ID + add deletion plan screen
* N°8761 - poc of deletion plan screen
* code style
* N°8761 - WIP deletion plan execution
* Delete all parent classes objects + cleanup
* 🌐 translation (EN only)
* remove history
* In case of no leaf class to remove, delete also the child classes
* 🎨 refactor & fix typo
* Analysis not stored anymore in DB
* Analysis for removed modules
* 🌐 dico
* Add spinner to setup button "Go to backoffice"
* Fix count after PR review
* Fix after PR review
* Fix Number of elements to remove
* Fix arrays
---------
Co-authored-by: odain <olivier.dain@combodo.com>
N°8760 - Audit uninstall of extensions that declare classes - be able to trace DM classes created_in
N°8760 - be able to test with additional extensions installed in test SDK
N°8760 - provide a service dedicated to extension removal
N°8760 - compute all rules by default
add comment
adapt audit to both extension and mtp
Same as 15d3201a, but this error happened before compilation, when setting read only mode.
As before this is another fix for #351.
This fix introduces the new method \WizardController::GetParamForConfigArray
I replaced existing duplicate code with a call to this new generic method.
Admin will now be able to re-launch the iTop setup directly from the administration console in the Administration / Application Upgrade screen.
Before the only way to launch setup on an existing iTop instance was to change permissions on the configuration file.
This button will be enabled depending on the isDevEnv (if true it will be displayed) and `setup.launch_button.enabled` new configuration parameter (not present by default ; if set to false will always hide the button, if set to true will always display it, if not set will display button depending on isDevEnv only).
Co-authored-by: Molkobain <lajarige.guillaume@free.fr>
