See the Composer plugins issues when upgrading to Adobe Commerce 2.4.4 Knowledge Base article for instructions on how to modify the composer.json file to explicitly allow plugin loading. However, as of July 2022, Composer will not load plugins unless they have been explicitly allowed. Currently, plugins that are included in the composer.json file but not marked as trusted are automatically installed. Bug fixes for these projects are documented in the separate, project-specific release information that is available in the documentation for each project.Ĭomposer 2.2 introduced a security feature that requires merchants to identify trusted plugins in their composer.json file before the plugins will be executed. Other release informationĪlthough code for these features is bundled with quarterly releases of the Adobe Commerce core code, several of these projects (for example, B2B, Page Builder, and Progressive Web Applications (PWA) Studio) are also released independently. See the Apply a patch to continue offering DHL as shipping carrier Knowledge Base article for information about downloading and installing the patch. Merchants deploying these releases should apply AC-3022.patch at their earliest convenience to continue offering DHL as a shipping carrier. Adobe Commerce 2.4.4 and earlier versions that support the DHL integration support only version 6.0. Apply AC-3022.patch to continue offering DHL as a shipping carrierĭHL has introduced schema version 6.2 and will deprecate schema version 6.0 in the near future. Major backward-incompatible issues are described in BIC highlights. To review backward-incompatible changes, see BIC reference. Adobe Commerce and Magento Open Source releases may contain backward-incompatible changes (BICs).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |