Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating to 1.0.6 breaks incremental builds #16

Closed
emson-digital opened this issue Oct 19, 2021 · 8 comments
Closed

Updating to 1.0.6 breaks incremental builds #16

emson-digital opened this issue Oct 19, 2021 · 8 comments
Labels
bug Something isn't working

Comments

@emson-digital
Copy link

Description

As stated in the title. Gatsby is no longer seeing updated content in the new update. Reverting to 1.0.5 resolves this.

Steps to reproduce

  1. Make edit in CMS
  2. Gatsby doesn't see any changes

1.0.6
image

1.0.5
image

Additional info

  • Craft version: 3.7.16
  • PHP version: 8.1
  • Database driver & version:
  • Plugins & versions:
@andris-sevcenko
Copy link
Contributor

Is this on a multisite build?

@emson-digital
Copy link
Author

Yes, though only one site has entries assigned to it currently.

@andris-sevcenko
Copy link
Contributor

Is that site the primary site? Also, have you set the enabledSites setting to anything for the gatsby-source-craft plugin?

@emson-digital
Copy link
Author

Yes, it is the primary site, have not set enabled sites in the gatsby source plugin.

@emson-digital
Copy link
Author

I notice today that there is a new gatsby-source-craft plugin that requires 1.0.6 that plugin was not updated after updating the CMS helper. I don't know if there was anything explicitly stated on 1.0.6 that made us aware of the Gatsby plugin update. I can assume that now that I see that, I will need to update the plugin in Gatsby for these to work together as expected? I will update both of these today sometime and get back to you.

@andris-sevcenko
Copy link
Contributor

Sorry, I didn't get around to it today. Theoretically, if you have not set the enabled sites, everything on the primary site should still have been sourced. I'll figure this out tomorrow and will also get back to you!

@andris-sevcenko
Copy link
Contributor

Found the bug, working on it!

@andris-sevcenko
Copy link
Contributor

Alright, just cut the 1.0.7 release that should fix this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant