Forums / General / Can't import ez4.0.1 package to ez4.1.x

Can't import ez4.0.1 package to ez4.1.x

Previous topic

General

Next topic

Author	Message
Felix Woldt	Wednesday 22 July 2009 4:12:12 am Hi all, today i try to import a simple contentclass package <b>my-classes-1.0_1.ezpkg</b> into ez4.1.x. But it failed! <i>"The package name my-classes is invalid, cannot import the package"</i> What i did wrong? I created the package with an ez4.0.1 installation and i used the packagename ez automatically had created. After some debugging I found out that ez 4.1.x has a new nameconvention regarding packagenames. In ez4.1.x the packagename can not include a '-' in package names and all characters has to be downcase! You can use all characters which you can use for class_identifiers. The solution is. If you want to export classes from an ez version < 4.1.x into ez4.1.x you must set the packagename to e.g. <b>my_classes</b> not ( 'my-classes' or MyClasses ). <b>Conclusion for export ez4.0.1 package into ez4.1.x:</b> Use underlines '_' instead of '-' when createing packages in ez4.0.1 http://www.jac-systeme.de - Developers united in eZ Publish: http://www.cjw-network.com CJW Newsletter 1.0.0 released: http://projects.ez.no/cjw_newsletter
Heath	Wednesday 22 July 2009 4:19:06 am Great Tip Felix Thanks, Heath Brookins Consulting \| http://brookinsconsulting.com/ Certified \| http://auth.ez.no/certification/verify/380350 Solutions \| http://projects.ez.no/users/community/brookins_consulting eZpedia community documentation project \| http://ezpedia.org
Russell Michell	Thursday 13 May 2010 3:26:05 pm Thank you also Felix! Possibly the most useful tip I have ever had the privilage to use! Just to clarify, becuase it took me an hour or so of trial and error even using this technique: It's not just the exported filename as I thought you meant The top-level/parent node you wish to export from ez v4.0.x needs to be renamed via the admin GUI in lowercase and without hyphens before performing an export Once the export is complete, hyphens in the filename itself that eZ puts in there for the version no. work A-OK. As you may have read elsewhere, exporting the content as 'Main Node Only' is a red-herring. It made no difference to my export. Scripts you might find helpful are: ezpublish/ezpm.php to import large packages from the command-line ezpublish/bin/php ezsubtreecopy.php - ideal when you wish to export some 'live' content, but need to rename it as lowercase and without hyphens before exporting - copy the subtree, rename it accordingly, then export. Thanks again Felix :-) Russell Russell Michell, Wellington, New Zealand. We're building! http://www.theruss.com/blog/ I'm on Twitter: http://twitter.com/therussdotcom Believe nothing, consider everything.

Author

Message

Felix Woldt

Wednesday 22 July 2009 4:12:12 am

Hi all,

today i try to import a simple contentclass package my-classes-1.0_1.ezpkg into ez4.1.x.

But it failed!

"The package name my-classes is invalid, cannot import the package"

What i did wrong?
I created the package with an ez4.0.1 installation and i used the packagename ez automatically had created.

After some debugging I found out that ez 4.1.x has a new nameconvention regarding packagenames.

In ez4.1.x the packagename can not include a '-' in package names and all characters has to be downcase! You can use all characters which you can use for class_identifiers.

The solution is. If you want to export classes from an ez version < 4.1.x into ez4.1.x you must set the packagename to e.g. my_classes not ( 'my-classes' or MyClasses ).

Conclusion for export ez4.0.1 package into ez4.1.x:

Use underlines '_' instead of '-' when createing packages in ez4.0.1

http://www.jac-systeme.de - Developers united in eZ Publish: http://www.cjw-network.com

CJW Newsletter 1.0.0 released: http://projects.ez.no/cjw_newsletter

Heath

Wednesday 22 July 2009 4:19:06 am

Great Tip Felix

Thanks,
Heath

Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org

Russell Michell

Thursday 13 May 2010 3:26:05 pm

Thank you also Felix!

Possibly the most useful tip I have ever had the privilage to use!

Just to clarify, becuase it took me an hour or so of trial and error even using this technique:

It's not just the exported filename as I thought you meant
The top-level/parent node you wish to export from ez v4.0.x needs to be renamed via the admin GUI in lowercase and without hyphens before performing an export
Once the export is complete, hyphens in the filename itself that eZ puts in there for the version no. work A-OK.
As you may have read elsewhere, exporting the content as 'Main Node Only' is a red-herring. It made no difference to my export.

Scripts you might find helpful are:

ezpublish/ezpm.php to import large packages from the command-line
ezpublish/bin/php ezsubtreecopy.php - ideal when you wish to export some 'live' content, but need to rename it as lowercase and without hyphens before exporting - copy the subtree, rename it accordingly, then export.

Thanks again Felix :-)
Russell

Russell Michell, Wellington, New Zealand.
We're building! http://www.theruss.com/blog/
I'm on Twitter: http://twitter.com/therussdotcom

Believe nothing, consider everything.