[1.5.4] New hooks in FrontController work only if placed in initHeader()?

[stratboy]

Hi. I created new hooks and assigned to smarty in an overridden frontcontroller.

I wanted to place them in init() or displayHeader(), but it simply doesn't work. I have to place theme in initHeader() instead.

 

Class FrontController extends FrontControllerCore{

   public function initHeader(){

       $this->context->smarty->assign('HOOK_HEADER_TOOLS', Hook::exec('displayHeaderTools'));
       $this->context->smarty->assign('HOOK_HEADER_RIGHT_BOX', Hook::exec('displayHeaderRightBox'));
       $this->context->smarty->assign('HOOK_HEADER_MAINMENU_BOX', Hook::exec('displayHeaderMainMenuBox'));

       parent::initHeader();
   }

}//end FrontController

 

Why aren't they recognized if I put them in init() or displayHeader()?

 

(I would receive a smarty Notice like Undefined index [..] Trying to get property of non-object [...] etc--)

[NemoPS]

I suggest you use the new way to create hooks instead. Here:

 

http://blog.arvixe.com/adding-hooks-to-prestashop-1-5-the-new-way/

[Valérie Assetskaya]

Hi,

 

If you check initial FrontController::displayHeader code, you will see that this method is depricated and the most likely is not used on the necessary page.

 

Best regards.

[stratboy]

Hi,

 

If you check initial FrontController::displayHeader code, you will see that this method is depricated and the most likely is not used on the necessary page.

 

Best regards.

 

Hi! You're right!

 

And what about using the init() method? Why doesn't it work?

[Valérie Assetskaya]

Hi,

 

It is hard to say. It is necessary to check the whole code and see the definite case. init() is not the method which should be reloaded. initContent() is better.

 

Best regards.

[stratboy]

Hi,

 

It is hard to say. It is necessary to check the whole code and see the definite case. init() is not the method which should be reloaded. initContent() is better.

 

Best regards.

 

initContent().. Yesss, interesting, thank you!!!