We use revisions for different revisions of a certain document, which can be changed by several users. However, when user1 creates a story, and user2 creates a new revision of that story, both will be displayed as authored by user2. However, we would expect it to show the original revision with the original author information (user1), and not the author of the newer revision (user2)
In addition, both articles will get the publication time of the newer revision assigned when displaying the story. This is confusing, especially as there can be months (or even years) between revisions. We would expect that on display of the original revision, it displays the publication date entered by user1 for the original revision, and when displaying the newer revision, it should display the publication date entered by user2 when adding this revision.

In addition, as we are moving old content from a static html site to a Drupal-6 base site, including revisions of articles, it always assigns the actual revision time to a revision, not the manually entered publication date, when viewing the revision overview.
Again, this might not be a problem for a completely new site, but is a problem when moving legacy content (i.e. we have revision1 published in 1998, revision2 in 2005).

Comments

michellezeedru’s picture

michellezeedru commented

This is a problem for me as well. Would love to know if anyone has a solution.

jayburgh’s picture

jayburgh commented

Major problem for me as well. I have a prolific author on a site who was using full URL refs from images and existing content (instead of using relative refs) to make hrefs on new content. The site moved, and now all that content had refs pointing to the old site. When I explained the problem, he bellied up to the bar and started fixing all the old refs. Now all that fixed content looks like it's brand new according to the byline and order on the front page. That sucks.

Status: Active » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.