eZPackage & Content class versionning

eZPackage & Content class versionning

Thursday 07 February 2008 2:14:24 am - 1 reply

Author Message

JT -

Wednesday 09 December 2009 2:05:28 am

Hi!

I have problems related to the package management too:

I can export a package easily but if I try to update the same package that doesn't work. I have to delete the old one before I can export a new one or I have to rename it. IMHO that's not sensible. There is a version counter one can edit and that means the package should be replaced by the new one.
If I have to delete it the comment "- Creation of package." is rather futile because one can only create new packages. Isn't it?

I would expect an "Update"-Button to rebuild the exported package with exactly the same parameters except the version and an additional comment.

And on the other side of the process:

I totally agree with Jerôme; one should be able to import an updated package

  • that respects the existing package (and updates it instead of having to delete and install manually)
  • that respects existing content (i.e. it is not deleted but kept; or kept and updated)

Is this issue going to be solved (the message by Jerôme is almost 2 years old...) or is it just balderdash?

Thx in advance,

JT

You must be logged in to post messages in this topic!

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.