I get the following error message:

"Import error: WARNING: No father row found for ...."

I actually think I understand the message, but I wonder why it all works in 2.0. It looks like the father is after the child, but it all works in links 2.0.

I had a similar problem, except I imported from 2.0, to SQL 1.13, then to beta2.01.

Probably what has happened is somehow one of your main categories has moved somewhere else in the database, and all the sub-categories for that main category are now orphans, probably located under the root now. Do a search for the father categroy to see where it is located. I ended up having to move around a whole bunch of categories to get things working properly again. This is not bad if you only have a dozen orphans, but it would be a big task if you have hundreds. =P



Rob Bartlett
AAA Internet Publishing, Inc.
http://www.AAAInternet.com

The next beta will have an option to automatically insert missing category gaps.

Cheers,

Alex

--
Gossamer Threads Inc.