well I found out and solved one issue with the import scripts. On an other system (Solaris), the import scripts did not work either (ezP 3.2 beta 2), but gave an error about not knowing the function ezi18n.
I could solve this and get the scripts running by inserting one line (in every script).
Insert this line:
include_once( "kernel/common/i18n.php" ); after the other include_once lines.
Unfortunatly, the above mentioned errors still are there on a Suse Linux setup (ezP 3.2 beta 2)
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"!
When I run php -C importimage.php I get the following error message:
PHP Fatal error: Undefined class name 'ezimage' in /var/www/pub3/importimage.php on line 217
<br /> <b>Fatal error</b>: Undefined class name 'ezimage' in <b>/var/www/pub3/importimage.php</b> on line <b>217</b><br />
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.