Hi Andreas, As I indicated in a previous email, I inherited a system that was primarily configured through the ZMI. Recognizing that application development through the ZMI imposes certain limitations (such as rudimentary version control), I managed the development in a manner that you suggested in your initial response. Given these facts, how do you suggest I improve my approach? Based on the two suggestions that you generously offered, I am still puzzled as to how this problem can be solved. Clearly, transferring the Data.fs from the test server to the production server is insufficient given the user data mismatch. Therefore, it would seem that my only option, given the circumstances would be to manually replicate the configuration in the production server. However, my better judgment leads me to think that this isn't sensible. Is there no alternative? Regards Joel
-----Original Message----- From: Andreas Jung [mailto:lists@andreas-jung.com] Sent: Tuesday, June 14, 2005 1:05 AM To: jlegris; 'Andreas Jung'; zope@zope.org Subject: RE: [Zope] Transferring Zope Settings
--On 14. Juni 2005 00:46:51 -0700 jlegris <joel.legris@egadss.org> wrote:
Hi Andreas,
In this case, copying the Data.fs file isn't a feasible solution because there is plenty of user content that would get over-written. The test instance of course doesn't contain this data. I am pretty new to Zope, so it's possible that I don't fully understand the development process when using this tool, but I would find it surprising if there isn't a way to administer updates without affecting content or manually replicating configuration settings. Is this an inherent weakness of Zope?
Basicially a weakness of your approach using Zope. Zope does distinguish between user content, customizations or whatever...everything is an object.
-aj