-
-
Notifications
You must be signed in to change notification settings - Fork 264
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
Pods API Error #5952
Comments
@refuelcreativeadam The fatal error however is something different. This is a resource error. Might need some more digging to find/fix that issue. |
I've tested and while there's less instances of the error, it still appears 10 times in the wordpress debugging.
Do you suspect something else is causing the fatal error?
as mentioned above, the API error is still showing. As is the critical error Also note that I'm not very familiar with GitHub so apologies if I've missed something Edit: formatting |
I've been looking into this @refuelcreativeadam and I believe I misread initially. I was fixing the PHP notice and realized you encountered what appears to be a timeout issue. I can tell this is what is happening because it fails after a great deal of time. I was able to pinpoint that you have at least one problematic location that is blowing things way up. See that here: https://staging-ntcommunity.kinsta.cloud/wp-json/wp/v2/location?page=63&per_page=1&orderby=title&order=asc You can see that I've set per page to 1 and the page to 63 so I'm basically getting just one item, the 63rd item in the list ordered ascending by title. The affected post ID is 7689 Can you go edit that location from the admin area and let me know if you see anything up there? Do you have a ton of data on that one? If I look briefly at the structure, I notice you have it set to recurse relationships data many levels deep. This can cause a recursion loop especially when something has a bidirectional relationship field on it. Check your depth, perhaps consider reducing the depth to 1 or have it return IDs only. You can adjust that when you edit the field configuration in the Pods Admin > Edit Pod screen. |
Fixes #5952 for just the notice, the other issue is configuration-related
hi @sc0ttkclark, I had a look at that location. There's nothing there that stands out. It's linked to multiple Services but no more than any of the other locations for that Organisation. I tried changing it to only return the ID and while it helped for the link you provided, my original link still times out. I tried changing all relationships to only return the ID but it didn't help with the original link Just as a bit of an FYI, the way we have relationships set up is this: Each Organisation can have many Locations Each Location can only have only 1 Organisation Each Service can have many Locations |
Hi @sc0ttkclark @JoryHogeveen something I've just noticed with this. Is that I'm unable to set it to only return the ID. I can select the option and hit save but then if I go back and check it, it's changed back to "Full". Any idea why? |
I was able to find out what was causing this, it was the Pods Alternative Cache plugin. It's been disabled and all relationship fields have been set to return the ID only |
This was originally raised in Wordpress Support
Our website is getting a mobile app version but we’re having trouble syncing the data to the mobile app.
The above link is the request that’s getting put in.
We get this error a bunch of times and then a critical error:
Do you guys have any idea how we can resolve this? or do we need to find a workaround?
I've set up a staging site that replicates the issue found on the live site, and it has wordpress debugging switched on
Testing instructions
Expected behavior
One the page loads, which should be quite fast, it should display all the listings on page 4 of the Locations POD. It should simply list them out as though in a text file
Pods version
Version 2.7.26
Other super helpful information
WordPress Environment
Pods Package Export
Staging Site Access
The text was updated successfully, but these errors were encountered: