Install
Requirements
Section titled “Requirements”| Supported | |
|---|---|
| Magento Open Source | 2.4.9 (magento/framework >=103.0.9 <103.0.10) |
| Mage-OS | 3.x, which tracks Magento 2.4.9 |
| PHP | 8.3 – 8.5 |
The magento/framework constraint gates the install: Composer will not place msi-core on a Magento
version it was not built for.
The upgrade installs database triggers to detect writes to the legacy
tables. They need the TRIGGER privilege. Without it the
upgrade only warns and carries on, and detection stays off.
Install
Section titled “Install”Add the repository to the composer.json of your project:
{ "repositories": [ { "type": "vcs", "url": "https://github.com/jeanmarcos-dev/msi-core" } ]}Then:
-
Require the package:
Terminal window composer require "jeanmarcos/msi-core:^1.0" -
Put the store in maintenance mode:
Terminal window bin/magento maintenance:enable -
Run the schema and data patches. On a large catalog the configuration migration is the slow step.
Terminal window bin/magento setup:upgrade -
Build the stock index. Stock 1 has no index rows until this runs, and the price and search indexes read salability from it:
Terminal window bin/magento indexer:reindex inventory catalog_product_price catalogsearch_fulltext -
Flush the cache and leave maintenance mode:
Terminal window bin/magento cache:flushbin/magento maintenance:disable
Then make sure the salability consumer runs. It is a requirement, not a tuning recommendation.
Coming from jeanmarcos/inventory
Section titled “Coming from jeanmarcos/inventory”The two packages provide the same modules and cannot coexist. Remove the drop-in package first:
composer remove jeanmarcos/inventorycomposer require "jeanmarcos/msi-core:^1.0"The upgrade steps above apply unchanged.
Choosing a version constraint
Section titled “Choosing a version constraint”^1.0 takes fixes and features and never a breaking change. Versioning
explains what each part of the version number promises.