 aguko
Post count: 43
|
Since I have posted to the [Resolved] topic, I post a new topic.
It is a continuation of this topic.
https://www.masterpressplugin.com/support/topic/i-want-to-separate-incoming-objects-for-every-related-post-field
Can I separate for every field similarly by “incoming_terms” in custom taxonomy (at taxonomy-[custom taxonomy].php template )?
ex. $wf->the_term->incoming_terms(“for=field_set.field”)
thanks.
|
 traversal
Post count: 207
|
Hi there. You should be able to do this yes. Have you tried to do this in the taxonomy-[tax_name].php template? Can you describe your field setup in a bit more detail?
Note that, if you want to use a standard WordPress “loop” in that template, you can also add “query=1” to the arguments before the standard loop code, and that should hopefully then show the correct posts.
$wf->the_term->incoming_terms(“for=field_set.field&query=1”);
if (have_posts()) : while (have_posts()) : the_post();
etc…
Thanks
|
|
aguko
Post count: 43
|
I explain something to do in detail.
I want to make the flexible relationship for every keyword using custom taxonomy.
By the category of wordpress, I cannot set two or more parents to one keyword. Then, I set “Related Terms” to custom taxonomy, and I want to be able to set two or more parents to one keyword.
I drew the figure.
https://cacoo.com/diagrams/lP4GdGERZOl7MEs3-1E6A8.png
1 ) Input a parent keyword into the “parent field” of each keyword.
2 ) Display the taxonomy-keyword.php of a parent keyword. The keyword which makes itself parents using “MEOW_Term :: incoming_terms” is displayed.
3 ) Add some values to the child field using “MPFT_RelatedTerm :: value_for_set.”
Can I realizable?
Thanks.
|
|
traversal
Post count: 207
|
Wow, thanks for that. So do you actually need to do step 3, and store the child relationship? The children of a keyword are defined by the incoming_terms query right?
You can certainly store the reverse relationship if you want to, but it means you need to keep them in sync, which is probably a little tricky.
By the way, the value_for_set method is not intended to be called directly, it basically enables the fields to be set via direct assignment. Something like this should be possible:
http://pastebin.com/drYxbbm5
|
|
aguko
Post count: 43
|
Thank you for the additional method to the field.
And I want to save each child-parent relationship at DB for other purposes.
However, I was not able to separate and display on the field by “$wf->the_term->incoming_terms(“for=field_set.field”).”
Although the following codes were written at taxonomy-keyword.php, it did not display.
http://pastebin.com/YHiEhUYT
custom taxonomy: keyword
field set: relationship
field(Related Term): parent
field(Related Term): child
thanks.
|
|
traversal
Post count: 207
|
Okay thanks. I’ll need to setup a test environment and find out why that’s not working.
|
|
traversal
Post count: 207
|
Hey, I’ve just looked into this and realised that the code in http://pastebin.com/YHiEhUYT is not quite right.
The first argument for incoming_terms is actually the taxonomy name. Have you tried making the first argument in line 12 and 18 the string “keyword” to specify the keyword taxonomy?
|
|
aguko
Post count: 43
|
I referred to http://pastebin.com/Y0B7qd78, and described it.
How should I specify the first argument in this case?
|
|
traversal
Post count: 207
|
Hi. Here is the reference in the class documentation:
https://www.masterpressplugin.com/docs/developer/methods/meow-term-incoming-terms
It should be something like this:
http://pastebin.com/0gPGAGr4
Let me know if that works. Thanks
|
|
aguko
Post count: 43
|
I was able to display for every field!
“Incoming” is a wonderful function.
Thank you very much!
|
|
traversal
Post count: 207
|
Great. I’m really glad that does actually work!
The “Incoming” functions are really nice – the queries running behind them are quite difficult, so it’s good that you don’t need to worry about that.
|
.
