XWiki Platform

Allow recurring blog post titles

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 1.9
  • Fix Version/s: None
  • Component/s: Blog
  • Labels:
    None
  • Environment:
    Win XP, XE 2.0b
  • keywords:
    blog title
  • Similar issues:
    XWIKI-6960The title of blog posts is not updated
    XWIKI-7166Blog posts with question marks in their name appear incorrectly in the blog panels
    XWIKI-6628New blog posts indicate they are unread
    XWIKI-9181Bad redirect when trying to create an blog post with empty title
    XWIKI-4430Allow the Caller for the Blog Feed to specify a different Blog Post Class Name
    XWIKI-8817Users should be forced to write a post title when creating a new blog post
    XWIKI-6340Creating a blog post requires edit rights on Blog.CreatePost
    XWIKI-6357It's not clear where a post comes from in aggregated blogs
    XWIKI-6343Cannot changeXwiki document title ($doc.title) for Blog entry easilly
    XWIKI-3608Set new blog posts to be created in XWiki 2.0 syntax

Description

Identical titles should be allowed for multiple blog posts, e.g. I might want to create several posts with the title "Ideas". Conflicts should be avoided by automatically prefixing each post with the date.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Sergiu Dumitriu added a comment -

I'd like to close this as "won't fix", because:

  • An article has both a wiki document name and a blog post title, which are independent. What you specify in the "create post" form is the document name, which must be unique. You can change the post title afterwards. So, this is not really a blocker bug, but a nice-to-have feature that can help the users.
  • I'd rather keep the default blog names clear, without any dates in them. This is a personal preference.
  • I don't think that two blog posts with the exact same title should be created. Names should be unique, so that users don't get confused. They might not notice the date, so they will easily assume that the article they visited last week was rewritten, and not that this is a brand new article on the same topic.

I would agree with a different behavior: when the user tries to create a blog post with a title that's already taken, the software informs the user about it, and offers to create a different post with the same visible title, but with a postfixed document name (with a _2 at the end, then _3, and so on).

WDYT?

Show
Sergiu Dumitriu added a comment - I'd like to close this as "won't fix", because: An article has both a wiki document name and a blog post title, which are independent. What you specify in the "create post" form is the document name, which must be unique. You can change the post title afterwards. So, this is not really a blocker bug, but a nice-to-have feature that can help the users. I'd rather keep the default blog names clear, without any dates in them. This is a personal preference. I don't think that two blog posts with the exact same title should be created. Names should be unique, so that users don't get confused. They might not notice the date, so they will easily assume that the article they visited last week was rewritten, and not that this is a brand new article on the same topic. I would agree with a different behavior: when the user tries to create a blog post with a title that's already taken, the software informs the user about it, and offers to create a different post with the same visible title, but with a postfixed document name (with a _2 at the end, then _3, and so on). WDYT?
Hide
Permalink
Philipp Roessler added a comment - - edited

Okay, you've got a point here: I guess most people wouldn't like to remember dates in document names (i.e. URLs).

So I agree with you: postfixed document names are the way to go.

Do you have any timeline when this will happen?

Show
Philipp Roessler added a comment - - edited Okay, you've got a point here: I guess most people wouldn't like to remember dates in document names (i.e. URLs). So I agree with you: postfixed document names are the way to go. Do you have any timeline when this will happen?

People

  • Assignee:
    Unassigned
    Reporter:
    Philipp Roessler
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Date of First Response: