Closed Bug 505476 Opened 16 years ago Closed 15 years ago

Archive old testday/bugday posts on QMO

Categories

(quality.mozilla.org :: Website, defect, P3)

Product:
quality.mozilla.org
Component:
Website
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: tchung, Unassigned)

Details

It would be great to archive the older testday and bugday posts someplace. This way it would not show up on people's calender, yet it can be easily accessed by anyone who wanted to look back to older content for the purpose of recreating a new post or just past reference. This would be better than just deleting it otherwise. Please also make sure archive posts are easily accessible somehow. Thanks!
Severity: normal → minor
OS: Mac OS X → All
Priority: -- → P3
Hardware: x86 → All
should be website i think
Component: Content → Website
QA Contact: content → website
Sounds like it is. So you'd need an "Archive" page/category where you can move events to? What other content types might be archived? Blog, forum topic, etc? (look at list in dropdown menu)
IMO, i think blog and events would be (In reply to comment #2) > Sounds like it is. So you'd need an "Archive" page/category where you can move > events to? > > What other content types might be archived? Blog, forum topic, etc? (look at > list in dropdown menu) IMO, ones that come to my mind that would be useful for future archiving are Projects, blog, Events, Documents. I dont really care too much past forums. But you can make an argument that everything could be obsolete one day (eg. tools, docs), but always good to refer back to for whatever reason.
Okay, the behavior of this needs to be thought about more. What happens to posts once in archive? E.g. you mentioned events are taken off the calendar. What about the others? I.e. what happens when you archive a blog post, to the blog page and any other pages that display that blog post (except the URL to the post itself)?
This bug is being moved to a resolved state of invalid due to one of the following reasons: - we're moving to wordpress and so all drupal cruft is not going to be fixed - the feature is not supported on the new qmo, at least for this release.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
This bug is being moved to a resolved state of invalid due to one of the following reasons: - we're moving to wordpress and so all drupal cruft is not going to be fixed - the feature is not supported on the new qmo, at least for this release.
You need to log in before you can comment on or make changes to this bug.