Bug #30750
EM should not suggest upgrade when it leads to conflict
| Status: | Closed | Start date: | 2011-10-10 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assigned To: | - | % Done: | 0% | |
| Category: | Extension Manager | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 4.6 | Is Regression: | No | |
| PHP Version: | Sprint Focus: | |||
| Complexity: | medium | 
Description
EM always suggests to update to the latest version of an extension although it could lead to conflicts.
When you install ks_sitemgr, you have this in the dependencies:
'constraints' => array(
    'depends' => array(
        'be_acl' => '1.3.0-1.3.99',
    ),
    'conflicts' => array(
        'be_acl' => '1.4.0',
    ),
    'suggests' => array(),
),
	Once you install version 1.3.3 of be_acl, then install ks_sitemgr, it still suggest to upgrade to the latest version (currently 1.4.3) instead of sticking to the 1.3 branch.
Related issues
History
#1 Updated by Kay Strobach almost 4 years ago
please do not missunderstand me.
theoretically the following should be posible too:
'constraints' => array(
    'depends' => array(
        'be_acl' => '1.3.0-1.3.99, 1.4.1-1.4.8',
    ),
    'conflicts' => array(
        'be_acl' => '1.4.0',
    ),
    'suggests' => array(),
),
#2 Updated by Mathias Schreiber 8 months ago
- Status changed from New to Closed
- Is Regression set to No
will be tackled by composer in the future