Alex,

A few things before I forget:

1) same thing happened with the Import.pl as last time. Because some 'required' (ie: '1') fields in the _NEW_ .def file don't exist in the old database, the database had a lot of import errors. This can be fixed by changing the '1' to '0' in the Links.def and Category.def files in the DEFS directory...
They have to be re-set later, but at least the database imports.

2) The instructions should also say to set the DEFS directory to 777 not just Backup

3) Clarify the fact that you _MUST_ manually add any fields you have added to your database to the SQL.pl file, or you will not import your directory correctly (Why can't the SQL.pl read the old def file and add any extra fields? It wouldn't be perfect in all cases, but it would make most people's lives easier) -- Also, changing any spaces in field names to '_' at this time makes it easier.

There was one other thing in the install, and it's escaping me at the moment...

But this is a great step forward!

Alex,

On the import issue ...

Would it be easier to modify the links.db file, by preprocessing to add missing fields, than trying to import it all at once?

Hello!

I fail to beleive that one uses the Import.pl just like this.
This is just a basic concept of importing database. Everyone
needs to customize their database + scripts. What I have done
is I have copied this file into db_config.pl and there it has custom
modifications for that database. Simply run it and it does everything.
Extremely good for testing and playing. So one has to test on a test database
ofcourse.

In this case you always need to have your custom file ready to prepare
your database new for any reason.

By the way, hey, where did you get 1.1b2?

------------------
rajani

Remembered what it was ---

The link checking dies for internal links -- ie: links that start with a "/" not http://