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

Critical NoneType error with pelican 4.5.0 when installing Flex theme #687

Open
nidupb opened this issue Sep 7, 2020 · 1 comment
Open

Comments

@nidupb
Copy link

nidupb commented Sep 7, 2020

Hi,
I’m using pelican 4.5.0 with Python 3.8.5 and Invoke 1.4.1

When I do the command invoke build in my blog folder, I have the following output :
`CRITICAL: argument of type 'NoneType' is not iterable``.

I tried to install a theme named Flex, so I added the following line in my pelicanconf.py file :
THEME = "/Users/nicolas/pCloud Sync/Blog/pelican-themes/Flex"

If I remove the line, the command invoke build runs correctly.

Netlify output is :

8:27:17 PM: $ invoke build
8:27:17 PM: CRITICAL: Could not find the theme /Users/nicolas/pCloud Sync/Blog/pelican-themes/Flex
8:27:17 PM: ​
8:27:17 PM: ┌─────────────────────────────┐
8:27:17 PM: │   "build.command" failed    │
8:27:17 PM: └─────────────────────────────┘
8:27:17 PM: ​
8:27:17 PM:   Error message
8:27:17 PM:   Command failed with exit code 1: invoke build
8:27:17 PM: ​
8:27:17 PM:   Error location
8:27:17 PM:   In Build command from Netlify app:
8:27:17 PM:   invoke build
8:27:17 PM: ​
8:27:17 PM:   Resolved config
8:27:17 PM:   build:
8:27:17 PM:     command: invoke build
8:27:17 PM:     commandOrigin: ui
8:27:17 PM:     publish: /opt/build/repo/output

Also, the Pelican 4.5.0 documentation differs from the getpelican/pelican-themes git page (or I misunderstand something :) ). So I also tried using the pelican-themes command. It runs without any issue, and the pelican-themes -l shows my theme in the output. I guess I still have to put the THEME path in the pelicanconf.py file ? However, the invoke output is still the same.

Does anyone have an idea about the source of the error ?
Thanks

@nidupb nidupb changed the title Critical NoneType error with pelican when installing theme Critical NoneType error with pelican 4.5.0 when installing Flex theme Sep 7, 2020
@avaris
Copy link
Member

avaris commented Sep 8, 2020

Related: getpelican/pelican#2797

Workaround in the mean time, define PLUGINS in pelicanconf.

  • If you don't use plugins, PLUGINS = [].
  • If you use the newer auto-detected plugins, it should be an explicit list of those plugins: PLUGINS = ['pelican.plugins.foo', 'pelican.plugins.bar', ...]

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

No branches or pull requests

2 participants