You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: I am currently working on customizing Akeneo and would like to override an annotation-based entity in Akeneo. Specifically, I am trying to extend and modify the ConfigValue entity from Oro\Bundle\ConfigBundle. Objective:
To replace the default ConfigValue entity with a custom version that adds additional functionality, without modifying the vendor files.
Steps Taken:
Created a new entity class (ExtendedConfigValue) in my custom bundle that extends the original ConfigValue entity.
Configured resolve_target_entities in my Resources/config/config.yml file to point from Oro\Bundle\ConfigBundle\Entity\ConfigValue to My\Bundle\Entity\ExtendedConfigValue.
Cleared the Symfony cache and ran doctrine:schema:update to ensure schema changes apply.
Issue:
Despite these steps, the application continues to reference the original ConfigValue entity, and I encounter errors indicating that it does not recognize the new configuration.
Questions:
Is there any additional configuration required to override an annotation-based entity in Akeneo?
Are there specific Akeneo or Symfony caching steps I might have missed that could prevent the override from taking effect?
If anyone has successfully implemented an annotation-based entity override in Akeneo, could you share the steps or configurations that worked?
Thank you for any guidance you can provide!
The text was updated successfully, but these errors were encountered:
Akeneo Version: 3.x
Description: I am currently working on customizing Akeneo and would like to override an annotation-based entity in Akeneo. Specifically, I am trying to extend and modify the ConfigValue entity from Oro\Bundle\ConfigBundle.
Objective:
To replace the default ConfigValue entity with a custom version that adds additional functionality, without modifying the vendor files.
Steps Taken:
Created a new entity class (ExtendedConfigValue) in my custom bundle that extends the original ConfigValue entity.
Configured resolve_target_entities in my Resources/config/config.yml file to point from Oro\Bundle\ConfigBundle\Entity\ConfigValue to My\Bundle\Entity\ExtendedConfigValue.
Issue:
Despite these steps, the application continues to reference the original ConfigValue entity, and I encounter errors indicating that it does not recognize the new configuration.
Questions:
Thank you for any guidance you can provide!
The text was updated successfully, but these errors were encountered: