Re: Fwd: Re: Poi update

On Fri, Feb 10, 2006 at 08:50:12PM -0000, Martin Aspeli wrote:
| >>Thank you Martin, that was the problem indeed.
| >>
| >>Btw, only for your information, I noticed those messages when running   
| >>runzope in debug mode when I add a response to an issue:
| >>
| >>2006-02-09 17:53:39 INFO Archetypes Tried to update PoiResponse:id but   
| >>field is not writeable.
| >>2006-02-09 17:53:39 INFO Archetypes Tried to update PoiResponse:title  
| >>but  field is not writeable.
| >  Yeah. Archetypes sucks. :)
| > You tell it that a field is read-only, and then it acts surprised in  
| >the log.
| >Stupid.
| 
| Quote from Archetypes.Field.py:
| 
|      security.declarePublic('writeable')
|      def writeable(self, instance, debug=True):
|          if 'w' not in self.mode:
|              if debug:
|                  log("Tried to update %s:%s but field is not writeable." %  
| \
|                      (instance.portal_type, self.getName()))
|              return False
| 
| Who on earth made 'debug' default to True in a release???
| 
| With other words: I think that should be changed.
| 
| Opinions anyone?

What's the issue? It's helpfully logging a message that the field is
not writeable, nothing else.

-- 
Sidnei da Silva
Enfold Systems, LLC.
http://enfoldsystems.com


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642