[TYPO3-core] RFC #17320: Not installing extensions in Upgrade Wizard should also get rid of the wizard

Ernesto Baschny [cron IT] ernst at cron-it.de
Wed Jan 26 09:52:39 CET 2011


François Suter schrieb am 26.01.2011 09:42:
> Hi,
> 
>>> How to test:
>>> >  Run the wizards, don't install anything. Run the Upgrdae Wizard
>>> again:
>>> >  They are gone, amazing!
> 
> This could probably be used in the workspace migration wizard too, but
> it's a bit more touchy, because the wizard should really be run through
> when there's at least one bit of versioning/workspace-related stuff
> install. OTOH if nothing is installed and the user doesn't want to
> install anything, it should "disappear" like the other wizards do now.
> But this doesn't need to be fixed, as at least the workspace migration
> wizard does not "fail" when skipped.
> 
> Anyway this new mechanism introduces interesting possibilities for the
> wizards and we should probably revisit them all in 4.6 (for example, the
> compatibility wizard; it should be possible to make it go away too, when
> one doesn't want to switch compatibility version anymore). In an ideal
> world the Update Wizard should be completely empty in a fully updated
> installation.
> 
>> Committed to trunk, rev. 10318, so that it can be tested in RC3.
> 
> My post-commit +1 by reading and testing.
> 
> Thanks for coming up with this solution.

Yes, I have implemented this "quick and easy" way right now because its
pretty bullet proof because its very easy. These were other thoughts I
had while doing it, just for the record:

- there are wizards which might need a revisit on each release, because
new stuff is added to it. F.e. tx_coreupdates_installsysexts used to
install 'about', 'cshmanual', 'feedit', 'opendocs', 'simulatestatic' in
4.4 and in 4.5 we added 'info', 'perm', 'func', 'filelist'. So I thought
I need to mark the branch number in which the user decided to skip the
wizard, so that it can be shown again on future updates. But then it
would require to maintain a list of branches where the user has already
"skipped" it (to be able to detect jumps when upgrading, for example
from 4.3 to 4.5) and also do a switch inside the selection of sysext (to
only show the ones never offered before).

=> I dropped the idea for 4.5, because it would add too much complexity
at this late time, and in 4.5 its not needed yet (because in 4.4 you
could not "markAsDone" anyway). So starting in 4.6, if more stuff is
added here, we could differenciate further (and recognize if someone
"markedAsDone" in 4.5 by checking if wizardDone "==" 1).

- The "compatVersion" has some similar issues, because we need to show
it again if some stuff is added in a future release. In 4.6 we could try
simply to remove the case of "downgrading" functionality through it,
which is pretty uncommon for an "Upgrade Wizard". So if "Up to date!" =>
don't show the wizard, as its just annoying!


One thing I noticed while writing this: It's called "Update Wizard" in
the Install Tool, while I always talk about "Upgrade Wizard" (because to
me this is what is done when "Upgrading" from 4.4 to 4.5). Shouldn't
this be renamed??


Cheers,
Ernesto


More information about the TYPO3-team-core mailing list