Jump to content

Reason for services.yml override is not reflecting correctly for FO controllers?


Dinu SK

Recommended Posts

I have created one base module for a payment module and a dependency module for overriding the base module using services.yml.

Below is the services.yml created in the base module
 

services:
  _defaults:
    public: true
  ignite.new.checker:
    class: Ignite\Src\ignite\helper\Checker
    shared: true
  ignite.frontpaymentoptions.paymentoptionswrapper:
    class: Ignite\Classes\ignite\FrontPaymentOptions\PaymentOptionsWapper
    shared: false
    

And below is the services.yml used in the dependency module 
 

services:
  _defaults:
    public: true
  ignite.new.checker:
    class: Override\Src\helper\Checker
    shared: true
  ignite.frontpaymentoptions.paymentoptionswrapper:
    class: Override\Src\FrontPaymentOptions\PaymentOptionsWapper
    shared: false

Currently, I am facing an issue with FO controllers that is when I try to get a service "ignite.frontpaymentoptions.paymentoptionswrapper" inside hook hookPaymentOptions, it always gets the class from the base module, not from the dependency module. But when I debug the service container it shows the override class "Override\Src\FrontPaymentOptions\PaymentOptionsWapper". I cleared the cache from the admin advanced parameters option.

Does anyone know why the FO code does not reflect the override class? 

Edited by Dinu SK
spelling mistake (see edit history)
Link to comment
Share on other sites

  • Dinu SK changed the title to Reason for services.yml override is not reflecting correctly for FO controllers?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...