Bug #15689
EM seems to let me install conflicting extension (reverse dependency checking needed)
| Status: | Closed | Start date: | 2006-02-21 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | Extension Manager | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 4.0 | Is Regression: | No | |
| PHP Version: | Sprint Focus: | |||
| Complexity: |
Description
I have installed tt_products 2.4.6. This one excludes zk_products as conflicts.
However it seems that the EM wants to let me install zk_products after tt_products.
I did not dare to press UPDATE now in order to do not get the conflict.
-----------------------
Extension: Shop system (extended by ZK) (zk_products) Go back
Installing Shop system (extended by ZK): DATABASE NEEDS TO BE UPDATED
Before the extension can be installed the database needs to be updated with new tables or fields. Please select which operations to perform:
Changing fields
ALTER TABLE tt_products CHANGE inStock inStock int(11) default '0';
Current value: int(11) default '1'
ALTER TABLE tt_products CHANGE gradings gradings varchar(40) default '';
Current value: varchar(255) default ''
ALTER TABLE tt_products CHANGE subtitle subtitle tinytext;
Current value: mediumtext
ALTER TABLE sys_products_orders_mm_tt_products DROP KEY tt_products_uid;
ALTER TABLE sys_products_orders_mm_tt_products ADD KEY tt_products_uid (tt_products_uid);
ALTER TABLE tt_content CHANGE tt_products_code tt_products_code varchar(30) default 'LIST';
Current value: varchar(30) default 'HELP'
Clear cache
This extension requests the cache to be cleared when it is installed/removed.
Clear all cache:
(issue imported from #M2652)
Related issues
History
#1 Updated by Karsten Dambekalns over 9 years ago
Yes, because this is a reverse dependency. tt_products conflicts with tt_products, but you are installing zk_products which isn't defining a conflict with tt_products...
A check should be added that works reversely...
#2 Updated by Alexander Opitz over 1 year ago
- Status changed from New to Needs Feedback
- Target version deleted (
0) - PHP Version deleted (
4) - Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
#3 Updated by Franz Holzinger over 1 year ago
This bug is still present in the latest TYPO3 6.2 Core from this week.
How to test:
Install the extension agency which conflicts sr_feuser_register.
Then copy sr_feuser_register to the typo3conf/ext folder and change the dependency of the file ext_emconf.php of sr_feuser_register: 'typo3' => '4.4.0-6.2.99'. Then install sr_feuser_register. It can be installed despite of the restriction.
There must be an error message and it must be avoided to install the conflicting extension.
#4 Updated by Alexander Opitz over 1 year ago
- Status changed from Needs Feedback to New
- Priority changed from Should have to Must have
#5 Updated by Mathias Schreiber 7 months ago
- Status changed from New to Closed
The current implementation is a mess that can't be handled.
This issue will be tackled by using composer which offers a clean way of resolving conflicts