Import gives errors. Need help.

Friday 12 September 2003 1:48:08 pm

Hello everyone, especially Wenyue ;)

I'm trying again the import scripts to import data from 2.2 to 3.1 (or later 3.2).
I tried "importuser.php" first, but the problem is the same.
I did a cleandatabase with kernel_clean.sql. All necessary object classes and class attributes are in the (clean) database.

Debugging show me one warning and then fails with an error:
Warning: Invalid argument supplied for foreach() in [docroot]/kernel/classes/ezpersistentobject.php on line 552.
(caused by $contentObject =& $class->instantiate( $userID, 1 ); )

The fatal error is this:
Fatal error: Call to a member function on a non-object in [docroot]/importuser.php on line 125.
This is caused by $contentObjectAttributes[0]->setAttribute( 'data_text', $name );

Looks a lot, like the preceeding line ($contentObjectAttributes =& $version->contentObjectAttributes(); ) does not return the expected array of object attributes.

Why?
How can I debug this?
(The data from the ez2-tables in the DB are looking fine.)

What DB entries are needed for the import scripts to work?

I really need some help here, because I think, it's a silly small bug, but I cannot figure it out.

Marco
http://www.hyperroad-design.com

Sunday 28 September 2003 9:00:16 am

I solved the other import error now:
When you get an error complaining about something like "not beeing able to call a method of a non-existing object", you might have a setup, where the content is non-english.
As the import-scripts to not evaluate the override files, it read the content locale from the original site.ini, where it is "eng-DB". When your Database is mono-linugal (ie. German-only), the import fails.
Just edit the original settings/site.ini and change "ContentObjectLocale" to your locale (ie ger-DE).
Do NOT change the "Locale", but the "ContentObjectLocale"!

Marco
http://www.hyperroad-design.com

Saturday 07 February 2004 2:37:37 am

Hi,
in 3.3, ezPublish uses a new image system. The import scripts were not written for this new image system, and i think, this results in the errors, that you mention.
ez 3.2 uses the old image system (just as 3.0 and 3.1)
So, i suggest, that you installed 3.2-4 (the latest 3.2 release) and import your data from 2.2.9 to 3.2-4.
This should work. Check, if your images are okay in 3.2
Then, make a backup of everything ;) and update from 3.2-4 to 3.3-3
Hope, this helps.

Marco
http://www.hyperroad-design.com