search

mosra / m.css

A no-nonsense, no-JavaScript CSS framework, site and documentation theme for content-oriented websites
https://mcss.mosra.cz
Other
406 stars 92 forks source link

Unable to find {path to file}, skipping url replacement #243

Closed jegrami closed 4 months ago

jegrami commented 4 months ago

I get the above warning whenever I run Pelican -Dlr. I think this started happening after I created a custom landing page, overriding the default index page, and then added the following config settings:

STATIC_URL = '{path}'
STATIC_PATHS = ['static']

Also, my article page only has the latest article expanded. It doesn't have other older articles listed as summaries under the first expanded post, even though I have the following settings in my pelicancon.py: 

PAGINATED_TEMPLATES = {'archives': True, 'tag': None, 'category': None, 'author': None}

DEFAULT_PAGINATION = 10

I also noticed that the file reference in the warning message isn't correct. It says specifically unable to find 'post/<filename>.rst', skipping url replacement. But the file is actually in articles/ folder, not posts/. I changed the folder name from posts/ to articles/ a few days ago and it was working fine.

On the served pages at localhost, if I click 'show older article', i find the article that pelican said it was 'unable to find' sitting on the next page. But it's not listed as a summary under the first expanded article in the Articles page as it should. It this because of the customized landing page config?

mosra commented 4 months ago

Given that you closed the issue, I assume you found out the root cause, right?

Just for the record, the unable to find message I think comes from links in the .rst files themselves, not from anything in the configuration. So if you get those messages, search in the input files and fix the links to point to the new location instead.