jjci

Documentation page URL: https://pods.io/docs/code/pods/find/

Under “Additional Parameter Options”

Join:
Additional table(s) to JOIN, using SQL syntax like “LEFT JOIN my_table ON my_table.id = t.id”

Regarding my application, I am using it in some PHP code designed to respond to an AJAX call.

I have since developed a work-around similar to what you suggested. However, I would still like to understand it if I should ever consider using JOIN in the future as a means to retrieve related data in a single extract process.

That said, this is no longer inhibiting my development, therefore you can consider it resolved.

Thanks,
JJCI

Thank you.

Bernhard,

Thanks for your response. Sorry for not getting back to you sooner.

Will review the documentation provided in the links.

Regards,
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.

Good to know. Thanks to all for investigating.

I experiencing an issue with a particular POD CPT definition not saving on the ‘Edit Pod’ back-end screen.

How was your issue resolved?

Thanks for the detailed explanation(s). All good points.
I am experimenting with PODS taxonomies as a means to set ‘status’ values at various levels of a hierarchy of PODS CPT tables. That is, I have three tables in a parent->child->grandchild relationship as well as a number of other related tables. I am hoping to use a common taxonomy to set the ‘enabled/disabled/suspended’ status value for each table entry where the taxonomy setting for a given entry MAY be affected by the setting(s) of the parent and/or grandparent settings above it. The alternative was to introduce 2-3 separate ‘status’ fields into the structure of each CPT, but that would just become a nightmare to develop/maintain, so I doubt I will go with that particular solution. It is so much easier to assign one (or more) taxonomies to a give CPT and to use common filter-level code to evaluate the taxonomy terms and set the status value(s).

The biggest problem I am having right now is evaluating the taxonomy terms for a given table entry. This is a WordPress issue rather than a PODS issue, but it’s still an issue. Just have to do more research, I guess… ??

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…”.

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.

Did this turn out to be a false-positive?

I am just in the early stages of exploring how to best apply Custom Taxonomies, so I am trying to understand your approach of using taxonomies in conjunction with relationship fields. I think I understand the solution you provided and how it works, but I don’t think I understand the problem that you were trying to solve. That is, why would you want to select a value from a simple list in a relationship field and then translate the selected value into a taxonomy term rather than just selecting the taxonomy term directly? What am I missing?
Your feedback would be appreciated.

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.

Understood.

Thanks, Jory.

Good suggestion regarding GF support.

You may want to checkout plugin FacetWP which also has a PODS add-on.