OroCRM

[ignatParticipant]

Hey @d8bhatta,

Probably you’ve entered

PHP

php app/console lexik:maintenance:unlock -env prod

1	php app/console lexik:maintenance:unlock -env prod

instead enter 2 minus sybmbols before “env” to fix too many parameters error:

PHP

php app/console lexik:maintenance:unlock --env prod

1	php app/console lexik:maintenance:unlock --env prod

[ignatParticipant]

You might be using xdebug. I’d recommend to disable it and enable only when you need to debug something. To fix this specific issue you can specify this option in your xdebug.ini or php.ini files and restart web server:

PHP

xdebug.max_nesting_level=1024

1	xdebug.max_nesting_level=1024

http://xdebug.org/docs/all_settings#max_nesting_level

[ignatParticipant]

Try to pass –timeout option to install command:

PHP

sudo -unginx php app/console oro:install --env prod -vvv --timeout 3600

1	sudo -unginx php app/console oro:install --env prod -vvv --timeout 3600

Don’t forget to clear DB before install.

[ignatParticipant]

Hi @rogerio,

The issue might be we permissions of your web server user and permissions of files in app/cache/prod. Do you have access to CLI for this instance? If yes, please run install in CLI to debug this problem:

1) Clear cache:

PHP

rm -R app/cache/*

1	rm -R app/cache/*

2) Run install command

PHP

php app/console oro:install --env prod -vvv

1	php app/console oro:install --env prod -vvv

Make sure you run this commands as your web server user, for example:

PHP

sudo -unginx php app/console oro:install --env prod -vvv

1	sudo -unginx php app/console oro:install --env prod -vvv

[ignatParticipant]

Hi @calidays,

The issue might be in your app/config/parameters.yml file. I guess some attribute value was specified incorrectly after composer install. Check all values of parameters. If you won’t be able to solve this issue please share content of this file.

Thanks,
Ignat

[ignatParticipant]

These entities can be extended now. Changes available in master and in 1.9.0-RC1: https://github.com/orocrm/platform/commit/e0887f16bd0483183ec6d08b5ab096388b7b2f3c

[ignatParticipant]

Hi Tom,

I’ve created a bug report for this issue and I’ll follow up when it will be fixed.

Regards “oro_html_filter” I think you won’t be able to use this Twig filter in template because only allowed Twig filters/functions/tags can be used. They are:
tags: ‘app’, ‘for’, ‘if’, ‘spaceless’
filters: ‘default’, ‘date’, ‘escape’, ‘format’, ‘length’, ‘lower’, ‘nl2br’, ‘number_format’, ‘title’, ‘trim’, ‘upper’, ‘oro_format’, ‘oro_format_date’, ‘oro_format_time’, ‘oro_format_datetime’, ‘oro_format_name’, ‘oro_tag_filter’
functions: ‘date’, ‘calendar_date_range’, ‘oro_config_value’, ‘url’, ‘path’

Thank you,
Ignat

[ignatParticipant]

To avoid this error you need to adjust app/config/parameters.yml. When Oro installed parameter “installed” is set too current date. For example https://gist.github.com/ignat-s/b4edfaec1b34a2eb51d8#file-parameters-yml-L23. Consider to put value in this file. Value could be either date time or simply boolean true, like this:

PHP

installed: true

1	installed: true

[ignatParticipant]

It seems like you are using application cache that is not actual for your current code base. Try to remove app/cache/prod and run command app/console cache:clear –env=prod

[ignatParticipant]

And when do you receive this error?

[ignatParticipant]

Did you change anything in config.yml to enable SSO in your application?

[ignatParticipant]

Maybe it’s just the case of how you are using composer in your environment, try this one without grep:

PHP

php composer.phar show -i

1	php composer.phar show -i

[ignatParticipant]

What is the version of Oro you are using? Please run these commands:

PHP

php composer.phar show -i | grep oro php composer.phar show -i | grep hwi/oauth-bundle

1 2	php composer.phar show -i | grep oro php composer.phar show -i | grep hwi/oauth-bundle

[ignatParticipant]

Hi Madhur,

To collect statistics Oro send request to external resource. You can debug here: https://github.com/laboro/platform/blob/master/src/Oro/Bundle/TranslationBundle/Provider/OroTranslationAdapter.php#L60.

If your instance’s environment blocks external requests this could be the issue. For example it is possible when you are running Oro instance under some VPN.

To check if this is the case run this curl request in same the server where your instance is located:

curl http://translations.orocrm.com/api/stats?packages=composer/composer,Oro,Symfony,Doctrine,Sensio,JMS,Knp,FOS,Nelmio,BeSimple,Stof,Escape,Liip,Genemu,A2lix,Lexik,OroPro,HWI,Akeneo,JDare,OroCRM,OroCRMPro,Sylius

Consider to run it using same user which is running Oro (for example www-data oro nginx), like this:

sudo -unginx curl http://translations.orocrm.com/api/stats?packages=composer/composer,Oro,Symfony,Doctrine,Sensio,JMS,Knp,FOS,Nelmio,BeSimple,Stof,Escape,Liip,Genemu,A2lix,Lexik,OroPro,HWI,Akeneo,JDare,OroCRM,OroCRMPro,Sylius

Thanks,
Ignat

[ignatParticipant]

lapino, I was able to reproduce this issue when I tested it on workflow with transition which has option “acl_resource”. Is that your case too? If it is you can consider next options to avoid using ACL in transition:

1) If this transition cannot be called from UI (as far as it is used only as start transition) it make sense to remove “acl_resource”.

2) Create another transition, same as original but use option is_hidden. Then run this transition in your process. In this way your users will be able to use ACL-aware transition in UI and integration sync will use non-ACL transition.

Thanks,
Ignat

[Author]

Replies