Bug #44755
6.0.0 behaves like 3.8.0 initially
| Status: | Resolved | Start date: | 2013-01-23 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | 6.2.0 | |||
| TYPO3 Version: | 6.0 | Is Regression: | ||
| PHP Version: | 5.3 | Sprint Focus: | ||
| Complexity: | easy |
Description
Fresh new 6.0.0 install. Upgrade wizard says:
Version Compatibility
Your current TYPO3 installation is configured to behave like version 3.8 of TYPO3. If you just upgraded from this version, you most likely want to use new features as well.
Is it supposed to be like that? I didn't expect it and so had quite some trouble with the set up.
Related issues
History
#1 Updated by Oliver Hader over 2 years ago
- Status changed from New to Accepted
- Complexity set to easy
Yes, since you could be upgrading an old version, the Core just does not know what you're currently running.
One could have a TYPO3 4.5 data-set (database, configuration, etc.) but using the TYPO3 6.0 source code.
However, on new installations this should be determined automatically and furthermore the lowest possible version should be 4.5.0
#2 Updated by Christian Kuhn about 2 years ago
- Status changed from Accepted to Resolved
- Target version set to 6.2.0
- PHP Version set to 5.3
This is solved in current 6.2 install tool, compat_version is set to 6.2 during installation.