Forums

Covering OroCommerce, OroCRM, OroPlatform topics, including community updates and company announcements.

Starting from March 1, 2020 the forum has been switched to the read-only mode. Please head to StackOverflow for support.

Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Author
    Replies
  • in reply to: How to override parts of oro #36974

    nevoeiro
    Participant

    Considering your documentation on https://oroinc.com/orocrm/forums/topic/how-to-override-parts-of-oro/#post-63331

    Is it possible to have 2 bundles extending the same js component? Imagine you have bundle A that adds component A and bundle B that adds component B. And you want, on both bundles, initialize the component on line-item-view.js (order contexts, like you do for product-unit-component)

    If we extend LineItemView adding on initialize method the init of new components, in both bundles, then just the one with high priority will be executed, right?

    what would be the best (and clean) approach for these case?
    Thanks

    in reply to: Missing option "type" for "color" field #32748

    nevoeiro
    Participant

    I couldn’t get it working on my side without your workaround. Attribute was added to default family on my migrations too.
    If I back to this topic again I’ll post my finds.
    Thanks.

    in reply to: Missing option "type" for "color" field #32746

    nevoeiro
    Participant

    Hi iantypenko,

    I’m using platform 2.6 and commerce 1.6

    What you mean with “New field should be added automatically to the search index”?
    Don’t we need to add “searchable”=>true?
    If I don’t add that, then the field isn’t searchable.

    Regarding your suggestion if I clear cache and run the migration:load I don’t get the error. But I don’t want to run that, I mean I don’t want to have a error.

    For the workaround I got this:

    I changed ‘type:string’ by ‘type:text’ and it worked.

    Is this the best approach to add a new searchable attribute? What is the best practice to add a searchable attribute programmatically without having that issue on migration load?
    thanks


    nevoeiro
    Participant

    Hi msulima

    Thanks for reply, we found the issue. It was a side effect from other new unit test added recently that was broken the cache generation.
    It was not clear because when we run the test isolated we didn’t got the issue, but when we tried to run all tests the issue came up in our pipeline.
    So it’s fine.
    thanks


    nevoeiro
    Participant

    Hi again,

    We update to 1.6.0 version and it’s strange now we are getting a similar issue.
    When it tries to load the data for functional test:

    We get the error below on “$manager->persist($childNode);” execution:

    We checked on htdocs/app/cache/test/oro_entities/Extend/Entity/EX_OroWebCatalogBundle_ContentNode.php the field $metaTitles is there.

    in reply to: Translatable fields? #35607

    nevoeiro
    Participant

    Is this still not possible, have a support of multilingual field types for custom fields? We need that too.


    nevoeiro
    Participant

    Thanks msulima!
    Yes, we have one for test and other for dev/prod.

    I run ‘console oro:platform:update –env=test’ and I got the extended class updated with the custom ‘image’ field. Now my tests are running successfully! Thanks.


    nevoeiro
    Participant

    @msulima
    1. Field was created through a migration using AttachmentExtensionAwareInterface, like

    2. What do you mean with “installed for test environment” ? Like running ‘console oro:platform:update –env=test’? I didn’t run that.

    The installation has cache for test, I checked the app/cache/test/ folder, it has content and I can see the file ‘htdocs/app/cache/test/oro_entities/Extend/Entity/EX_OroWebCatalogBundle_ContentNode.php’. But image field isn’t there.

    On htdocs/app/cache/dev/oro_entities/Extend/Entity/EX_OroWebCatalogBundle_ContentNode.php I can see the image field there.

Viewing 8 replies - 1 through 8 (of 8 total)
Back to top

You will be redirected to [title]. Would you like to continue?

Yes No

You will be redirected to [title]. Would you like to continue?

Yes No