Hi,
First thx for the video, several things happenin and some of them have always been that way.
– The list of the fields has always depended on the BB preview settings and not on the setting in the “post module” hence as you are on a “page” you get the list for a page :/ that one of the shortcoming I didn’t find a good way around need to take a look again
– More fields are exposed as a side effect of pods 2.8 still not sure if I’d wan’t to keep some of them…
– You can workaround that using BB Shortdcodes like you did or use the “pods” version -> Template, Magic Tag
Magic Tags: (the way I use it) are the most powerful way and most “visible” as the syntax is shorter! see https://docs.pods.io/displaying-pods/magic-tags/using-magic-tags/
Hope that helps to clarify some things!
Hi @quasel
You’re more than welcome. I always find videos make it easier.
1) List field dependencies – Yes maybe that was an oversight on my part and a frustration I ran into before and ended up having to switch to ACF but I’d love to not need ACF.
I have seen some BB modules break it into two sets, so first there’s only one drop down and that asks you to select the post type single you or tax term you want to see the fields or data for.
Then a second field appears and only shows field related to that post type. That way it prevents them all being mixed together.
2) More fields exposed – Yes, I think maybe 2 or 3 might be worth keeping but most are arbitrary like has pinged etc. Maybe an option would be to have a settings page for your plugin and allow people to choose from Advanced (Show all) vs Intelligent (Filter based on what is most practical for most users/use cases)/
3) I am not that familiar with MagicTags but it sounds like this is a good method to try next. I will have a look into that and see how I get on but would still love for your plugin with its ease of use to make a few improvements to cater for these situations too. 🙂 I appreciate you might be busy though.
Thanks for your help.