Displaying ACF values of a taxonomy not working

Hello,

There was not yet support for custom taxonomy fields made in ACF. I added basic features in the newest plugin update, for text/textarea and image fields. So, the following should work now:

[taxonomy tax_name term="id" field="field_name"]
[taxonomy tax_name term="id" image="field_name" size="thumbnail"]
[taxonomy tax_name term="id" image="field_name" size="thumbnail" out="url"]

This last one is not well documented yet, but it can output id, url, title, description, caption, etc.

So, please let me know how that works for you.

I’m sorry about that, Eliot. I thought I had read in another one of the support threads that custom taxonomy fields were supported. My mistake!

Thank you very much for adding this for me. I’ve tested it out on text and textarea fields and it works perfectly. I haven’t had occasion to test custom image fields assigned to taxonomies yet, but I will soon enough. It’s probably needless to say I’ll be back if I have any issues ??

And also, many thanks for your continued work on this plugin. I’m really enjoying playing around with the new features you’ve been adding. I haven’t tried pagination yet, but I can’t wait to see how it goes.

Cheers!

Thanks for letting me know that it’s working.

There was some tentative support for custom taxonomy fields made with another plugin – except I forget which one! – and I hadn’t discovered ACF’s ability to add taxonomy fields until recently. These are stored differently, so I had to add a way to retrieve them.

This plugin is a pet project of mine, so I enjoy working on it. I use it on all WordPress sites I build, so any new feature or improvement is useful for me as well.

Pagination was much requested, but I wasn’t able to figure out a good way to implement it until earlier this week. It’s brand new and needs to be road-tested, so any feedback is welcome.

I’m so glad that adding all the features people request is useful for you — you go above and beyond compared to many other plugin authors, so it’s nice to know you’re benefiting as well ?? Perhaps there’s something I could do to help you out a little. Would there be a need for a French translation of the plugin? I’ve never done it but would like to try, if you’re interested…

Hope you’re having a good weekend!

I appreciate the offer of a translation – at the moment, there is no internationalization support at all. The areas which I can imagine being translated are:

1. Reference pages
2. Content overview page – just headers like “field”, “taxonomy”

I’ve been thinking how to improve the reference pages. Several times, I had feedback that it’s difficult to learn how to use the plugin, and that more examples would help. It’s good that all features, shortcodes and parameters are documented, but it’s also not so well-organized or simple to navigate.

Right now, all reference pages are a bunch of HTML files, and probably wouldn’t be pleasant to translate. I’m thinking of converting them to Markdown syntax, which are easier to read and edit.

Also, I’m looking for a different layout. The reference sections are split in horizontally-listed navigation tabs – except that now, there are more sections than can fit in a row. For example, there’s a long description of the [pass] shortcode hidden under “Other”; sections for ACF and WCK fields can only be reached from the Welcome page; etc.

So, I’m working on improving these points. Perhaps after the reference pages are better organized, they can be translated – if you think it would be worthwhile! ??

—

I have some ideas in progress for this plugin. I’d like to put together a simple site for it, with complete reference and examples. I also have a number of modules that provide extended features like drop-downs and sliders; and wondering how best to package it, as individual plugins, or all-in-one toolbox; and whether it should be free or valuable enough as commercial “pro” version.

So, as things move forward, it would be great to have feedback on your thoughts, suggestions for features or points to improve.

Hi Eliot,

If you think it would be best to reorganize the reference section before translating the plugin, then perhaps I could help you with that as well. But before I get off the subject of translation, I’ll just mention that I’m comfortable with HTML but have never used Markdown, so that doesn’t matter to me. ??

In regards to more examples, I’ve been thinking the same thing. I have to admit that I do get confused at times about how to use some of the parameters. Perhaps I could work out a few examples I think would be useful and send them to you…

Concerning the organization of the reference pages, I think you should put the settings on the main (introductory) tab, which would give you space for something else in that tab — either the Pass section or a new Custom Fields section which would include both ACF & WCK. I also think the main tab should be renamed to Index & Settings (to indicate that links to the various reference sections can be found there). These small changes would improve the visibility of more settings. I’ve got some other ideas, but these would all depend on how you choose to set things up…

Finally, regarding your extended functionality modules, I think they should all be packaged together and sold as the Pro version. You work so hard on this plugin, you bend over backwards for everyone, implementing every request possible. You deserve to earn something from it! The plugin, as it stands, is already extremely useful. You can continue to improve the basic functionality, of course, but it’s not like withholding the new modules will be a detriment to the free version. Just so long as you don’t remove any of the current functionality from the free version, since that is never well-received.

If you would like to continue this discussion, perhaps we should move it off the forum? If so, feel free to email me: julie (at) niackery (dot) com.

BTW, I just remembered something about the original topic of this thread. I think it was me who had previously requested support for taxonomy fields. I was trying to get the Tax Meta Class plugin to work, but I never did get it figured out ??

Cheers!