You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But passing a zero gets evaluated as a falsy string "0" rather than a true boolean value. This works but it doesn't seem particularly clean. Might be better to just have two template global methods DisableSubsiteFilter() and EnableSubsiteFilter()?
Or alternately for the use case I'm encountering it might be handy to opt a particular object relationship out of Subsite filtering altogether. I'm having to disable subsite filtering both on the CMS fields and in the template.
The text was updated successfully, but these errors were encountered:
You can create a class implementing TemplateGlobalProvider interface and add the methods there. Possibly the Subsite class itself can implement that interface and expose the mechanism for templates. Happy to look at a PR.
I'm able to disable subsite filters in a template by doing the following.
But passing a zero gets evaluated as a falsy string
"0"
rather than a true boolean value. This works but it doesn't seem particularly clean. Might be better to just have two template global methodsDisableSubsiteFilter()
andEnableSubsiteFilter()
?Or alternately for the use case I'm encountering it might be handy to opt a particular object relationship out of Subsite filtering altogether. I'm having to disable subsite filtering both on the CMS fields and in the template.
The text was updated successfully, but these errors were encountered: