magento / magento/community-features
Not needed hard dependency between bundle and catalog search modules
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 46
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
### Preconditions (*)
1. Magento version 2.2 or 2.3
### Steps to reproduce (*)
1. DIsable module `Magento_Bundle` by changing 1 to 0 in `config.php` prior to installing magento since it cannot be disabled via cli because of circular dependencies.
2. set catalog search full text index to manual `bin/magento indexer:set-mode manual catalogsearch_fulltext`
### Expected result (*)
1. fulltext search index is set to `manual`.
### Actual result (*)
1.console command reports an error
```
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'catalog_product_bundle_selection' doesn't exist, query was: CREATE TRIGGER trg_catalog_product_bundle_selection_after_insert AFTER INSERT ON catalog_product_bundle_selection FOR EACH ROW BEGIN INSERT IGNORE INTO catalogsearch_fulltext_cl (entity_id) VALUES (NEW.parent_product_id); END
```
### Additional info.
The problem is caused by this line
`` from the `mview.xml` file from the Catalog Search module.
Moving this line to the bundle module looks like it solves the problem.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Catalog Search module's mview.xml entry for catalog_product_bundle_selection and compare it with the Bundle module configuration. Reproduce the issue by disabling Magento_Bundle and running bin/magento indexer:set-mode manual catalogsearch_fulltext; done means the command succeeds without referencing the missing table.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100