-
Notifications
You must be signed in to change notification settings - Fork 122
Internal server error when using particular ACF meta fields #100
Comments
Side note. In this particular case, when using the Graphiql interface from the WP backend, the queries would successfully return data, even before we changed the field type. When queried from the frontend, it would fail. This, however, is not always the case. There have been times in the past few months when we have experienced the issue on both the backend and frontend, only on the backend, or only on the frontend. |
Same problem ...
When removing Let me know if some one has a solution. |
update: difference: |
This one is going to be tough to reproduce, as the issue is so intermittent and inconsistent in it's behavior. I did run into it again yesterday, where I was receiving an internal server error through the graphiql interface in WP admin, but requests made from my own client application would work as intended. The issue resolved on its own after about ten minutes of troubleshooting. |
@SunooBertsch could you maybe provide a PHP or JSON config for the particular ACF Field Group that's causing the issue so I can set it up the same as you locally? |
This is our entire acf PHP file. The issue doesn't occur with a specific field, but rather any acf field at any given moment. |
Just experienced the same issue as @SunooBertsch |
closed by #301 |
I ran into an issue this morning where using the "Page Link" field caused internal server errors. The only fix was to change the field type from "Page Link" to "Relationship". This stopped Apollo from throwing the internal server errors, but this is something my team and I have run into before.
Occasionally, we will encounter internal server errors and the only solution is to either delete the ACF field that is causing the issue and recreate it, or to change the meta field type. The only way we can figure out which field is causing the issue is via trial and error.
Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: