The restriction on backdating is irrelevant -- the "problem" is the way journals and communities sort entries. In particular, even if backdating were possible in communities, the entry still wouldn't stay at the top of the page.
Without getting too technical: Personal journals sort entries by the date given in the entry. The theory is that most of the time, you're going to write in chronological order. So a future-dated entry will always show up at the top, because that's the most recent according to entry dates. The backdate option evolved, for various reasons that I won't get into, as a "yes I know this entry is being posted out of order" flag, because otherwise LJ complains that you're posting out of order. Community journals, OTOH, sort entries by the server date/time when they were posted. This happens because multiple people are going to be posting to communities, and they may be living in different time zones. If someone posts at 2:30pm EST, and five minutes later someone posts at 11:35pm PST, the second post is going to appear above the first one because, even though it has an earlier time, it was posted later. (The same logic is used for friends pages, ftr: in both cases, you don't want to miss seeing an entry just because it has an earlier timestamp.) Because there isn't the same restriction on chronological order, you don't need to flag any entries with "backdate" -- but also, future-dating a post doesn't keep it at the top. So it isn't *quite* as simple as "remove the 'no backdate in comms' line of code". *wry grin* If there is some sort of "this post is sticky" flag, which I'd assume could be used in personal journals (getting around the future-dating thing) as well as communities, that would work; but backdating a community entry wouldn't do anything for keeping it at the top. -Isabeau (who knows waaaaaaay too much about how LJ used to work :) ) Lee Ann Rucker wrote: > The restriction on back-dating comm entries is one line in the code. > I've seen it! > > Maybe it could be something only maintainers could do? > > On Jan 23, 2009, at 5:21 PM, Sophie wrote: > >> On 1/23/09, Denise Paolucci <[email protected]> wrote: >>> Yes, S2 styles already allow this, and we hope to alter all of our S2 >>> styles so that they support the feature. >> The trouble is, an S2 "sticky post" isn't really a post. People can't >> comment on it, you can't link people to it when they're not following >> the rules, and you can't add it to the memories of a community. And on >> my personal journal at least, I have a (real) sticky post that shows >> up only for friends; while it would be possible to do this in S2, it's >> not something that any current style offers. >> >> However, for obvious reasons, not everybody should be able to make >> sticky posts in a community, either. It would need to be restricted or >> restrictable. >> >> - Sophie. _______________________________________________ dw-discuss mailing list [email protected] http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss
