[TYPO3-core] RFC: Fix bug #3943

Ernesto Baschny [cron IT] ernst at cron-it.de
Fri Jul 28 11:31:12 CEST 2006

Michael Stucki schrieb am 28.07.2006 01:44:

> This is a SVN patch request.
> I think this is a showstopper for 4.0.1 and should be fixed asap!
> Problem:
> compat_version is going to be changed to "4.0.1" and makes the user think 
> there are functional changes between 4.0 and 4.0.1. This is wrong of course.
> Bugtracker reference:
> http://bugs.typo3.org/view.php?id=3943

Read the code and tested it. +1 from me.

> Comments:
> While working on this, I've made a lot of changes to the Update Wizard because 
> I realized that it is very difficult to understand. Please check out the 
> functionality and let me know if there is something wrong with it.

It now looks a lot nicer and the string corrections also makes a lot of
things clearer to the user.

One bug missing, but not a "showstopper": If I don't acknoledge every
item in "Step 2", then press "Perform updates!" and on the resulting
page (where it says "you need to confirm all checkboxes") the "Go back"
link doesn't work, as this is a JavaScript "history.back" but the
previous page was a result of a POST submit. At least in IE, this
results in an error like "Warning: page not valid anymore". Best would
be to have a "BACK" button which resubmitts the already checked acknoledges.

A new feature would be nice, to get rid of the warning if one stays in
compat 3.8:  In "Step 1" there could be a "keep current compat version
as 3.8" button, which would save "3.8" in localconf.php so that the
warning should be gone. This is only needed now because "3.8" has never
set the "compatVersion" in locallang.php. In future all new TYPO3
installation should have this set.


More information about the TYPO3-team-core mailing list