Accessing Taxonomies

I’m glad that you liked it. Just to clarify, this plugin will not replace Frontier. We will be using the same internals, with a different UI for Frontier 2 once we can figure out how to get it to work with Pods::display() the same way Pods magic tags do now.

“Whats the syntax to access taxonomies inside a template”

Right now this isn’t something that it supports. It will soon. So let me turn this back around on you: “what should the syntax be?”

If you have a custom taxonomy foo, you might think it makes sense that it should be {foo.name}, but if there is a meta field called “foo” we have a problem. {taxonomies.foo.name} is not particularly intuitive, but would work.

Hi Josh,

you made me think about it, and here is my suggestion. I don’t know if there are any reserved characters but since you used @ in magic-tags and # in control structured, why not use * or ~ like {~foo.name} for taxonomies?

on a side note, any ETA on Pods 3.0 and Frontier 2?

That’s something to consider, but I’m not sure about adding a new symbol. # isn’t limited to control structures. It signifies a Handlebars helper.

It might make the most sense to register special each loop as a Handlebars helper, that way you’d be able to show all terms, with something like {{#taxonomy taxonomy_name}}{{#name}}{/taxonomy}}

Pods 3.0 beta will be ready once these issues are resolved.

Frontier 2 will be ready as soon as David can make time for creating a Handlebars.php helper to work with Pods Objects. Once we can scale CalderaWP to the point that it can be David’s fulltime employment setting aside time for Frontier will be easier. That is one of the reasons we are doing this.

It might make the most sense to register special each loop as a Handlebars helper, that way you’d be able to show all terms, with something like {{#taxonomy taxonomy_name}}{{#name}}{/taxonomy}}

I take it, can you wrap it please. ??

Once we can scale CalderaWP to the point that it can be David’s fulltime employment setting aside time for Frontier will be easier. That is one of the reasons we are doing this.

Hit me up on GitHub (following you) to send me an email, maybe I can help or we can find some “arrangement”.

oh, and resolved.

Want fries with that? ??

I will try and make it work next time when I’m in the code. Last time I was in I added support for loading template for files, whic–if it works–will be awesome.