Back to slash1toslash2.2 hell
Moving from slash 1.n to 2.2 i have 2 strange problems when running slash1toslash2.2
First i get 1003 lines of (after “Processing users_index” message):
Use of uninitialized value in split at ./slash1toslash2.2 line 205, line 3.
Use of uninitialized value in split at ./slash1toslash2.2 line 205, line 3....
and so on
and second problem is that i get 1392 lines of (after “Processing moderatorlog” message )
Warning: NULL CID found for '02/05/31/0329257' #5 - record not imported.
Warning: NULL CID found for '02/06/18/1627202' #5 - record not imported....
and so on
I can not figure out what is wrong with those stories.
Really like to get this site updated. Thanx for any help ;)
First i get 1003 lines of (after “Processing users_index” message):
Use of uninitialized value in split at
Use of uninitialized value in split at
and so on
and second problem is that i get 1392 lines of (after “Processing moderatorlog” message )
Warning: NULL CID found for '02/05/31/0329257' #5 - record not imported.
Warning: NULL CID found for '02/06/18/1627202' #5 - record not imported....
and so on
I can not figure out what is wrong with those stories.
Really like to get this site updated. Thanx for any help
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.



Same Probleme Here (Score:1)
I have the same error messages and noticed that for some of the stories mentioned I don't have entries in the comments table (that's what the error message is about - no matching comment found), but for some there exists the comment with exactly that CID.
I haven't had time yet to find out what happens there.
--
symlink.ch [symlink.ch]: YAGSS - yet another German slash si
bug? (Score:1)
look for:
$comments{$data->{sid}}->{$data->{cid}} = $new_cid
if $data->{date} ge $display;
and remove "if $data->{date} ge $display;" line so it looks like this:
$comments{$data->{sid}}->{$data->{cid}} = $new_cid;
look for th
line 168 of 1884 in slash1toslash2.2 (Score:1)
$data->{flags} = 'delete' if $ws == 5 || $ws == 10;
as i understand this, all the archived stories in my old slash 1.9 db are marked as "delete".
after you start your slash, the freshenup.pl will delete all of those stories.
I just updated (in new slash db) the 'writestatus' field in my 'stories' table before i started the salashd.
Replaced the 'delete' with 'ok'.
Most of them will be marked 'archived' after you start slashd.