ect
way to resolve this.
Any comments would be appreciated
Thanks,
Daryl.
--
Daryl Daly, B.Sc.
Chief Programmer/Business Analyst
[EMAIL PROTECTED]
Norco Products Ltd. Really Cool Bikes!!!
Norco__OTel: 604-552-2930 ext 205
Performance=\ \
>>
>> I have been able to fix the problem by adding this to my zope.conf:
>>
>> HTTP_ACCEPT_CHARSET utf-8
>>
>
> Should not play a role here.
However, if I remove it & restart zope, the problem comes back :)
>
>
>>
>> I don't understand why this "fixes" the problem or if it is the correct
>>
On Sun, February 18, 2007 1:29 pm, Jostein Leira wrote:
> After the comments in the Collector above I'm wondering what to do if I
> should not set the sys.setdefaultencoding()? Not changing the default
> encoding I always get a decode error when trying to save a page template
> with non-ascii cha
I have setup a test case which seems to show the problem. This test
removes the database component.
New install of zope 2.10.2:
Zope Version (Zope 2.10.2-final, python 2.4.4, linux2)
Python Version 2.4.4 (#1, Oct 23 2006, 13:58:00) [GCC 4.1.1 20061011 (Red
Hat 4.1.1-30)]
System Platform linux2
I
On Wed, February 21, 2007 2:05 am, Jostein Leira wrote:
>
> How about changing the following line 996 in
> /lib/python/zope/publisher/http.py ( as described in
> http://www.zope.org/Collectors/Zope/2280 )
>
> header_present = 'HTTP_ACCEPT_CHARSET' in self.request
> to
>
> header_pr
> Date: Wed, 15 Jul 2009 18:01:58 -0700 (PDT)
> From: Dennis Allison
> I am getting 401 errors with ZSyncer-0.7.1 using a configuration which
> worked with Zope 2.9 and an earler version of the ZSyncer product. Both
> use Python 2.4. Has anyone seen this problem? Can you recommend a fix?
> Is