We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I used the latest JBake 2.5.0 release, enabled paging and set the post per page parameter:
index.paginate=true index.posts_per_page=10
However in my freemarker template the variables nextFileName and previousFileName does not exist:
nextFileName
previousFileName
<#if (nextFileName)??> <#-- is always false --> [...] </#if> <#if (previousFileName)??> <#-- is always false --> [...] </#if>
In org.jbake.app.Renderer#renderIndex() the variables are put to the model map:
org.jbake.app.Renderer#renderIndex()
[…] model.put("previousFileName" …); […] model.put("nextFileName", …); […]
But the model is never given to freemarkers template engine. Maybe here the ModelRenderingConfig is needed instead of the used DefaultRenderingConfig.
ModelRenderingConfig
DefaultRenderingConfig
The text was updated successfully, but these errors were encountered:
Have the same issue
Sorry, something went wrong.
fixes jbake-org#310 - propagate nextFileName and previousFileName to …
264e464
…the model * adds `currentPageNumber` to the model * adds `numberOfPages` to the model
Thanks for taking the time to raise an issue about this.
2822cfc
No branches or pull requests
Problem
I used the latest JBake 2.5.0 release, enabled paging and set the post per page parameter:
However in my freemarker template the variables
nextFileName
andpreviousFileName
does not exist:Possible solution
In
org.jbake.app.Renderer#renderIndex()
the variables are put to the model map:But the model is never given to freemarkers template engine. Maybe here the
ModelRenderingConfig
is needed instead of the usedDefaultRenderingConfig
.The text was updated successfully, but these errors were encountered: