Hi @jjci
Have you checked your browser console for javascript errors?
Also, did you check for plugin conflicts? https://docs.pods.io/faqs/plugin-theme-conflicts/
Cheers, Jory
Thread Starter
jjci
(@jjci)
Just to clarify, this issue is happening for ONLY ONE of my Pods. The other Pods are being updated with no problem.
I should also clarify that this is happening on the back-end Admin Edit Pods.
Given these, would this still point to a browser error or plugin conflict?
In any case, I will see what I can find.
Hi @jjci
Could you create an JSON string export with the Migrate Packages component and share it here?
Cheers, Jory
Thread Starter
jjci
(@jjci)
I tried to create the JSON using the Migrate Package component. However, I ran it twice and it timed-out both times. I had selected only the one POD in question and no templates.
I had done something else before that. On the Edit Pods screen, I used the ‘Duplicate’ function on the POD in question, and that process worked OK. However, I made a simple change to the new POD and tried to save it, but I received the same error message as I di when trying to update the original POD. So, there is something in this particular POD definition that is causing the failure, especially when the save function is not failing for any other PODS.
Should I delete the original POD definition and recreate it? If I did, what would happen to the existing Relationship fields? I am not concerned about my data because right now it is only test data and can be rebuilt if necessary.
I need to make changes to this POD in order to continue my development and testing, so I am running out of time to debug this issue. Please let me know if I would be better advised to scrap the failing POD definition and start over.
Thanks.
Thread Starter
jjci
(@jjci)
Just another bit of information as per one of your comments.
I checked my browser console during one of the update failures and it indicated an error “Failed to load resource…”.
Thread Starter
jjci
(@jjci)
In order to proceed with my development, I had to delete the POD that was causing the problem.
The test data contained only four(4) entries, so it can be recreated fairly easily.
At this point, I still don’t know what went wrong. However, I suspect it was a browser-based anomaly that corrupted the POD definition.
We can consider this closed.
