Drupal path alias change not firing update on node save

Created on 31 October 2022, about 2 years ago

Updated 4 May 2023, over 1 year ago

Problem/Motivation

While working on a headless Drupal / Gatsby setup (new), I noticed that if the node title changes or if the path alias is manually changed, Gatsby Cloud is not triggered to update the FE and show the new path for the page for the Gatsby site. Another save or two does seem to trigger Gatsby Cloud to update the page path on the FE.

Drupal 9 with Gatsby Integration 2.x RC4
Gatsby 4.24.4

Steps to reproduce

Update the Drupal node to a different path alias
Save the node
Gatsby Cloud doesn't build with the new change
Subsequent node updates do eventually update Gatsby correctly

I wonder if anyone else has seen this type of behavior. What additional info would be helpful?

Some next steps, which I think will help:

Update current site setup details in this issue, including settings for the Gatsby Integration module
Post additional details from the fastbuilds logs to id when webhook are fired

🐛 Bug report

Status

Closed: outdated

Version

2.0

Component

Code

Created by

🇺🇸United States shrop

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment over 1 year ago →
🇺🇸United States apmsooner
The patch here: https://www.drupal.org/project/gatsby/issues/3347297 🐛 draft content leaking into "live" server Fixed and latest gatsby-source-drupal plugin will resolve the issue when the build_published setting is disabled. Will open another feature tickets that expands settings to bypass only publishing nodes and include other entities like redirects and path aliases along with it. The build_published setting as it stands is limiting and too restrictive for common updates that "should" occur along with node updates.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024