[TYPO3-core] RFC: Fix bug #3943 (was: Re: compatVersion in 4.0.1)

[Christian Jul Jensen]

One comment, while you are at it:

If you decide to leave a site in 3.8 compat mode for css reasons, you will 
stil have the big yellow "something wnet awfull wrong"-box when you login. 
Kind of confusing if you don't know what it is about.

-julle

On Friday 28 July 2006 01:44, Michael Stucki wrote:
> Finally, I have solved this problem:
>
> 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
>
> Solution:
> Compare against TYPO3_branch instead of TYPO3_version.
>
> 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.
>
> - michael
>
> Am Donnerstag, 27. Juli 2006 17:08 schrieb Dmitry Dulepov:
> > Hi!
> >
> > Michael Stucki wrote:
> > > please have a look at the attached screenshots. This is an installation
> > > with TYPO3 4.0.1 which was upgraded from 4.0. compatVersion is already
> > > set to "4.0", but obviously the version needs to match exactly.
> > > Is this intention or a mistake?
> > >
> > > In my opinion, the compatVersion should reflect a branch, not a
> > > version.
> >
> > I think compatVersion should change only and only if really there are
> > compatibility changes. We had them between 3.8.x and 4.0 but there are
> > no any between 4.0 and 4.0.1. Going to upgrade wizard presents empty
> > list of updates, which puzzles a bit and makes me thing that something
> > went wrong.
> >
> > Dmitry.

-- 
Christian Jul Jensen

TYPO3 association
http://association.typo3.org

* this mail is signed with GnuPG. If all you 
* see is a file of unknown type, your mail client 
* does not support it, just ignore it, it is not
* a virus, or have a look at http://openpgp.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20060728/ec7f5fd0/attachment.pgp