|
Would future-dated entries show up ahead of time, or only be shown to the public on the date that they are set at? Perhaps they are visible to the poster (so that they can remove them if necessary), but invisible to everyone else until the set post date.
My use case for this would have all posting, past, current and future, visible to everyone. As a community calendar, you would want to show future events as well as past events.
I can also understand the concept of items being invisible until the a future date, in which case they should be visible to the person who posted them. But invisible items wouldn't serve for a community calendar. conf-4010 seems to me to be a more comprehensive approach to this issue, perhaps this issue could be remarked as related to conf-4010
What is the status of this request? I recently submitted a duplicate request (
Hi Jeff,
The only solution at the moment is to import the blog posts, then access the database you are using directly and change the posting dates. Jeremy Would I need to take any special steps such as rebuilding Lucene indexes / restarting Confluence to make sure that any cached dates don't get messed up, etc?
If possible, I'd shut down Confluence while changing the dates, so you don't run into any problems with concurrent access. As far as the indexing goes, it shouldn't really be a problem, but it wouldn't hurt to do so.
I strongly vote for this feature. We are moving old blog content into a new Confluence blog and it is frustrating that I really can't do this because of the dates. Another related issue (I'll report it separately) is to be able to change the author. I need to move across postings from a number of users (some of whom have now left the company) and there's no way to correct the blog entry to have the correct author.
Does anyone have any suggestions? I'd really like to see some progress made in this area. As previously suggested having CONF-4010 is another possibility but then we'd need to be able to edit date and author on regular pages. One more thing. Can this be upgraded to major, because it seems more than a minor bug. Without an official workaround this really leaves us stuck when trying to get old content into Confluence.
Last comment for today, I promise. I've created CONF-5927 which requests the ability to be able to create content on behalf of another user. I think these two things together (being able to set the author and date of content before posting it) would be extremely useful for a certain class of user.
I completely agree with the use case of changing dates on news posts. Not only would we like to postdate meeting agendas, but we'd also like to schedule announcements on a specific date ("server XYZ will be down this weekend").
Having an an-place "EDIT" link, just like the Labels field above it, would serve this purpose wonderfully. This solution presents a much smaller and more direct solution than any alternatives presented here. And judging by the 28 votes garnered thus far, people want it. This is one of the most voted for features and it is reported almost two years ago! This is a show stopper for me. A step-by-step work-around by maniplulating the database by hand would help a bit.
Can we have some kind of statement when (if) this will be resolved/worked on any time soon? Agreed. This issue also keeps getting duplicated - another sign of its importance.
It's really annoying that this feature is missing. Sometimes you forget to make blog entries at the day it should be done. Then it would be great to create it the next day and backdate it to the day where it belongs (i.e. the "thing" happened). So I vote for this to be fixed, too. I also wouldn't consider this issue being only "minor".
There is kind of a workaround available now if you are using the Blogging RPC plugin. The latest (beta) version allows you to specify the publish date on a blog post if you are using the meta-weblog API. (Or to update the publish date for blog posts that are already there.)
http://confluence.atlassian.com/display/CONFEXT/Blogging+RPC+Plugin It would be nice if this functionality made it into the proper web interface though. I am proposing Confluence at a client's as it solves two of their problems, the latter of which is as a decent Wiki. However, I am told I need to understand that the client's primary goal is decent blogging capability.
This feature is NOT a minor priority in their eyes. It's core functionality as important as being able to give a blog post a title. With 47 votes, please prioritize it. If you need someone to code it please contact me. We're getting the same feedback from clients and this issue pops up on the conf-user mailing list regularly. For Confluence adoption, the ability to backdate blogs is extremely important to new clients. There are other factors that force them to use Confluence, but they really don't like having all their old blog posts appearing on the same day when they move them in to Confluence.
Yeah I want this too, it's obviously an important feature. What can the problem be with getting this prioritised??
Hi everyone,
After considering everyone's input on this issue we have implemented the ability to back date a news post on creation, either via the web interface or the RPC interface. We've disallowed setting dates in the future because we felt that it would take more work to implement in a logical manner and it dones't seem to be nearly as important as the post dating feature. If you really want a future dating capability in Confluence please open another issue. Chris |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Resolved
Minor
Backdate blog entries
The "meetings" page would be known as the place to look to see upcomming meetings, and minutes, etc. from past meetings.
Members of the team can post a tentative agenda (and/or locations, etc.) on a future date, and the community can comment, edit the agenda (if given permission), etc. When the meeting happens minutes can be posted.
Seems to me like it leverages the blog feature to provide a significant additional capability.