Here is the sql statement I used:

insert into nuke_news_stories (state,story_id,summary,ext_text,title, views,create_date,author_id,topic_id)
select pn_state,pn_sid,pn_hometext,pn_bodytext,pn_title,pn_counter,pn_time,pn_uid,pn_topic from nuke_stories, nuke_users
where nuke_users.pn_uname=nuke_stories.pn_informant;

I have a little problem with the news topics:

I fed the nuke_news_topic by hand (I mean not via nukes interface) and the topics are not counted in the news admin page (but they appear in the Topics page).

The new archived/queued/published state for the news is nice.

Would it be possible to add an access to the archived (previous) stories?
(or maybe the notion archived is not good for me because I would like to allow my users to search/browse all the available stories, but restricting the current stories displayed to a minimum (else it takes too much time to load and to

Would it be possible to have a block with most visited stories?

Problem fixed.

The state was 0 (default value).

I set it to 1 and now the topics are counted fine.

It would be nice to put a default value that is either published or archived.


--Daniel

It does make sense.

I am thinking about creating a deadline countdown module in July to train myself to cmp.
(A module that displays a list of days to go before some conference deadlines).