Help Understanding the available events on the Node element

[stuartmitchelhill]

Question

Hi

I am working on a headless setup with a Next.js application as the frontend. As such I am trying to setup webhooks to revalidate my queries when data changes in the CMS.

I am using the webhooks plugin by pixel and tonic

The problem I am facing is with Node events. As per the documentation there is a afterSaveNode event however this isn't detectable by the webhooks plugin. afterSave allows the webhook to be saved but never triggers anything when nodes are edited

The afterSaveNav event on verbb\navigation\services\Navs works as expected, triggering a webhook, but verbb\navigation\elements\Node afterSaveNode or afterSave don't

Just wondering if there is something very easy that I am missing?

Thanks for any guidance you can provide

Additional context

No response

[engram-design]

I'm actually not sure how the Webhooks plugin resolves those event names. In our case afterSaveNode is technically just the name we've given it but isn't stated anywhere to anything. It's just a label in the docs.

We inherit this event, like all Craft Elements do. I'm wondering if the technical "name" for the event is afterSave, going off what the constant EVENT_AFTER_SAVE is (again, coming from Craft).

[stuartmitchelhill]

Thanks for getting back to me @engram-design

Apologies I am not super familiar with PHP so this may be a dumb question, do either of the afterSave or afterSaveNode events get exposed on the Node Element?

Digging into the package I can see in src>services>Navs.php I can see a couple snippets calling a EVENT_BEFORE_SAVE_NAV and EVENT_AFTER_SAVE_NAV in the saveNav and handleChangedNav methods and both these events work as expected with the webhooks plugin

However looking into the Node element in src>elements>Node.php theres nothing similar that I can see calling the EVENT_AFTER_SAVE

[engram-design]

So the EVENT_AFTER_SAVE event is triggered for any element across Craft. We list it in our docs for clarity, but it's not an event we raise ourselves. For context.

Node objects extend the Element class, so we inherit that event.

Happy to spin up the Webhook plugin if that'll help.

[stuartmitchelhill]

Thanks @engram-design really appreciate the guidance, I had assumed this was the case hooking into the native afterSave event but doesn't seem to want to play nicely

No stress on spinning up the Webhook plugin, i've asked a colleague smarter than I to have a dig in and see if they can find out what's going on.

Will let you know what we find

Thanks again

[engram-design]

Out of interest, I actually went into the Webhooks plugin. I noticed that the autocomplete didn't even show up verbb\navigation\elements\Node which was odd.

There's an issue I see on their handling of loading classes. It looks like if there's any error encountered in the class-loading handling they do, it bails on processing any further.

In my instance, I actually have an issue with the Freeform plugin:

"Class \"Solspace\\Freeform\\Library\\Integrations\\Types\\Elements\\ElementIntegration\" not found"

So it means that any classes with errors are going to mess with the autocomplete in the Webhooks plugin. I might look at adding a PR to their plugin for improvements on this. But manually adding afterSave and verbb\navigation\elements\Node should be fine.