Posted by davegan on July 17, 2007 at 11:24pm
I'm creating a website for a magazine, who are going to publish some of their archive of content.
We're currently importing / entering much of it into drupal. However, we aren't publishing it right away.
What we're going to do is publish the content over time. However, this poses a bit of an issue, as in taxonomy lists the content won't be sorted by date published. Using Views, I could sort by date edited, but I don't want to push something to the top of lists for a simple typo correction.
Any ideas?
Comments
How about this...
You might find some information here that could be useful...
Moshe & friends redevelopment of the New York Observer website, lots of useful tips in the article.
Web Development in Nottingham, UK by Kineta Systems / Follow me on Twitter! @NikLP
Thanks for the tip
That's an article I've definitely peered over - and used their solution to manage my front page. Doesn't have quite what I need in this situation, but thank anyhow.
How about...
Can you try adding a Date field and then using the mech as described in the NYO article? That way, you can scrap the default taxonomy lists and use views taxonomy overridden lists instead; then you can order by your Date field (publication date).
Any good?
Web Development in Nottingham, UK by Kineta Systems / Follow me on Twitter! @NikLP
_
I would be curious to know if you ever came upon a non-CCK Date field solution to this issue, such as a module that achieves this?
I seems as a no-brainer to me to have a 'published' datestamp on a node that is accessible via Views, and while the work involved should be fairly straight forward, I'm not a fan of re-inventing the wheel.
Cheers,
Deciphered.