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

502 error when combined with content-heavy ACF pages #239

Open
tcmulder opened this issue Jan 13, 2023 · 0 comments
Open

502 error when combined with content-heavy ACF pages #239

tcmulder opened this issue Jan 13, 2023 · 0 comments

Comments

@tcmulder
Copy link

We're getting a 502 timeout error when saving posts that have a lot of ACF fields on them, causing the content to be partially unsaved (i.e. some fields that had content further down the page are empty once we refresh after the 502 error). If we disable WPGatsby, these same posts save quickly, even if we double the number of ACF fields on them.

For now, we're disabling WPGatsby, making a bunch of changes, reactivating the plugin, then saving a post that happens to have only a few ACF fields; when we do this, everything works great and our Gatsby site updates with all the content correctly.

So, it seems WPGatsby is maybe doing something expensive on post save when many ACF fields are present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant