Visibility Conditions based on custom taxonomies

[StrangeTech]

This has now come up for us as a limitation.

Currently for us to be able to release a site we have been working on we need either this feature or one of the following:

1. URL parameters block visibility with front-end rendering:

Allow block visibility conditions based on url parameters to work with front-end rendering

From our testing url parameter visibility conditions for blocks do not seem to work within a query with front-end rendering switched on. This feature will be extremely useful for toggling the visibility of certain elements based on changes to filters. [Screenshot 2023-04-19 at 13.16.07] Thanks.

2. Custom ACF field to be working within a Taxonomy Terms block with front-end rendering:

Custom ACF field in Taxonomy Terms block within a Query block not displaying on front end

Description: We are using a Taxonomy Terms block to display an ACF custom field for a Taxonomy within a Query block (a price suffix for the duration of a subscription term). [Screenshot 2023-04-17 at 12.04.31] This displays perfectly in the editor [Screenshot 2023-04-17 at 12.11.14] But on the front-end nothing displays: [Screenshot 2023-04-17 at 12.13.20] If we specify a fallback it is used. Displaying standard taxonomy fields such as description works perfectly: [Screenshot 2023-04-17…

Using any of these we can achieve the desired result but are currently blocked on all three.

@Louis, can you take a look and see if one or more of these can be included in an upcoming Cwicly version? We will be really grateful for any of these that you are able to fit within your release schedule.