tags are only processed in posts, not in pages #1014

Closed
damiencourousse opened this Issue Jan 29, 2014 · 6 comments

3 participants

@damiencourousse

hello !

I am a new user of Nikola v6.2.

I cannot have tags generated for pages (aka stories), but the tags are correctly processed for posts.
How to configure the build so that tags are not only searched in posts ?

For example with this configuration :
(nikola init --demo)

POSTS = (
    ("posts/*.rst", "posts", "post.tmpl"),
    ("posts/*.txt", "posts", "post.tmpl"),
)
PAGES = (
    ("stories/*.rst", "stories", "story.tmpl"),
    ("stories/*.txt", "stories", "story.tmpl"),
)

NAVIGATION_LINKS = {
    DEFAULT_LANG: (
        ('/stories/news.html', 'News'),
        ('/categories/index.html', 'Tags'),
        ('/rss.xml', 'RSS'),
    ),
}

The generated file categories/index.html does only show the tags contained in the posts, but not in the pages.

Is it a problem of configuration, or a bug ?

regards,
Damien

@Kwpolska
Nikola, a static site generator member

I personally would call it an user error, a feature, expected behavior — as tags for pages seem kinda nonsense, at least in my opinion. @ralsina, what’s yours?

@ralsina
Nikola, a static site generator member

Well, it's something that is not in the "of course it should work that way" category.

We are allowing tags in pages, and treating them differently from tags in posts. So, we should have a discussion about how this works best, perhaps comparing with other similar tools.

@damiencourousse
@ralsina
Nikola, a static site generator member

@damiencourousse well, good news and bad news ;-)

Bad news: right now, you can't do what you want.

Good news: we are discussing whether doing that is a good idea or not, and if yes, how to do it.

@ralsina ralsina modified the milestone: v6.5.0, v6.4.0 Feb 26, 2014
@ralsina ralsina modified the milestone: v7.0.0, v6.5.0 Mar 22, 2014
@Kwpolska Kwpolska modified the milestone: v7.1.0, v7.0.0 May 16, 2014
@Kwpolska
Nikola, a static site generator member

How is this? Should we (a) reject this, because integrating this can be problematic? (also, nobody else does this); or (b) continue with this?

@Kwpolska Kwpolska modified the milestone: v7.2.0, v7.3.0 Nov 2, 2014
@ralsina
Nikola, a static site generator member

I say a).

@ralsina ralsina closed this Jan 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment