Skip to content
New issue

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

On fresh install: "simple" theme build error using publishconf.py #2487

Closed
julien-h opened this issue Dec 6, 2018 · 3 comments

Comments

@julien-h
Copy link

commented Dec 6, 2018

❯ pelican --version
4.0.1

If I use the "simple" built-in theme:

THEME = 'simple'

Then the following command works:

pelican content

But not:

pelican content -s publishconf.py

Outputs this error:

CRITICAL: TypeError: not all arguments converted during string formatting

But not if I use the "notmyidea" built-in theme.

EDIT: Same problem with a fresh install using pelican-quickstart.

@julien-h julien-h changed the title "simple" theme build error using publishconf.py On fresh install: "simple" theme build error using publishconf.py Dec 7, 2018

@rask004

This comment has been minimized.

Copy link
Contributor

commented Jan 10, 2019

Is anyone else able to replicate this? I tried with a quickstarted project but using publishconf.py worked.

Additionally, I cannot find the mentioned error when searching in pelican.

@rask004

This comment has been minimized.

Copy link
Contributor

commented Jan 10, 2019

@julien-h What plugins are you using? Also, what settings are different between your pelicanconf.py and publishconf.py?

@bryanbrattlof

This comment has been minimized.

Copy link
Contributor

commented Jan 10, 2019

I was able to reproduce this, but I suspect this is another #2442 issue.

Looking into the simple theme's base.html source, it still uses the old format to generate the feed's urls.

CATEGORY_FEED_ATOM_URL|format(category.slug)

The reason why pelicanconf.py works, is because doesn't build the category feeds like publishconf.py does.

CATEGORY_FEED_ATOM = 'feeds/{slug}.atom.xml'

Edit: Just now noticed that this hasn't been fixed yet. I can have a PR ready in a few hours if It's still needed by then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.