Custom Classes & Showing Taxonomies

working on it. no success yet. stay tuned.

joelle,

i think i got it. rather complex issue. please update to v1.34 and report.

best,
JdA

Hi! That DID work. Hurrah! My only issue is that it’s showing both sets of taxonomies. This isn’t the end of the world, but ideally, I’d like to be able to just show the terms from *one* taxonomy and not both.

But this is awesome. ??

well, if it belongs to more than one, it belongs to more than one…

may i go to the beach now? hahaha ??

Of course you can go to the beach. haha!

So, I’m curious – the taxonomy_terms doesn’t do anything now, correct? It’s just the listing of category=text in the fields? And it will show all the taxonomies. That’s fine, I’ll work with it! but in the future, you know — after the beach someday — maybe there’s a way to filter that a bit more.

Don’t forget your sunscreen. ??

FWIW, I snuck into your plugin and added some spans and classes before and after the taxonomies and then used CSS to hide the taxonomy I didn’t want, as well as the single line break. I realize I’ll need to do this again if you update it, but it was the only for me to get the results I needed for my client right away. ?? I don’t know if that info is helpful to you, but I figured I’d share my process.

you can only use category if post_type=post. that’s the way wordpress works.

so, if you want to narrow your selection within books, you use both taxonomy= along with taxonomy_terms=. however, as you have to specificy the exact terms. and this might be tricky. here’s an example:

[the_future_posts post_type=”exhibition” taxonomy=”exhibition_category” taxonomy_terms=”2017″………………….

where “2017” is the category slug name. note that the Pods plugin always adds a “_category” suffix to the taxonomy.

depending on what you have specificed, it should be something like this:

[the_future_posts post_type=”books” taxonomy=”books_category” taxonomy_terms=”red-falcon-series”………………….

instead of introducing <span class=”tax_display”> you can use class “tfp_categories”. it’s already there for you.

and if you need to use different settings for each instance of The Future Posts, you can use “theme_custom=my_suffix_001” or “theme_custom=on_the_left” or whatever suffix name you want the plugin will generate the class for you, and then use it as DIV class “my_suffix_001_categories” or “on_the_left_categories”.

you can only use category if post_type=post. that’s the way wordpress works.

so, if you want to narrow your selection within books, you use both taxonomy= along with taxonomy_terms=. however, as you have to specificy the exact terms. and this might be tricky. here’s an example:

[the_future_posts post_type=”exhibition” taxonomy=”exhibition_category” taxonomy_terms=”2017″………………….

where “2017” is the category slug name. note that the Pods plugin always adds a “_category” suffix to the taxonomy.

depending on what you have specificed, it should be something like this:

[the_future_posts post_type=”books” taxonomy=”books_category” taxonomy_terms=”red-falcon-series”………………….

It should spit out the terms within the books category of “series”. If it’s not dynamic, it doesn’t help, unfortunately.

instead of introducing <span class=”tax_display”> you can use class “tfp_categories”. it’s already there for you.

Yes, I know and I call upon it, but because I had to hide the first taxonomy that I didn’t want shown, I needed to be able to address it and I couldn’t do that without a tag around it of some kind. Does this make sense? It’s showing me the terms from ALL my taxonomies (in my case, there are two for ‘books’ – series and world – I only want series). So i had to use CSS to hide the ‘world’ terms.

and if you need to use different settings for each instance of The Future Posts, you can use “theme_custom=my_suffix_001” or “theme_custom=on_the_left” or whatever suffix name you want the plugin will generate the class for you, and then use it as DIV class “my_suffix_001_categories” or “on_the_left_categories”.

That’s handy, thank you! ??

I also wanted to make sure you saw my feedback from yesterday about the permalinks. I added my snippet back to my functions file and it works now, but you’d mentioned adding that feature to your plugin, but when I tried it, it didn’t work. We got caught up in the taxonomies, I didn’t want you to hear about it later if someone says it doesn’t work. ?? It’s fine on my end, as I said, I added the snippet back and all is well.

I also hope you received my donation. I really appreciate your attention to this!

sorry, i didn’t understood? what’s yesterday problem about permalinks?

ho, that was more than generous! thank you, joelle.

now i can buy an outrageous expensive luxury suncreen! ??

hey! what permalink problems?

Hiya!

From your change:
* Added a new method of having pretty permalinks in ALL posts (including ‘Future’ posts), keeping WordPress’ Permalink Settings whatever they may be. For instance: https://the-future-posts.local/my-category/sample-post/. Thanks, Joelle!

I said this. ?? Basically, whatever you added isn’t working on my end. I had to keep the snippet in my functions file, without that in my functions, the links just went to the un-pretty permalinks. When I dropped it back in, your links were pretty again. So whatever change you made to incorporate that didn’t take on my end. But maybe it’s me!

hi,

please paste that snippet into here.

i thought this was already solved… ??