Fix: Adapt voucher category attribute creation for OroCommerce 6.1.x version#49
Fix: Adapt voucher category attribute creation for OroCommerce 6.1.x version#49vanlayo wants to merge 2 commits intomollie:masterfrom
Conversation
Merge pull request mollie#47 from vanlayo/master
Refactored the 'mollie_voucher_category' product attribute creation to ensure compatibility with OroCommerce 6.1. The previous data fixture caused a fatal error on a fresh `oro:install` due to changes in how enum attributes are handled in OroCommerce 6.1. This commit now follows the standard OroCommerce convention by splitting the logic into two separate fixtures: - `LoadMollieVoucherCategoryData`: Uses the `AbstractEnumFixture`, which is the correct approach for creating enum options. - `LoadMollieProductAttributeFamilyData`: Assigns the created attribute to the default product family. This approach aligns with the updated data fixture loading mechanism in OroCommerce 6.1 and resolves the installation failures.
|
Hi @vanlayo Thanks for reaching out to us. Please note that we will review the changes carefully and update you regarding our decision accordingly. Best regards |
|
Hi @vanlayo Just so you know, we are still reviewing the changes and will update you as soon as possible. Best regards |
|
Hi, @vanlayo Please note that the review of the changes is in progress, and we will update you accordingly. Best regards |
|
@logeecom is this still in progress? Orocommerce 6.1 has been released in March 2025... |
|
Hello @powli, Yes, we are actively working on this. By the end of this month, a new plugin version compatible with Orocommerce 6.1 will be released. Best regards |
|
Hi @logeecom, This is becoming a roadblock to progress in customer projects. Please provide substantial feedback. |
Refactored the 'mollie_voucher_category' product attribute creation to ensure compatibility with OroCommerce 6.1.
The previous data fixture caused a fatal error on a fresh
oro:installdue to changes in how enum attributes are handled in OroCommerce 6.1.This commit now follows the standard OroCommerce convention by splitting the logic into two separate fixtures:
LoadMollieVoucherCategoryData: Uses theAbstractEnumFixture, which is the correct approach for creating enum options.LoadMollieProductAttributeFamilyData: Assigns the created attribute to the default product family.This approach aligns with the updated data fixture loading mechanism in OroCommerce 6.1 and resolves the installation failures.
ℹ️ This will be merged into main, but should probably be tagged specifically for OroCommerce 6.1.
### Screenshots
Product Attributes after install:
Product Families after init: