Re: [Zope] Confusing DateTime().strftime behavior
Are you using Python 2.4? I've seen other people here on the list having problems witht he DateTime module and it being a day off. Search the archive on 'strftime' and hope. 2005/10/15, Kirk Strauser [EMAIL PROTECTED]: I'm upgrading our server from a FoxPro backend to PostgreSQL, using the Psycopg connector. My problem is that the old database returned timestamps as a %m/%d/%Y-formatted string, while Psycopg returns a DateTime object (I'm using the internal module, not mxDateTime). Whenever I use strftime to format the object for display, I get the previous day's date instead. I've found several references to this problem in Google, but no one seems to have found a good solution. Any thoughts? -- Kirk Strauser The Day Companies ___ 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 ) -- Peter Bengtsson, work www.fry-it.com home www.peterbe.com hobby www.issuetrackerproduct.com ___ 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] Confusing DateTime().strftime behavior
On Saturday 15 October 2005 01:24, Andreas Jung wrote:
If you speak of DateTime instances then you should be able to write
to two-line testcase that shows the issue with a standard Zope
installation.
If you can provide such a testcase we are able to look at it in detail.
date = context.testQuery()[0]['date']
print date
print date.ISO()
print date.strftime('%m/%d/%Y')
return
gives
2005/10/14
2005-10-14 00:00:00
10/13/2005
By the way, this is with Zope 2.7.7 and Python 2.3.5 on a FreeBSD 5-STABLE
server (if that makes any difference).
--
Kirk Strauser
The Day Companies
___
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] Confusing DateTime().strftime behavior
--On 16. Oktober 2005 10:41:19 -0500 Kirk Strauser [EMAIL PROTECTED] wrote: On Saturday 15 October 2005 01:24, Andreas Jung wrote: If you speak of DateTime instances then you should be able to write to two-line testcase that shows the issue with a standard Zope installation. If you can provide such a testcase we are able to look at it in detail. date = context.testQuery()[0]['date'] This might work for you on your system but that is unusable to reproduce your error on a bare Zope system. -aj pgpWRcZ4UIAOR.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 )
Re: [Zope] REQUEST not accessible
Jürgen Herrmann wrote at 2005-10-13 12:39 +0200: ... it seems this isn't working anymore, the catalog would return all brains instead of seraching the relevant ones... (completely ignoreing everything in REQUEST) This should still work in Zope 2.8.1. The relevant code is in Products.ZCatalog.Catalog.Catalog.searchResults. -- Dieter ___ 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] Packaging a zope application
Joshua Burvill wrote at 2005-10-10 10:19 +1000: ... We put everything we can into the filesystem (e.g. via CMFCore's Filesystem Directory View) and use CVS/SVN to manage and distribute it. ... I guess that means creating a kind of product. The CMF comes with such a product: Filesystem Directory View. You can use is outside the CMF (but it is most useful together with a CMF SkinsTool (or my SkinnedFolder)). Someone repackaged it also alone (in case you do not want to install CMFCore). -- Dieter ___ 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] __getitem__ and returning a PageTemplateFile instance
Anders Bruun Olsen wrote at 2005-10-14 11:53 +0200: ... I am trying to make a product where-in I want to be able to return a page based on the url, think something like /product/username which would return a page with the users details. For this purpose I am using __getitem__, but when I return a PageTemplateFile instance it just tells me it has encountered a problem publishing the object. I such a case, you look at the traceback (which you can find in the error_log object in your Zope Root Folder (ZMI)). If it does not solve the problem directly, you include the full error information (at least Error Type, Error Value *AND* traceback) in your post. -- Dieter ___ 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] POSKeyError nightmare
Kevin Carlson wrote at 2005-10-10 18:37 -0400:
...
I'm not sure I understand what you mean by fixing them all as shown
above. You mention loading the object from the ZODB and deleting the
broken references, but I'm not sure how to do that.
fsrefs tells you the OID of objects containing broken
references.
When you have the OID (as binary value; I think
fsrefs tells you the hex value, then can use hexvalue.decode('hex')
to get it as binary), you can load the respective object
via
obj = connection[OID]
You get the connection from an object via obj._p_jar.
In your case, an OOBucket lost some of its references
(that is an easy case -- provided it does not loose all its content).
You determine the broken keys and delete them:
for k,v in list(bucket.objectItems()):
try: v._p_changed = 0 # load the object
except:
# broken
del bucket[k]
The case becomes very complicated, when the bucket ends
empty -- an empty bucket would make the (probably) enclosing
BTree invalid. You would need to fake something to
keep it non-empty.
if not bucket: bucket[k] = None # k was one of the deleted keys
--
Dieter
___
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] Deleting objects from an external method
Nikko Wolf wrote at 2005-10-14 15:37 -0600: I'm trying to allow users to delete objects that have been accidentally created. I have criteria for what that means, but since I *DO NOT* want them to delete object except by this method, I want to avoid granting Delete objects to them (non-Managers). Can this even be done? At the base level, Delete objects is a hard-coded requirement of the ObjectManager.manage_delObjects() function. Usually, an External Method is not restricted by Zope's security. Unless manage_delObjects does not perform an additional internal check (I think, it does not), your External Method can use it to delete objects. BTW: Often, it is more faster simply to try something than to post a question to the mailing list and wait for the answer. Your question above is such a case ... -- Dieter ___ 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] Error on starting and stopping Zope 2.8.2
whrandom is a deprecated python library package which should be replaced by random. Python 2.3.5 does not produce the deprecation warning but lacks some of the features of the Python 2.4.X series. On Fri, 14 Oct 2005 [EMAIL PROTECTED] wrote: Hello. On starting and stopping Zope 2.8.2 (upgraded from 2.8.1, compiled with Python 2.4.2, running on Fedora Core 3) I get the following error. Performance does not seem to be affected. Resolution? # service zopectl start /opt/python2.4.2/lib/python2.4/whrandom.py:38: DeprecationWarning: the whrandom module is deprecated; please use the random module DeprecationWarning) . daemon process started, pid=22829 # service zopectl stop /opt/python2.4.2/lib/python2.4/whrandom.py:38: DeprecationWarning: the whrandom module is deprecated; please use the random module DeprecationWarning) . daemon process stopped -- ___ 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] Error on starting and stopping Zope 2.8.2
--On 16. Oktober 2005 11:27:36 -0700 Dennis Allison [EMAIL PROTECTED] wrote: whrandom is a deprecated python library package which should be replaced by random. Python 2.3.5 does not produce the deprecation warning but lacks some of the features of the Python 2.4.X series. It is already replaced on the trunk but there is no need to replace it on the 2.8 branch. Once again: Python 2.4 is not supported for Zope 2.8 and therefore there is no need to replace something for an unsupported configuration. Such changes can be made for major release but not after the seconds minor release. The 2.8 branch is in general closed for new features. This change is neither a bugfix nor a feature request...this warning is just a warning as the name says...if it worries you, close your eyes :-) -aj pgpPmXkgkJ9tN.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 )
RE: [Zope] Error on starting and stopping Zope 2.8.2
Pascal, Why does Zope lag the release of Python by so very long? The Python 2.4.X series includes language features and poerformance enhancements which ought to be available in Zope. For the most part, Python 2.3.5 is a subset of Python 2.4.X. Compatibility is a language and implementation design priority. Python 2.4 was released November 30, 2004, almost a year ago. Python 2.3.5 was released Feb 8, 2005 (after Python 2.4.0, released November 30, 2004, and shortly before Python 2.4.1 which was released March 30, 2005). Python 2.3 was released July 29, 2003. The current Python 2.4.2 was released just recently. My understanding is that the reason the Python 2.4.X is not the recommended Python is because a security audit has not been performed and not because of functionality issues.We have been using Python 2.4.1 in production without apparent problems; I am about to move to 2.4.2 which fixes some bugs we have not encountered. IMHO it would be wise to track the releases of Python a bit more closely. On Fri, 14 Oct 2005, Pascal Peregrina wrote: From the Zope 2.8.2 announcement on this mailing list : Please also keep in mind that Zope 2.8.2 requires Python 2.3.5. Zope 2.8.2 is not certified for any Python 2.4.x versions. So using Python 2.4 is neither recommended nor supported and any related questions or problems are likely to be ignored until 2.4 is an officially supported Python version for Zope. Pascal -- ___ 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] Error on starting and stopping Zope 2.8.2
On 16 Oct 2005, at 19:54, Dennis Allison wrote: Why does Zope lag the release of Python by so very long? Because someone has to spend considerable time to assess impacts on the Zope 2 security machinery. This has been mentioned on this and other Zope lists on various occasions. My understanding is that the reason the Python 2.4.X is not the recommended Python is because a security audit has not been performed and not because of functionality issues.We have been using Python 2.4.1 in production without apparent problems; I am about to move to 2.4.2 which fixes some bugs we have not encountered. The fact that it seems to work is a pretty weak argument. It's like driving with really old tires where the rubber is starting to crack. It could lead to sudden failure, even though the car seems to drive just fine today. jens ___ 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] Error on starting and stopping Zope 2.8.2
Andreas, Aside from a security audit what problems have been reported using Python 2.4.X? Those of use who run Python 2.4.X do it becasue we want access to the language features and performance. If there are stability issues attributed to that choice, we'd like to know what they are. If the reason for trying to stick with 2.3.5 is to maintain a stable test and development environment for Zope 2.8, so be it. It is much much easier to fix one of the multitude of possible variables in a complex system. I, for one, have occasionally created a special instance of Zope running a different Python to ensure a problem I had discovered was not python version related. -d On Fri, 14 Oct 2005, Andreas Jung wrote: --On 14. Oktober 2005 10:09:39 -0600 [EMAIL PROTECTED] wrote: Hello. On starting and stopping Zope 2.8.2 (upgraded from 2.8.1, compiled with Python 2.4.2, running on Fedora Core 3) I get the following error. Performance does not seem to be affected. Resolution? Quote from my announcement yesterday: Please also keep in mind that Zope 2.8.2 requires Python 2.3.5. Zope 2.8.2 is not certified for any Python 2.4.x versions. So using Python 2.4 is neither recommended nor supported and any related questions or problems are likely to be ignored until 2.4 is an officially supported Python version for Zope. :-) -aj -- ___ 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] Error on starting and stopping Zope 2.8.2
--On 16. Oktober 2005 11:54:18 -0700 Dennis Allison [EMAIL PROTECTED] wrote: IMHO it would be wise to track the releases of Python a bit more closely. Software components choosen for a framework have to be solid and approved. There is no reason to run after every new python version or whatever. Stability and performance is somewhat more important than hunting for new language features.. Some features of Python 2.4 are nice2have but we can perfectly live with Python 2.3.5. If you want Python 2.4, use it (at your own risk). As we already explained a bunch of times (sorry, this issue is bothering the more people ask about the same issue), a security audit has not happened yet. Why not? Because it takes time to do such an audit and the persons that can do such an audit likely had not time so far. So things are as they are and will change as they change. If you have the skills, resources and perhaps some money to fund the audit then raise your hand. Otherwise we have to wait until it will happen. -aj pgpgXajSHuyQv.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 )
Re: [Zope] Error on starting and stopping Zope 2.8.2
--On 16. Oktober 2005 12:01:00 -0700 Dennis Allison [EMAIL PROTECTED] wrote: If the reason for trying to stick with 2.3.5 is to maintain a stable test and development environment for Zope 2.8, so be it. It is much much easier to fix one of the multitude of possible variables in a complex system. I, for one, have occasionally created a special instance of Zope running a different Python to ensure a problem I had discovered was not python version related. Please look at Tim Peter's statement concerning the security audit...there is nothing to add..that's the official position from the ZC side and I do 100% second this position. I won't continue responding to such postings and request as long as the situation is unchanged...this discussion is a waste of time and we discussed this issue already long enough on this list. I find it somewhat bothering and annoying to discuss the same things over and over again...can we stop this for now? -aj pgpjkWhtkJKjO.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 )
RE: [Zope] Error on starting and stopping Zope 2.8.2
Andreas, I understand both the importance of stability and the need for a security audit at some point. (I do wish we had the funds or I had the time to help move it forward, but I don't.) I also understand the need for a consistent framework for reporting and resolving bugs. It is reasonable to expect that all bugs be reported against the same framework to eliminate one significant possible variable. What does concern me is the way in which the recommendation to use (at the moment) Python 2.3.5 is explained. I may be willing to accept the risks of using a system which has not yet been audited in terms of security, but I want to know if there are any reported instabilities or incompatibilities which have been identified when, say, Python 2.4.X is used. I'd rather people say that the standard reference platform against which all bugs should be reported uses 2.3.5, and that use of other, later versions of Python is at your own risk. When using another Python that is known to cause problems, it would make sense to identify the problem so that users can make an informed decision. There are times when there are Python version related problems and these need to be identified and publicized. We certainly collect the incompatilities (if there are any) so they can be fixed as eventually the code base will move to later python systems. -d On Sun, 16 Oct 2005, Andreas Jung wrote: --On 16. Oktober 2005 11:54:18 -0700 Dennis Allison [EMAIL PROTECTED] wrote: IMHO it would be wise to track the releases of Python a bit more closely. Software components choosen for a framework have to be solid and approved. There is no reason to run after every new python version or whatever. Stability and performance is somewhat more important than hunting for new language features.. Some features of Python 2.4 are nice2have but we can perfectly live with Python 2.3.5. If you want Python 2.4, use it (at your own risk). As we already explained a bunch of times (sorry, this issue is bothering the more people ask about the same issue), a security audit has not happened yet. Why not? Because it takes time to do such an audit and the persons that can do such an audit likely had not time so far. So things are as they are and will change as they change. If you have the skills, resources and perhaps some money to fund the audit then raise your hand. Otherwise we have to wait until it will happen. -aj -- ___ 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] __getitem__ and returning a PageTemplateFile instance
On Sun, Oct 16, 2005 at 06:50:09PM +0200, Dieter Maurer wrote: I am trying to make a product where-in I want to be able to return a page based on the url, think something like /product/username which would return a page with the users details. For this purpose I am using __getitem__, but when I return a PageTemplateFile instance it just tells me it has encountered a problem publishing the object. I such a case, you look at the traceback (which you can find in the error_log object in your Zope Root Folder (ZMI)). It just says No exceptions logged. So it does not log any errors in error_log. The error message I am getting is: Site Error An error was encountered while publishing this resource. Debugging Notice Zope has encountered a problem publishing your object. Cannot locate object at: http://localhost:8080/vitester/asonhe If it does not solve the problem directly, you include the full error information (at least Error Type, Error Value *AND* traceback) in your post. If there had been a better error description I would of course have included it, but the thing that has made this difficult to understand is that I haven't been able to find any real error messages. I have enabled debug-mode and am running Zope in the foreground, but it reports no errors at all. -- Anders -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS/O d--@ s:+ a-- C++ UL+++$ P++ L+++ E- W+ N(+) o K? w O-- M- V PS+ PE@ Y+ PGP+ t 5 X R+ tv+ b++ DI+++ D+ G e- h !r y? --END GEEK CODE BLOCK-- PGPKey: http://random.sks.keyserver.penguin.de:11371/pks/lookup?op=getsearch=0xD4DEFED0 ___ 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] Error on starting and stopping Zope 2.8.2
On Sun, 2005-10-16 at 12:29 -0700, Dennis Allison wrote: What does concern me is the way in which the recommendation to use (at the moment) Python 2.3.5 is explained. I may be willing to accept the risks of using a system which has not yet been audited in terms of security, but I want to know if there are any reported instabilities or incompatibilities which have been identified when, say, Python 2.4.X is used. I'm sure there are, but a list of all such issues hasn't been created and likely won't be. I suspect that there just aren't a lot of folks who are willing to do the time-consuming labor of testing their application under both 2.3.5 and a later Python revision and reporting the issue in a structured way to make it easy for others to consume. To the extent that some people are willing to do this, the historical mechanism for reporting has been the Zope collector; these kinds of issues are thrown in to the bucket like any other kind of issue. A concentrated effort is usually organized every year or two to find and solve them. When this concentrated effort is undertaken, developers have time to go cull the collector for issues like this. This is also why it's only undertaken every year or so, because it's pretty labor-intensive and so usually requires some injection of cash (which has historically comes from Zope Corporation or one of their customers). Collector issues already have a metadata field that is supposed to be used as a field for reporting the Python version used. Unfortunately there is no user-visible searching mechanism in the collector to show only issues that have been reported against a particular Python version. - C ___ 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-Annce] MailTemplates 1.1.0 Released!
These allow you to use the full power of the the python email package along with Zope's Page Template technology to easily build and send fully standards compliant emails. This release adds the ability to create attachments using string data. It also fixes a long list of bugs uncovered by public testing and has been tested for compatability with Zope 2.7, Zope 2.8, CMF 1.4 and CMF 1.5. For more information, please see: http://www.simplistix.co.uk/software/zope/mailtemplates cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Announce maillist - Zope-Announce@zope.org http://mail.zope.org/mailman/listinfo/zope-announce Zope-Announce for Announcements only - no discussions (Related lists - Users: http://mail.zope.org/mailman/listinfo/zope Developers: http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-Checkins] SVN: Zope/branches/Zope-2_8-branch/ - ZSQLMethod.manage_main: Moved the error message that warns of a
Log message for revision 39474:
- ZSQLMethod.manage_main: Moved the error message that warns of a
non-existing or closed database connection next to the Connection ID
dropdown and present it using red to increase its visibility.
Changed:
U Zope/branches/Zope-2_8-branch/doc/CHANGES.txt
U
Zope/branches/Zope-2_8-branch/lib/python/Products/ZSQLMethods/dtml/edit.dtml
-=-
Modified: Zope/branches/Zope-2_8-branch/doc/CHANGES.txt
===
--- Zope/branches/Zope-2_8-branch/doc/CHANGES.txt 2005-10-16 16:36:25 UTC
(rev 39473)
+++ Zope/branches/Zope-2_8-branch/doc/CHANGES.txt 2005-10-16 17:23:01 UTC
(rev 39474)
@@ -6,14 +6,14 @@
To-do
- - Renable C permission roles by implementing recent Python
+ - Reenable C permission roles by implementing recent Python
changes in C, brining the Python and C implementations back in
sync. See lib/python/AccessControl/PermissionRole.py.
- Add cyclic-garbage collection support to C extension classes,
especially to acquisition wrappers.
- - Renable C Zope security policy by implementing recent Python
+ - Reenable C Zope security policy by implementing recent Python
changes in C, bringing the Python and C implementations back in
sync. See lib/python/AccessControl/ZopeSecurityPolicy.py.
@@ -22,6 +22,14 @@
- Collector #1233: port ZOPE_CONFIG patch from Zope 2.7 to Zope 2.8
+ After Zope 2.8.2
+
+Other
+
+ - ZSQLMethod.manage_main: Moved the error message that warns of a
+non-existing or closed database connection next to the Connection ID
+dropdown and present it using red to increase its visibility.
+
Zope 2.8.2 (2005/10/13)
Features added
Modified:
Zope/branches/Zope-2_8-branch/lib/python/Products/ZSQLMethods/dtml/edit.dtml
===
---
Zope/branches/Zope-2_8-branch/lib/python/Products/ZSQLMethods/dtml/edit.dtml
2005-10-16 16:36:25 UTC (rev 39473)
+++
Zope/branches/Zope-2_8-branch/lib/python/Products/ZSQLMethods/dtml/edit.dtml
2005-10-16 17:23:01 UTC (rev 39474)
@@ -2,16 +2,6 @@
dtml-var manage_tabs
dtml-if SQLConnectionIDs
-dtml-if connectionIsValid
- dtml-if connecteddtml-else
- strongWarning:/strong
- The database connection used by this method is currently not
- open.
- /dtml-if
-dtml-else
- strongWarning:/strong
- The database connection for this method cannot be found!
-/dtml-if
form action=manage_edit method=POST
table cellpadding=2 cellspacing=0 width=100% border=0
@@ -42,6 +32,19 @@
dtml-sequence-key;/option
/dtml-in
/select
+dtml-if connectionIsValid
+ dtml-if connecteddtml-else
+ p style={color:red;}
+ strongWarning:/strong
+ The database connection used by this method is closed.
+/p
+ /dtml-if
+dtml-else
+ p style={color:red;}
+strongWarning:/strong
+The database connection for this method cannot be found!
+ /p
+/dtml-if
/div
/td
/tr
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/Zope-2_8-branch/lib/python/Products/ZSQLMethods/dtml/edit.dtml - be a little more helpful by revealing the vanished database connection ID
Log message for revision 39476:
- be a little more helpful by revealing the vanished database connection ID
Changed:
U
Zope/branches/Zope-2_8-branch/lib/python/Products/ZSQLMethods/dtml/edit.dtml
-=-
Modified:
Zope/branches/Zope-2_8-branch/lib/python/Products/ZSQLMethods/dtml/edit.dtml
===
---
Zope/branches/Zope-2_8-branch/lib/python/Products/ZSQLMethods/dtml/edit.dtml
2005-10-16 17:23:17 UTC (rev 39475)
+++
Zope/branches/Zope-2_8-branch/lib/python/Products/ZSQLMethods/dtml/edit.dtml
2005-10-16 18:38:09 UTC (rev 39476)
@@ -42,7 +42,8 @@
dtml-else
p style={color:red;}
strongWarning:/strong
-The database connection for this method cannot be found!
+The selected database connection (dtml-connection_id;)
+cannot be found!
/p
/dtml-if
/div
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Coders] Zope tests: 8 OK
Summary of messages to the zope-tests list. Period Sat Oct 15 11:01:01 2005 UTC to Sun Oct 16 11:01:01 2005 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Sat Oct 15 22:27:07 EDT 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-October/003327.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Oct 15 22:28:37 EDT 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-October/003328.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Oct 15 22:30:07 EDT 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-October/003329.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Oct 15 22:31:37 EDT 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-October/003330.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Oct 15 22:33:07 EDT 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-October/003331.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Oct 15 22:34:37 EDT 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-October/003332.html Subject: OK : Zope-trunk Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Oct 15 22:36:07 EDT 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-October/00.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Oct 15 22:37:37 EDT 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-October/003334.html ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
[Zope-dev] Re: [Zope-CMF] Re: RestrictedPython, TALES Expressions and CMF
Tres Seaver wrote at 2005-10-11 08:58 -0400: ... 'call_with_ns' should be invoked only for objects with either a '__render_with_namespace__' attribute (PythonScripts fit here) or those with 'isDocTemp' true. Its only real purpose is to set up the namespace before calling a DTMLMethod; I don't even understand why PythonScripts have such a method. Probably, because they can bind the DTML namespace... -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] Re: [Zope-Checkins] SVN: Zope/trunk/lib/python/Shared/DC/ZRDB/ Collector #556: sqlvar now returns 'null' rather than 'None'.
Chris Withers wrote at 2005-10-11 07:50 +0100: ... I dunno, it's very handy to be able to rely on something RDB-like being installed when you want to tests things like ZSQL methods... But, for ZSQL method tests you do not need a real DA; a DA fake is sufficient (you test ZSQL methods and not SQL command execution). -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
