Believe me, I want to! We’d much rather use one of the many other ways that Cwicly allows, unfortunately we seem to be blocked at every turn on this one. Please see here for a full outline of what we have tried:
And as mentioned - this related one:
If you think that these are bugs rather than feature requests, we’ll be happy to change them and see them fixed also.
Both these feature requests are valid and will definitely be addressed in due course.
However, does your price suffix necessarily need to be implemented with a custom taxonomy?
Without a clear understanding of your current setup, it’s difficult for me to determine the best approach.
Perhaps if you could provide additional details, we might hopefully be able to find a workaround.
Given the fact that we have multiple filters (e.g. subscription duration and currency), using a standard post category as a taxonomy didn’t occur to us - I suppose we could switch the subscription duration custom taxonomy for a standard post category and then use the Post Category visibility filter for it to display the price suffix. This is not ideal for a number of reasons but as long as Post Category visibility filters work with front-end rendering, then it should technically be viable.
@Araminta, can you confirm whether this is a reasonable workaround or if you have any other better suggestions.
Perhaps it might be easier for you to add a filter to your Query, using the shortcode whitelist.
This way all the logic is done in PHP so you can directly access exactly what you need (your custom taxonomy).
If you need any help setting this up, I’ll let @Louis know!
However, if you feel more comfortable with using a standard post category as a taxonomy, then that might be the best solution.
Please don’t hesitate to let me know if you have any questions on this.
Apologies for not focusing on the client aspect earlier.
To answer your question, I can confirm that on my end, post category visibility conditions work as expected with frontend rendering.
However, if you experience any issues with this, please do not hesitate to reach out to us, and we will fix it as soon as possible.
If you decide to use the shortcode route, be sure to let us know if you need help!