{%- if config.extra.enable_post_view_navigation and page.lower or page.higher %}
I'm pretty sure its broken since config.extra.enable_post_view_navigation and page.lower evaluates first.
If tera supported brackets for specifying order of operations I could fix the issue by writing it as:
{%- if config.extra.enable_post_view_navigation and (page.lower or page.higher) %}
As a workaround I was able to solve the issue by writing it as:
{%- if config.extra.enable_post_view_navigation %}
{%- if page.lower or page.higher %}
I came across some code like:
I'm pretty sure its broken since
config.extra.enable_post_view_navigation and page.lower
evaluates first. If tera supported brackets for specifying order of operations I could fix the issue by writing it as:As a workaround I was able to solve the issue by writing it as:
But that is not ideal.