Conditional Hooks

[Jonathan Lahijani]

In 2015, Ryan introduced conditional hooks:
https://processwire.com/blog/posts/new-ajax-driven-inputs-conditional-hooks-template-family-settings-and-more/

I have the following hook which works properly:

$wire->addHookAfter('Pages::added', function($event) {
  $page = $event->arguments[0];
  if($page->template=='mytemplate') {
    // ...
  }
});

Now if I want to take advantage of conditional hooks, I should be able to do this:

$wire->addHookAfter('Pages(template=mytemplate)::added', function($event) {
  // ...
});

however the hook doesn't get hooked.  Any ideas?

[Jonathan Lahijani]

Note: whether I use Page(template=mytemplate)::added or Pages(template=mytemplate)::added does not make a difference.

[LostKobrakai]

So the conditional hooks (probably) work on the $event->object of the HookEvent passed to the hook. That's why ryan's examples only use Page(…)::…. Page does not have a function added (neither hookable nor unhookable), while Pages cannot be evaluated against a selector. 

[bernhard]

I've also been struggling with this:

Thats because the $page you want to check is the first argument of the HookEvent, so you need to apply it there, not at the first part, which is the class (or object). You can also do this:

[LAPS]

@bernhard So, the advice is not to use conditional hooks if not as made in @ryan's example(s)?

[bernhard]

No, conditional hooks are great. I just tried to show that this:

Pages(template=foo)::saved

is wrong and this is the correct version:

Pages::saved(template=foo)

See https://processwire.com/talk/topic/18037-2-date-fields-how-to-ensure-the-second-date-is-higher/#comment-158164 and