-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Closed
Closed
Copy link
Labels
Issue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P3May be fixed according to the position in the backlog.May be fixed according to the position in the backlog.Progress: doneReproduced on 2.1.xThe issue has been reproduced on latest 2.1 releaseThe issue has been reproduced on latest 2.1 releaseReproduced on 2.2.xThe issue has been reproduced on latest 2.2 releaseThe issue has been reproduced on latest 2.2 releaseReproduced on 2.3.xThe issue has been reproduced on latest 2.3 releaseThe issue has been reproduced on latest 2.3 releaseSeverity: S3Affects non-critical data or functionality and does not force users to employ a workaround.Affects non-critical data or functionality and does not force users to employ a workaround.help wantedstale issue
Description
Preconditions
- Magento 2.1.x
- PHP 7.0.14
- MySQL 5.7.16
Steps to reproduce
- Have a custom module with the following structure.
- composer.json
- registration.php
- src
- in registration.php have the dir as:
__DIR__.'/src'
- in composer.json have psr-4 as:
"Vendor\\Module\\": "src/"
- have some installSchema, installData file in src\Setup
- have a Uninstall file in src\Setup
- run:
bin/magento module:uninstall Vendor_Module --remove-data
Expected result
- It should properly find the composer.json file and uninstall the module
Actual result
- Exits with error: Vendor_Module is not an installed composer package
But if you add a composer.json file to src/ then it will uninstall the module, but this is not where the composer.json file should be for 3rd modules.
lamasfoker
Metadata
Metadata
Assignees
Labels
Issue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P3May be fixed according to the position in the backlog.May be fixed according to the position in the backlog.Progress: doneReproduced on 2.1.xThe issue has been reproduced on latest 2.1 releaseThe issue has been reproduced on latest 2.1 releaseReproduced on 2.2.xThe issue has been reproduced on latest 2.2 releaseThe issue has been reproduced on latest 2.2 releaseReproduced on 2.3.xThe issue has been reproduced on latest 2.3 releaseThe issue has been reproduced on latest 2.3 releaseSeverity: S3Affects non-critical data or functionality and does not force users to employ a workaround.Affects non-critical data or functionality and does not force users to employ a workaround.help wantedstale issue
Type
Projects
Status
Done