Deniz Turgut
Deniz Turgut
Well, you **can** still use them if you add the subfolder to `PLUGIN_PATHS`: ```python PLUGIN_PATHS = ['pelican-plugins', 'pelican-plugins/pelicanfly'] PLUGINS = ['pelicanfly'] ``` Not ideal, but also not impossible :). But,...
Will it be OK for all submodules? Feels like it will take away some control from the author(s). Also, it's easy to update all submodules locally: ``` git submodule update...
I didn't mean "let's not update them... ever..." :). What I was trying to say is that this depends on (all) submodule authors. What's true for a submodule might not...
I am OK with an opt-in solution, but the original message implied an all-in approach (at least, I got that impression). >We have no way of knowing the comfort level...
No. Those settings are for article collections. Even if you could, `pelican` wouldn't have any information about the photos *inside* your page to paginate. Sounds like this is a job...
Can you add it to the readme with a short description?
It is working for me know. Also for the record, as far as I know, that site is a user project and is not handled by `pelican` maintainers. So, not...
Checked again. still working. I think the owner is here: https://github.com/m-allanson/pelican-themes
Sure, `ERROR` sounds a bit ominous but based on the code it should just skip that `img` tag and leave it as is. Isn't the output correct?
I can't reproduce it. If page is skipped it's probably for another reason and I need an example with the issue to investigate. ```bash $ cat content/article.rst Test #### :date:...