[Zope-Checkins] SVN: Zope/trunk/ Added automatic inline migration for databases created with older Zope versions. The `Versions` screen from the `Control_Panel` is now automatically removed on Zope st
Log message for revision 99286:
Added automatic inline migration for databases created with older Zope
versions. The `Versions` screen from the `Control_Panel` is now automatically
removed on Zope startup.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/App/ApplicationManager.py
U Zope/trunk/src/HelpSys/HelpTopic.py
U Zope/trunk/src/OFS/Application.py
-=-
Modified: Zope/trunk/doc/CHANGES.rst
===
--- Zope/trunk/doc/CHANGES.rst 2009-04-19 16:38:24 UTC (rev 99285)
+++ Zope/trunk/doc/CHANGES.rst 2009-04-19 17:38:06 UTC (rev 99286)
@@ -23,6 +23,10 @@
Restructuring
+
+- Added automatic inline migration for databases created with older Zope
+ versions. The `Versions` screen from the `Control_Panel` is now
+ automatically removed on Zope startup.
+
- Removed more unused code of the versions support feature including the
Globals.VersionNameName constant.
Modified: Zope/trunk/src/App/ApplicationManager.py
===
--- Zope/trunk/src/App/ApplicationManager.py2009-04-19 16:38:24 UTC (rev
99285)
+++ Zope/trunk/src/App/ApplicationManager.py2009-04-19 17:38:06 UTC (rev
99286)
@@ -139,18 +139,6 @@
InitializeClass(DatabaseChooser)
-class VersionManager(Item, Implicit):
-Version management
-
-id='Versions'
-name=title='Version Management'
-meta_type ='Version Management'
-
-InitializeClass(VersionManager)
-
-
-
-
# refcount snapshot info
_v_rcs=None
_v_rst=None
Modified: Zope/trunk/src/HelpSys/HelpTopic.py
===
--- Zope/trunk/src/HelpSys/HelpTopic.py 2009-04-19 16:38:24 UTC (rev 99285)
+++ Zope/trunk/src/HelpSys/HelpTopic.py 2009-04-19 17:38:06 UTC (rev 99286)
@@ -140,6 +140,7 @@
self._v_last_read = mtime
def _check_for_update(self):
+import Globals
if Globals.DevelopmentMode:
try:mtime=os.stat(self.file)[8]
except: mtime=0
Modified: Zope/trunk/src/OFS/Application.py
===
--- Zope/trunk/src/OFS/Application.py 2009-04-19 16:38:24 UTC (rev 99285)
+++ Zope/trunk/src/OFS/Application.py 2009-04-19 17:38:06 UTC (rev 99286)
@@ -289,6 +289,17 @@
cpl._init()
app._setObject('Control_Panel', cpl)
self.commit('Added Control_Panel')
+else:
+# Inline migration of old databases
+cp = app.Control_Panel
+ids = [i['id'] for i in cp._objects]
+if 'Versions' in ids:
+new = []
+for entry in cp._objects:
+if entry['id'] != 'Versions':
+new.append(entry)
+cp._objects = tuple(new)
+self.commit('Removed Control_Panel.Versions')
# b/c: Ensure that a ProductFolder exists.
if not hasattr(aq_base(app.Control_Panel), 'Products'):
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/skel/bin/runzope.bat.in changes so it's easier to move a Zope instance between zope versions.
Log message for revision 67786: changes so it's easier to move a Zope instance between zope versions. Changed: U Zope/trunk/skel/bin/runzope.bat.in -=- Modified: Zope/trunk/skel/bin/runzope.bat.in === --- Zope/trunk/skel/bin/runzope.bat.in 2006-05-01 10:12:03 UTC (rev 67785) +++ Zope/trunk/skel/bin/runzope.bat.in 2006-05-01 11:13:52 UTC (rev 67786) @@ -1,8 +1,8 @@ @set PYTHON=PYTHON @set ZOPE_HOME=ZOPE_HOME @set INSTANCE_HOME=INSTANCE_HOME [EMAIL PROTECTED] SOFTWARE_HOME=SOFTWARE_HOME [EMAIL PROTECTED] CONFIG_FILE=INSTANCE_HOME\etc\zope.conf [EMAIL PROTECTED] SOFTWARE_HOME=%ZOPE_HOME%\lib\python [EMAIL PROTECTED] CONFIG_FILE=%INSTANCE_HOME%\etc\zope.conf @set PYTHONPATH=%SOFTWARE_HOME% @set ZOPE_RUN=%SOFTWARE_HOME%\Zope2\Startup\run.py %PYTHON% %ZOPE_RUN% -C %CONFIG_FILE% %1 %2 %3 %4 %5 %6 %7 ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/skel/bin/runzope.bat.in further changes so it's easier to move an instance between zope versions.
Log message for revision 67788: further changes so it's easier to move an instance between zope versions. Changed: U Zope/trunk/skel/bin/runzope.bat.in -=- Modified: Zope/trunk/skel/bin/runzope.bat.in === --- Zope/trunk/skel/bin/runzope.bat.in 2006-05-01 11:14:30 UTC (rev 67787) +++ Zope/trunk/skel/bin/runzope.bat.in 2006-05-01 11:19:33 UTC (rev 67788) @@ -1,6 +1,6 @@ [EMAIL PROTECTED] PYTHON=PYTHON @set ZOPE_HOME=ZOPE_HOME @set INSTANCE_HOME=INSTANCE_HOME [EMAIL PROTECTED] PYTHON=%ZOPE_HOME%\bin\python.exe @set SOFTWARE_HOME=%ZOPE_HOME%\lib\python @set CONFIG_FILE=%INSTANCE_HOME%\etc\zope.conf @set PYTHONPATH=%SOFTWARE_HOME% ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.9/skel/bin/runzope.bat.in further changes so it's easier to move an instance between zope versions.
Log message for revision 67789: further changes so it's easier to move an instance between zope versions. Changed: U Zope/branches/2.9/skel/bin/runzope.bat.in -=- Modified: Zope/branches/2.9/skel/bin/runzope.bat.in === --- Zope/branches/2.9/skel/bin/runzope.bat.in 2006-05-01 11:19:33 UTC (rev 67788) +++ Zope/branches/2.9/skel/bin/runzope.bat.in 2006-05-01 11:19:56 UTC (rev 67789) @@ -1,6 +1,6 @@ [EMAIL PROTECTED] PYTHON=PYTHON @set ZOPE_HOME=ZOPE_HOME @set INSTANCE_HOME=INSTANCE_HOME [EMAIL PROTECTED] PYTHON=%ZOPE_HOME%\bin\python.exe @set SOFTWARE_HOME=%ZOPE_HOME%\lib\python @set CONFIG_FILE=%INSTANCE_HOME%\etc\zope.conf @set PYTHONPATH=%SOFTWARE_HOME% ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope] Zope Mirror sites running on different zope versions...
Hi Everyone, We have our main zope site running on Zope-2.7.6 and want to create a mirror for that (on our local LAN)... Is it feasible to use Zope-2.8.0b1 (the current stable prerelease) or a higher for the mirror? I mean is it going to cause any compatibility issues when synchronizing the two sites? Would appreciate any quick info on this... --JV ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope Mirror sites running on different zope versions...
--On Freitag, 20. Mai 2005 10:49 Uhr +0530 JV Singh [EMAIL PROTECTED] wrote: Hi Everyone, We have our main zope site running on Zope-2.7.6 and want to create a mirror for that (on our local LAN)... Is it feasible to use Zope-2.8.0b1 (the current stable prerelease) or a higher for the mirror? I mean is it going to cause any compatibility issues when synchronizing the two sites? As a general rule: you should run identical software versions...both on the Zope and the Product side to avoid any trouble. -aj pgps0mkLUPjA7.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Running different Zope versions
Is it possible to run different Zope versions on one machine? I have a Zope 2.6.4 running and a Zope 2.7.3 both on a Windows 2003 server.They use their own python. I runthem on different port numbers configured in the zope.conf file. Both are installed as services. Yet, when both are started usually only the 2.6.4 is available. I have to turn it off to reach the other. What did I forget? Any suggestion appreciated. Henk Laloli___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Running different Zope versions
On Apr 11, 2005 1:58 PM, Henk Laloli [EMAIL PROTECTED] wrote: Is it possible to run different Zope versions on one machine? I have a Zope 2.6.4 running and a Zope 2.7.3 both on a Windows 2003 server. They use their own python. I run them on different port numbers configured in the zope.conf file. Both are installed as services. Yet, when both are started usually only the 2.6.4 is available. I have to turn it off to reach the other. What did I forget? Any suggestion appreciated. Hmmm, could it be that you changes only the HTTP port and that the FTP port or webDav port still tries to use the same port on both instances? Otehrwise I have no idea. It's always worked fine for me, I think. :) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-dev] Different code layout for Persistence between various Zope versions was: RE: [Zope] Can not import PersistentMapping)
Sean wrote at 2004-1-24 11:12 -0500: ... Looking at the ZOPE 2.6.2 Source on the Windows machine, I see code for modules: Persistence.PersistentMapping, and Persistence.PersistentList On Linux, the Zope 2.6.1 Source has a Persistence Directory with nothing in it. The __init__.py file says: ...While obviously there is nothing in this module, the correct names are inserted by the __init__.py in ZODB, jumpstarting the process. Actually, the __init__.py file on the windows machine says the same thing, but there ARE in fact source files in the directory for both the PersistentMapping and PersistentList modules - as well as some .c and .h files - as follows: cPickleCache.c cPersistence.c cPersistence.h PersistentList.py PersistentMapping.py Would these be differences between the two versions of Zope, or are the classes not properly setup on the Linux box, and once they are, I could expect to see the source files that I see on the Windows box? Or, perhaps the way these classes were being implemented was changing between the two releases, and I should just upgrade both machines to 2.6.4 which is listed as the current stable release, or 2.7.0rc1. Recommendations? I know nothing about Windows :-) I think, I read somewhere that PersistentMapping and PersistentList should be moved out from ZODB to Persistence -- but only for Zope 2.8. I would be surprised when the Windows installation were the place where such things start... I moved your question to mailto:[EMAIL PROTECTED] where there are probably more people which can answer it. -- Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Can edit via FTP respect Zope versions?
I would like to see the following scenario: 1) I go into Zope/manage_main, create a Version, and enter it. 2) Outside Zope, I use emacs and pull up a DTMLDocument in an edit buffer using FTP 3) I make my changes and save the file (FTP PUT) 4) I return to Zope and see that the changes have been made INSIDE MY VERSION 5) Happy with the changes, I commit my Version and exit it. Today, this does not seem to work. That is, even though I have started working in a Version, FTP does not respect this. How could such a facility be implemented? Well, what about having a context mapping feature where you could map a user to a context. The Zope FTP machinery, when it gets a login, uses the passed in userid and looks up the context in the (global) context map. For me, it says oh, Craeg is working in a Version. I will silently and automatically map URLs for GET and PUT to respect his Version. For my colleague, it says oh, Chip has no special context, no filtering needed... Further, there could be hooks provided so that Zope developers could provide their own URI Resolution algorithms, so that different user's requests could be mapped in different ways. To use a contrived example, this could be a way of implementing a development workflow scenario-- for development, requests are mapped to one area, where as for testing they are mapped to a different area. Note that the virtual host monster operates on a somewhat similar idea. Has anyone else felt the need for such a facility (URIResolver) ? Does anyone have any pointers where I should look in the Zope libraries to program my own? Thanks in advance! --Craeg ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Versions Core Session Tracking
Edmund Goppelt wrote: What has been your experience with Versions? Is this a reliable feature of Zope? It is, but only in certain circumstances: 1. When people using your site don't need to write to the ZODB to use the site (it sounds like they do in your case) 2. You don't use mounted storages. In particular, Core Session Tracking and Version objects seem to have quite a bad time of it when played with together, but it's understandable when you think about how CST works. I find versions are generally useful when updating brochurewear (DTML Methods and Dcouments) but are limited elsewhere. It's a shame you can't use them with WebDAV (guessing here, somebody tell me I'm wrong ;-) or FTP without major hackory :-S cheers, Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope] Versions...
Chris McDonough wrote: Mounted storages fall down with versions (do not use versions in conjunction with mounted storages, it will do bad things to you). Is it just me or are versions not exactly the most robust things around? (I'm thinking external methods here, and ftp access into a version, amongst others ;-) cheers, Chris ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] Versions...
Versions are problematic in combination with mounted storages in particular because there is no link in versioning between storages. You can easily create a versioned object in one storage, then traverse to another part of the instance space that's been mounted and use that version cookie to make a change. But you need to commit the two versions separately. If you commit one of them, you'll be left scratching your head as to why the other storage didn't commit. I'd say in this particular that it's perhaps a limitation of mounted storages rather than versions. -Original Message- From: Chris Withers [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 30, 2000 8:28 AM To: Chris McDonough Cc: 'Roman Milner'; [EMAIL PROTECTED] Subject: [Zope] Versions... Chris McDonough wrote: Mounted storages fall down with versions (do not use versions in conjunction with mounted storages, it will do bad things to you). Is it just me or are versions not exactly the most robust things around? (I'm thinking external methods here, and ftp access into a version, amongst others ;-) cheers, Chris ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
