Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
New Extension: Chronological
Chronological
Forces the discussion grid to sort in a blog-like reverse chronological order.
Why? In my case, its better that way because of the timely subject matter.
Other cases?
Forces the discussion grid to sort in a blog-like reverse chronological order.
Why? In my case, its better that way because of the timely subject matter.
Other cases?
certain topics tend to float near the top forever, because people will be willing to argue about H1B visas, or what's wrong with Computer Science in college, until the end of the universe. Every day 100 new people arrive in the forum for the first time, and they start at the top of the list, and they dive into that topic with gusto.From: Joel on Software
The way I do it has two advantages. One, topics rapidly go away, so conversation remains relatively interesting. Eventually people have to just stop arguing about a given point.
Two, the order of topics on the home page is stable, so it's easier to find a topic again that you were interested in because it stays in the same place relative to its neighbors.
0
This discussion has been closed.
Comments
We use it to keep weekly sets of baby pictures from getting mixed up. Bumping was rather confusing for family not familiar with forums. (Why is week 7 above week 13 when week 14 is at the top???)
On second thought, maybe it won't be that bad. Could also set it as a per-user prefrence. Hmm, 'personal sink' was mentioned a bit back.
Will have to tinker a bit.
ADM: Discussion overview should be able to do that with some small modifications.
Here is some pseudocode assuming that discussion overview loops through the categories:
// some of discussion overview's code For each category in categories { if (category->Name == 'News') { // set the database definitions like they are in Chronological } else { // set the database table definitions back to normal } // rest of discussion overview code continues... }I will post some code to do that later today...