Pelican: pages not shown after upgrading to 3.7.1

Created on 24 Jan 2017  Â·  8Comments  Â·  Source: getpelican/pelican

Hi

After I upgraded pelican to 3.7.1, I met a problem and maybe that's a bug.

In pelican 3.7.1, pages html files are successfully generated in the output directory but they are not collected into PAGES variable in jinja2 template. In 3.7.1 {{PAGES|length}} has a value of 0.

This problem doesn't occur if I use 3.6.3

Most helpful comment

http://docs.getpelican.com/en/latest/faq.html#since-i-upgraded-pelican-my-pages-are-no-longer-rendered

On 24 January 2017 at 16:41, JunjieCai notifications@github.com wrote:

Hi

After I upgraded it to 3.7.1, I met a problem and maybe that's a bug.

In pelican 3.7.1, pages html files are successfully generated in the
output directory but their are not collected into PAGES variable in jinja2
template. In 3.7.1 {{PAGES|length}} has a value of 0.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/getpelican/pelican/issues/2097, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEOv-rkHn3859ESAEFKeb6ar9BbUkptuks5rVhuggaJpZM4Lsarf
.

All 8 comments

http://docs.getpelican.com/en/latest/faq.html#since-i-upgraded-pelican-my-pages-are-no-longer-rendered

On 24 January 2017 at 16:41, JunjieCai notifications@github.com wrote:

Hi

After I upgraded it to 3.7.1, I met a problem and maybe that's a bug.

In pelican 3.7.1, pages html files are successfully generated in the
output directory but their are not collected into PAGES variable in jinja2
template. In 3.7.1 {{PAGES|length}} has a value of 0.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/getpelican/pelican/issues/2097, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEOv-rkHn3859ESAEFKeb6ar9BbUkptuks5rVhuggaJpZM4Lsarf
.

Thank you. It works fine now!

I also had this issue.

Thanks for the clear advice and easy fix!

I think this may need a re-open and more fixes: Default theme notmyidea still uses PAGES at one place.

Good catch!

I found that that issue has been fixed in the main pelican-themes repo.

Maybe we could replace the included pelican/themes/notmyidea with a git submodule link to the fully updated pelican-themes repo. This would stay up to date, and give users many more choices.

Thoughts?

Probably the right direction but I suspect it's a bigger move? It would be awesome if the sub-module would be considered but still not hold back the tiny fix this ticket needs to get the page listing back to healthy. I'll offer a pull request in a minute. Can we re-open this ticket? I lack permissions to.

Let's leave this ticket closed and focus on updating the old themes that are using depreciated the depreciated pages. After all, the issue is with the theme(s), not with pelican itself.

They will merge and fix this in a few days. No need to rush.

It's the default theme so I don't really agree that it's just a theme. It would be awesome if people new to Pelican no longer have to wonder what they are doing wrong that the page listing is empty.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

networkpadawan picture networkpadawan  Â·  3Comments

Lucas-C picture Lucas-C  Â·  4Comments

quack1 picture quack1  Â·  6Comments

Moini picture Moini  Â·  6Comments

iKevinY picture iKevinY  Â·  5Comments