[ishakutaParticipant]

Here’s some draft https://github.com/orocrm/platform/pull/337 for field level acl.

[ishakutaParticipant]

Hi,
yes, it’s not possible right now

I think the way it should work, in scope of user-related settings, is some-kind of parameter for oro:install command, like existing –user-email or –application-url, something like –user-lang or –user-locale.

[ishakutaParticipant]

Yes, I think you’re right.

It’s because of both problems:
– API key disclosure, cause of Crowdin API
– repackage for multiple projects (can be done in your code)

[ishakutaParticipant]

Hi, @jakabadambalazs

Generally it’s simple, but I think you’ll have to override:
– ServiceController in TranslationBundle, in order to pass your adapter to TranslationServiceProvider
OR
– change oro_translation.oro_translation_adapter service to your own and implement download action that will download translations from both Crowdin projects. You can extend/re-use CrowdinAdapter (AbstractAPIAdapter) for that.

Now, the main reason why you need custom adapter is that you have to download translation packs from two Crowdin projects (Oro’s and your own), but CrowdinAdapter supports downloads only from one.

Also you may have to override TranslationServiceProvider::download method, cause it assumes that download adapter saved only one zip archive, or your custom adapter should prepare single zip archive after download from two Crowdin projects.

Alternatively you may implement kind-of a proxy that will take list of projects, download them and re-package them for OroPlatform application, as we did for our out-of-the-box instance, you may see it’s default URL in Oro\Bundle\TranslationBundle\DependencyInjection\Configuration and can change it in app/config.yml

Let us know if you’ll have any further questions.

[ishakutaParticipant]

where is your php executable located? is it in /usr/bin folder?
can your user access /usr/bin and run executables there?

check your php environment variables.

[ishakutaParticipant]

@19prince I don’t think it’s possible now, but you can try to do it with virtual field.
Just a thought.

[ishakutaParticipant]

Hi, @mdegoo
1. There’s no such folder, cause UI bundle is just a foundation for UI, e.g. this reference is just a sample. Menu configuration from OroNavigationBundle override OroUIBundle navigation (when merging), and you can find application_menu.html.twig there too (in Nav bundle)
2. In order to override application menu template – you have to override OroNavigationBundle
3. Yes, cause actual template located there.

Alternatively you can try to override application menu template location in your MyNewUIBundle,
by setting different path to template in your navigation.yml:

oro_menu_config: templates: application_menu: template: 'MyNewUIBundle:Menu:application_menu.html.twig'

1 2 3 4 5 6

oro_menu_config:     templates:         application_menu:             template: 'MyNewUIBundle:Menu:application_menu.html.twig'

Let us know if you’ll have any further questions or difficulties.
Thank you.

[ishakutaParticipant]

Hi, @ivan_dyadin

You should override Contact bundle and define your own validation group, e.g.:
validation.yml

OroCRM\Bundle\ContactBundle\Entity\ContactAddress: properties: countrty: - NotBlank: { groups: [req_country] }

1 2 3 4 5 6

OroCRM\Bundle\ContactBundle\Entity\ContactAddress:     properties:         countrty:             - NotBlank: { groups: [req_country] }

And add form extension to set this validation group to address form.
Default validation constraints won’t be used after that.

Not sure it will work as is, but you got an idea.

Btw: next week we’ll host another webinar about customization techniques and will show how you can do similar overrides yourself.

[ishakutaParticipant]

Hi,
thank you for reporting an issue, it came with recent symfony component update and now, as you describe, * sign used for referencing (according to YAML standard).
We’ll fix this issue in next release and nightly builds.

[ishakutaParticipant]

Just to be sure, are you using twm_orocrm_project.form.handler.project handler in your Project controller?

I’ll try re-create your scenario and let you know.

[ishakutaParticipant]

Hello, SHAD0WF4X

Are you sure you’re correctly created ProjectHandler (should implement TagHandlerInterface)?
Can you probably post it’s content (as well as services.yml) somewhere on pastebin.com, etc?

[ishakutaParticipant]

Hello Jaimy

This is intended behaviour, cause each entity synced from Magento contains link to channel it’s came from, so user will be able to distinguish e.g. customers/orders that was imported from different channels.
Do you, probably, want to de-activate channel when you no longer need it, instead of delete.
Otherwise: if there was an option to soft-delete (actually hide it from UI), will it be useful for you?

Thank you for your notice.

[ishakutaParticipant]

Hello, Stephan

This is known issue caused by third party dependencies after release, please install latest version http://oroinc.com/orocrm/download or update your composer.json manually,
see example here
"knplabs/knp-menu": "2.0.x-dev#ff1a6e73e79c9f75c6a130d03b07f05c89fede63"


Let us know if you’ll have any problems.

[ishakutaParticipant]

Possible cases are:
1. wrong API credentials (username, api key, password or wsdl url), check that you’re able to get this url from your browser and from host where OroCRM installed.
2. SoapClient unable to parse wsdl
3. SoapClient unable to perform request or get malformed response
4. Some chances you have unique case where our system crashed

Anyway, here’s a patch http://pastebin.com/A3sH7HVb that add logging for this error,
if you apply this, you will be able to check for “MageCheck error …” message in app/logs/prod.log (or dev.log, depending on your environment).

Here’s how to apply it:git apply channel-conn-log.patch

And here’s how to check your potentially big log:cat app/logs/prod.dev | grep MageCheck

Please provide error log or error message when you do this. Thank you.

[ishakutaParticipant]

Hello,

You should use v2 Magento API, so first URL seems to be correct.
Did you add this api_user in “System -> Web services -> SOAP/XML-RPC – Users” Magento admin panel and assign this user all necessary roles?

Let us know if this is the case and you still in trouble.

[Author]

Replies