thanks to Dieter and Peter Bengtsson .
Rajasekhar.
On Sat, Dec 13, 2008 at 6:30 PM, Peter Bengtsson wrote:
> Assuming you're developing your product on the filesystem and not inside
> the ZMI
> you can use this:
> http://www.fry-it.com/oss/ZSQL which has some profiling options.
>
> 2008/12/12 i
Has nothing to do with Zope but...
Use Firefox to debug it and you'll get to see the error.
put method="post" on form tag and the submission won't be visible in the URL.
2008/12/11 C :
> We are running Zope 2.9.8 on Macintosh OS X Server 10.5.5 behind Apache 2.x.
>
> I am having a problem when try
Quoting Peter Bengtsson :
> Has nothing to do with Zope but...
> Use Firefox to debug it and you'll get to see the error.
> put method="post" on form tag and the submission won't be visible in the URL.
I've had this happen with method=get in the past. Changing to post fixed it
but...
May be worth
2008/12/15 :
> Quoting Peter Bengtsson :
>
>> Has nothing to do with Zope but...
>> Use Firefox to debug it and you'll get to see the error.
>> put method="post" on form tag and the submission won't be visible in the URL.
> I've had this happen with method=get in the past. Changing to post fixed i
It turns out that Internet Explorer doesn't like it when you pass more than
141 form variables with a single submit. Our site collects employment
applications and once we hit 142 applications the page broke for anyone
using IE7 on XP.
On Thu, Dec 11, 2008 at 10:17 AM, C wrote:
> We are running Z
Andreas Jung wrote at 2008-12-14 16:00 +0100:
>On 14.12.2008 15:44 Uhr, Thibaud Morel l'Horset wrote:
>> Hey AJ,
>>
>> Thanks. Full traceback below. Regarding storing files, I meant the File
>> Zope Object, as added by the following API call:
>> newFolder.manage_addFile(id,title=title, content_type
On Monday 15 December 2008 15:04, Peter Bengtsson wrote:
> 2008/12/15 :
> > Quoting Peter Bengtsson :
> >> Has nothing to do with Zope but...
> >> Use Firefox to debug it and you'll get to see the error.
> >> put method="post" on form tag and the submission won't be visible in the
> >> URL.
> >
>
Hi Dieter,
That makes a lot of sense, thanks. Once I encode the strings in utf-8
there are no issues.
That's a great tip about setting the content_type charset correctly. The
way I was handling this so far was to specify it in the header of the page
that was displaying the text:
But s
One more thing... as far as I can tell there is still a need to set the
header through a nocall if try to display your file content as part of a
larger page that is generated with out of the box Page Templates or DTML
methods.
So the call that I pasted below should help if anyone else ever runs in
