How to show custom taxonomies in Essential Grid skin builder

Hi,

I have custom post types and want to show them in Essential Grid. I can find the custom allright, and select the correct custom type etc.

The trouble comes when I want to show the categories of the custom type in each post. We have a few:

  • speaker
  • year
  • language
  • series
  • categories (standard)

I am able to use the skin editor to show categories, but I can’t find any way to post the other stuff. Can you help?

This picture show what I actually want to make in essential grid. Show the different taxonomy under the title. But how to show them in the skin builder? Source: http://www.amaravati.org/audio/chapter-1-part-1/

Here you can see I can find the custom types allright, so Essential grid can see them and even show the ‘slugssss’.

I have been toying with the skin builder and nothing I choose could remotely show anything I wanted!

Help?

Hi there,

Thanks for writing in.

You have to select the Element as Taxonomy List, then Taxonomy with your preferred taxonomy. It’s currently selected as Tags in your screenshot.

Thanks!

Oops… rather obvious, sorry about that.

Although… I did find the taxonomies choice, but whenever I select one from a custom post, it says AJAX error when I try to display/preview them

I tried:

  • uninstall plugin essential grid
  • reinstall it
  • changed the taxonomy to another custom type taxonomy: languages, speaker etc --> same result
  • changed the taxonomy to an official wordpress type: no problem

Help again?

I know it is Sunday… but help?

@Rad help?

Some setting in your taxonomy setup is causing the issue. Regretfully, we don’t have support for custom taxonomy setup. Please consult with a third party WordPress developer to make your custom taxonomy display.

Thanks.

hi, thanks for checking! Will contact the developer, thanks

You’re welcome.

Hi,

Just FYI: I found another topic discussing the error: https://theme.co/apex/forum/t/essential-grid-causing-500-internal-server-errors/7476

It was rather ‘useful’ to turn on the WP debug mode. It showed actually where the error originates. Perhaps obvious to some, but I forgot.

So there was indeed an issue with the plugin.

Just FYI for those who arrive at this same kind of error in the future.

Bye,

Thanks for sharing!