-
Notifications
You must be signed in to change notification settings - Fork 87
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
Changes to my content files do not reflect on the rendered website #244
Comments
You're using the Judging from the output however, it seems that it just skips those plugins if they fail to load, so it should still generate something from the input Generally, there's no hidden magic done by m.css anywhere, it's all just plain Pelican with some theming on top. So if there's something strange going on, it's likely Pelican being misconfigured. |
It's working fine now. Thanks, @mosra! I think it was wrong indentation in some of the reST files that was causing the problem (beginner's error. lol). Because of those errors, Pelican wasn't parsing the files, so the changes I was making wasn't being updated. I added a new article file with fresh content, formatted with some m.css special directives. It rendered fine. So I deleted the content of the old articles and carefully added them back. They rendered perfectly, too. Everything is fine now. Thank you so much. |
Ah, yes, the error handling / reporting is a bit strange in Pelican, a single error causing everything to stop. Gotta get used to it, I guess :) |
I'm experiencing two issues I suspect are related to the m.css plugins. This is similar to the closed issue #181
note-dim::
,note-info::
,note-primary::
,gh
, etc) in my articles, they also don't reflect on the website.In my settings file, CACHE_CONTENT and LOAD_CONTENT_CACHE are both set to False. And the m.css plugins folder is correctly referenced there too:
The following is the Terminal output when I run
pelican -Dlr
:Notice the line last line there that says 'Unable to find
/posts/why-study-dsa.rst
, skipping url replacement.' Pelican is referencing an old folder nameposts/
, which I changed toarticles/
like four days ago. I've made several significant changes to the content of the articles, but it doesn't reflect on the website.I believe all these issues are related.
Deleting the output folder and regenerating the content doesn't fix it. The fix suggested by @lpirl on issue #181 also didn't work for me. Please help!
The text was updated successfully, but these errors were encountered: