portal_quickinstaller still seems like a necessary evil tool requiring to view TTW, changes done to the base configuration GS aware packages (manage_installProductsForm).
It provides a view with a list of versioned add-ons in addition to options for installing, uninstalling & reinstalling packages, in comparison to its counterpart prefs_installl_products_form.
Our site has been upgraded from 5.1.2 to 5.1.4, portal_quickinstaller shows the version registered in the database at installed time and the latest version available after the upgrade. For most of the add-ons in the list, packages align well to the version in the file system.
For instance: “Dexterity Content Types” version at install time is 2.5.1 and after the Upgrade the product version is 2.5.1. Thus, matching db and file system.
However, there are other packages showing red in the manage_installProductsForm list and do not match the version after the Upgrade. One example is the package “Mandatory dependencies for a Plone site” => version at install time: 188.8.131.52 after the Upgrade, the product version is: 5.1.4. Thus, showing misleading information.
Technically, why are some packages not aligning to the most recent upgraded version?
Since it is misleading, what is the plan to consolidate features from form manage_installProductsForm into prefs_install_products_form?
Displaying a package version in prefs_install_products_form would be nice, if it is enforced, we’ve got a few costumed add-ons not displaying the version in this tool.
Note: In the above concerns, there is no reference to running upgrade steps — as we know that can be done through portal_setup/manage_upgrades.