Trigger_Refetch_All not working.

[psharma-ii]

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

I had created following issue on wp-gatsby, but after talking with @TylerBarnes, the issue should be opened here.

We had discussed about a syncing issue with a plugin and you had asked me to use trigger_refetch_all which is also used by permalink_structure changes. The function didn't work (implementation example below). I also tested permalink structure change, which also didn't seemed to do any rebuilds. When i started digging around the gatsby-source-wordpress plugin, I noticed 2 things and I am not sure if they are the cause or I am completely looking into the wrong place. #1) There is no conditional for REFETCH_ALL here which probably is okay. #2) Also, noticed the conditional here was evaluating to false for REFETCH_ALL and never hitting this.

@TylerBarnes had suggested a fix, so I will be checking that out and see if I can do a PR

Reproduction Link

https://gatsby.dev/reproduction

Steps to Reproduce

1. Setup wordpresss locally
2. Add WP GRAPHQL, WP Gatsby Plugin
3. Install GatsbyJS and gatsby-source-wordpress plugin
4. Add some post in WP
5. Run gatsby build && gatsby serve
6. Do a permalink structure change.
7. 4. Run gatsby build && gatsby serve
8. The change to permalink structure is not reflected.

...

Expected Result

Permalink structure change should reflect on Gatsby

Actual Result

Permalink structure change should reflect on Gatsby

Environment

System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.18.0 - ~/.asdf/installs/nodejs/12.18.0/bin/node
    Yarn: 1.22.11 - /usr/local/bin/yarn
    npm: 7.16.0 - ~/.asdf/installs/nodejs/12.18.0/.npm/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 93.0.4577.82
    Firefox: 92.0
    Safari: 14.1.2
  npmPackages:
    gatsby: ^3.10.2 => 3.10.2
    gatsby-plugin-gatsby-cloud: ^2.10.1 => 2.10.1
    gatsby-plugin-image: ^1.10.1 => 1.10.1
    gatsby-plugin-manifest: ^3.10.0 => 3.10.0
    gatsby-plugin-meta-redirect: ^1.1.1 => 1.1.1
    gatsby-plugin-offline: ^4.10.0 => 4.10.0
    gatsby-plugin-postcss: ^4.10.0 => 4.10.0
    gatsby-plugin-react-helmet: ^4.10.0 => 4.10.0
    gatsby-plugin-react-helmet-canonical-urls: ^1.4.0 => 1.4.0
    gatsby-plugin-robots-txt: ^1.6.8 => 1.6.8
    gatsby-plugin-sass: ^4.10.0 => 4.10.0
    gatsby-plugin-sharp: ^3.10.2 => 3.10.2
    gatsby-plugin-sitemap: ^4.6.0 => 4.6.0
    gatsby-plugin-styled-components: ^4.10.0 => 4.10.0
    gatsby-source-filesystem: ^3.10.0 => 3.10.0
    gatsby-source-wordpress: ^5.10.0 => 5.14.0-next.4
    gatsby-transformer-sharp: ^3.10.0 => 3.10.0
  npmGlobalPackages:
    gatsby-cli: 3.7.1

Config Flags

No response

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[psharma-ii]

The PR is still open for this -#33264