Forums / Developer / Packages - problem with modifier/creator/versions (3.9.3)

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Packages - problem with modifier/creator/versions (3.9.3)

Previous topic

Developer

Next topic

Author	Message
Ross Kimbarovsky	Friday 11 April 2008 7:37:08 am A few days ago, we needed to migrate data from one install to another and created packages to do so. User class and user profile class migrated mostly OK, but we ran into an issue migrating user portfolios (we allow users to submit images as part of their portfolio, and we display those images on our site). Regardless of what options we pick for creating a package, the package does not migrate versions and does not maintain author information. When installing the package, all author information is replaced with the name of the person (admin) that is installing the package and all version information is lost. We are using eZ 3.9.3, and using the native package functionality. We wonder if anyone else has seen this problem and what you have done to solve it. What other options do we have to migrate such data? Thanks in advance. Ross

Author

Message

Ross Kimbarovsky

Friday 11 April 2008 7:37:08 am

A few days ago, we needed to migrate data from one install to another and created packages to do so. User class and user profile class migrated mostly OK, but we ran into an issue migrating user portfolios (we allow users to submit images as part of their portfolio, and we display those images on our site). Regardless of what options we pick for creating a package, the package does not migrate versions and does not maintain author information. When installing the package, all author information is replaced with the name of the person (admin) that is installing the package and all version information is lost. We are using eZ 3.9.3, and using the native package functionality.

We wonder if anyone else has seen this problem and what you have done to solve it. What other options do we have to migrate such data?

Thanks in advance.

Ross