Skip to content

Conversation

@jonafato
Copy link
Contributor

@jonafato jonafato commented Mar 24, 2023

This is most of what's needed to upgrade to the latest beta release of render-engine. Known issues:

  • Setting the jinja environment undefined handler to StrictUndefined seems to have broken rss rendering

  • The rss feed name override behavior has stopped working

- Archive pages are missing their url at time of generation, so the archive list page links back to itself (href="") instead of to the correct posts

@jonafato jonafato force-pushed the upgrade-render-engine branch from b2eb21f to 649f756 Compare March 24, 2023 21:49
This is most of what's needed to upgrade to the latest beta release of
render-engine. Known issues:

- Setting the jinja environment undefined handler to StrictUndefined
  seems to have broken rss rendering

- The rss feed name override behavior has stopped working

- Archive pages are missing their url at time of generation, so the
  archive list page links back to itself (href="") instead of to the
  correct posts
@jonafato jonafato force-pushed the upgrade-render-engine branch from 649f756 to 106b181 Compare March 24, 2023 21:52
This attribute used to be "feed", but some recent update to
render-engine has capitalized the first letter.
jonafato added a commit to jonafato/render_engine that referenced this pull request Apr 5, 2023
These templates used to work when using the StrictUndefined undefined
behavior in the jinja2 environment, but in recent releases, this causes
the build to fail. This issue can be seen at
Python-Community-News/Site#38. Using the `is
defined` test results in similar behavior even when `StrictUndefined` is
set, allowing site developers to catch typos or other missing template
context without breaking their rss feeds.

This change also includes a new test and a test fixture to create a
jinja2 environment that can be modified with the scope of a single test.
jonafato added a commit to jonafato/render_engine that referenced this pull request Apr 5, 2023
These templates used to work when using the StrictUndefined undefined
behavior in the jinja2 environment, but in recent releases, this causes
the build to fail. This issue can be seen at
Python-Community-News/Site#38. Using the `is
defined` test results in similar behavior even when `StrictUndefined` is
set, allowing site developers to catch typos or other missing template
context without breaking their rss feeds.

This change also includes a new test and a test fixture to create a
jinja2 environment that can be modified with the scope of a single test.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants