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

"empty slug for" should be "empty title for" #196

Closed
kylef opened this issue Dec 16, 2011 · 1 comment
Closed

"empty slug for" should be "empty title for" #196

kylef opened this issue Dec 16, 2011 · 1 comment

Comments

@kylef
Copy link
Member

kylef commented Dec 16, 2011

WARNING: empty slug for 'content/pages/about.rst

This happens when you leave a title out of the page. Since the code makes a slug from the title if there isn't already one.

@almet
Copy link
Member

almet commented Mar 3, 2012

Well, the problem is that pelican doesn't find a slug, the fact that there isn't any title is not really a problem, since it can be omitted and you can refer to articles / pages just using their slugs.

However, the slug is mandatory, thus the error message. Maybe can we do something a bit more clearer for the end user, adding: "You can resolve this by adding a title or a slug to your content".

Would it be sufficient?

@almet almet closed this as completed in ebe5c0b Apr 1, 2012
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