It would be good to do videos on just some common things developers may need to learn for suite 8. Things like adding a button or customizing and existing suite 8 layout through code or how logic hooks work now, etc. Would be great to see how this works on the new 8 framework. Thanks!
made my day! (almost). however, it has some issues, which I am not understanding right now. why there is a type conflict thrown by Smyfony? php bin/console cache:clear PHP Fatal error: Uncaught TypeError: Symfony\Component\DependencyInjection\Loader\ProtectedPhpFileLoader::Symfony\Component\DependencyInjection\Loader\Configurator\{closure}(): Argument #1 ($container) must be of type Symfony\Component\DependencyInjection\ContainerBuilder, Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator given, thanks for the clear guide. how is the actual mapping done of the module identifier to the actual legacy module. concrete: how does "invoices" get resolved to "AOS_Invoices" module by module_routing.yaml. so far "invoices" identifies the unique REST route, but still I don't get, how symfony resolves the right module for the REST call further, I would like to see more about the classic suite7 hooks and how the got replaced at suite8 especially "after_ui_frame".
It would be good to do videos on just some common things developers may need to learn for suite 8. Things like adding a button or customizing and existing suite 8 layout through code or how logic hooks work now, etc. Would be great to see how this works on the new 8 framework. Thanks!
Noted, thank you!
made my day! (almost). however, it has some issues, which I am not understanding right now. why there is a type conflict thrown by Smyfony?
php bin/console cache:clear
PHP Fatal error: Uncaught TypeError: Symfony\Component\DependencyInjection\Loader\ProtectedPhpFileLoader::Symfony\Component\DependencyInjection\Loader\Configurator\{closure}(): Argument #1 ($container) must be of type Symfony\Component\DependencyInjection\ContainerBuilder, Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator given,
thanks for the clear guide. how is the actual mapping done of the module identifier to the actual legacy module. concrete: how does "invoices" get resolved to "AOS_Invoices" module by module_routing.yaml. so far "invoices" identifies the unique REST route, but still I don't get, how symfony resolves the right module for the REST call
further, I would like to see more about the classic suite7 hooks and how the got replaced at suite8 especially "after_ui_frame".
Thanks for the elaborate comment! We encourage you to post this on the community forum-if you haven't done so, already!
community.suitecrm.com/