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 7 replies - 1 through 7 (of 7 total)
  • Author
    Replies
  • in reply to: GUI entity and relation field #36874

    hugeval
    Participant

    Hello @brunpatoch, this issue has been resolved already

    in reply to: Log Call > Change Required fields #28433

    hugeval
    Participant

    Hi @james_allies. Please try to set 'required' => false for phoneNumber, direction attributes at CallType.php and remove direction, phoneNumber nodes at CallBundle/Resources/config/validation.yml

    in reply to: Ownership in OneToMany relations #33843

    hugeval
    Participant

    In this case you should protect entities manually, as mentioned at page https://github.com/laboro/platform/blob/master/src/Oro/Bundle/SecurityBundle/Resources/doc/access-levels.md#manual-protection-of-select-queries.

    For example, with QueryBuilder:

    Or with objects:

    in reply to: Ownership in OneToMany relations #33841

    hugeval
    Participant

    @dimonixx, there are several ways to load entities. Could you please show an example how do you load entities?

    in reply to: Ownership in OneToMany relations #33839

    hugeval
    Participant

    Hi @dimonixx, @andesk. Let me clarify oro security protection. Data grids and param converters are automatically protected with security protection. Please check

    https://github.com/laboro/platform/blob/master/src/Oro/Bundle/SecurityBundle/Resources/doc/access-levels.md#data-grids-protections
    https://github.com/laboro/platform/blob/master/src/Oro/Bundle/SecurityBundle/Resources/doc/access-levels.md#protection-with-param-converters.

    But if you load objects manually, you should protect them with oro_security.acl_helper or oro_security.security_facade. Please check

    https://github.com/laboro/platform/blob/master/src/Oro/Bundle/SecurityBundle/Resources/doc/access-levels.md#manual-protection-of-select-queries
    https://github.com/laboro/platform/blob/master/src/Oro/Bundle/SecurityBundle/Resources/doc/access-levels.md#manual-access-check-on-object

    To be able use protection you should make several steps:
    1 Add ownership annotation to entity, as you made:

    2 Make migration to create new acl_classes entry

    3 Add annotation to controller if you want to use param converters protection

    4 run app/console oro:platform:update console command

    in reply to: Install SynoOroCRMFullContactBundle #28361

    hugeval
    Participant

    Hi nurikabe, currently you can install synolia/syno-orocrm-fullcontact with commands:

    in reply to: Create OneToOne relationship with migrations #33706

    hugeval
    Participant

    Hi! To create OneToOne relationship using migration, you can use Doctrine native methods Doctrine\DBAL\Schema\Table::addColumn() and Doctrine\DBAL\Schema\Table::addForeignKeyConstraint()

Viewing 7 replies - 1 through 7 (of 7 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