Ensure that the index_now hooks are run after pathauto

Hi codebymikey,

Thanks for the report. After reviewing the code more carefully, I want to clarify the actual behavior.

The module implements both hook_entity_insert and hook_path_alias_insert.
When a new node is created with a Pathauto pattern, the sequence is:

1. hook_entity_insert → Index Now fires before Pathauto (alphabetical order, same weight) → no alias yet → pings /node/123
2. hook_entity_insert → Pathauto fires → generates and saves the alias
3. hook_path_alias_insert → Index Now fires → pings /my-alias

So the aliased URL is correctly submitted via hook_path_alias_insert. The issue is not that the alias URL is never sent — it's that an extra, unnecessary ping is sent first with the system path.

There is already an in-memory deduplication system ($sentUrls) that prevents double pings when both hooks resolve to the same URL (which works correctly for updates). But on insert, the two pings resolve to different URLs, so deduplication does not help.

Regarding the proposed fix (setting module weight to 10): while functional, this approach is fragile — it relies on Pathauto keeping its default weight of 0, which is not guaranteed.

A more robust solution would be to defer all pings collected during hook_entity_insert to a KernelEvents::TERMINATE subscriber. By that point, all entity hooks have run, path aliases are available, and the correct canonical URL can be resolved. The existing $sentUrls deduplication would then also handle the subsequent hook_path_alias_insert ping naturally.

This would be a more significant refactor, but it would solve both the ordering issue and the double-ping issue in a way that does not depend on module weights.

While implementing this fix, I also noticed that hook_entity_delete pings never resolve to the aliased URL:
PathFieldItemList::delete() removes path aliases from the database inside doDelete(), before hook_entity_delete fires. This means Url::fromRoute() always resolves to the system path (/node/123) when an entity is deleted.

This would deserve its own dedicated issue, but since we are already introducing the KernelEvents::TERMINATE deferral system, it makes sense to handle it at the same time by capturing the canonical URL in hook_entity_predelete — before doDelete() runs — and deferring the ping alongside insert and update events.

I am extending the scope of this issue to include this fix.

Manually tested the fix with Pathauto enabled:

• Node creation: IndexNow receives the aliased URL, not /node/{id}
• Node update: the alias is correctly resolved at request termination; when the path alias changes, both the old and the new alias are pinged
• Node deletion: the aliased URL is captured in hook_entity_predelete before Pathauto removes it, and sent on KernelEvents::TERMINATE

All three cases work as expected. The unit tests also cover the deferral logic and the predelete URL capture.

For me it's RTBC for 4.0.x
Going to port it on 3.1.x

Seems to also be ok on 3.1.x

Note: Tests failures on 4.0.x MR are because I bumped the core minimal requirement to drupal 11.4 for 4.0.x while the CI still runs on 11.3

Drupal installed version: 11.3.12
....
Drupal\Core\Extension\MissingDependencyException: Unable to install modules: module 'index_now_node' is incompatible with this version of Drupal core.