Hi.
I want to fix this bug 442 and want to ask some question here about doing
that, if thats ok, i'll hope so.
I'll fixed the decorator not to apply shales validator renderer if the
renderer family matches the ajax stuff, which let them work again.
However this seams not the ultimate approach
On Mon, Mar 31, 2008 at 5:24 PM, Torsten Krah
[EMAIL PROTECTED] wrote:
I want to fix this bug 442 and want to ask some question here about doing
that, if thats ok, i'll hope so.
This is definitely the right place to discuss such fixes.
I'll fixed the decorator not to apply shales
Hi.
I want to fix this bug 442 and want to ask some question here about doing
that, if thats ok, i'll hope so.
I'll fixed the decorator not to apply shales validator renderer if the
renderer family matches the ajax stuff, which let them work again.
However this seams not the ultimate approach
Hi.
I want to fix this bug 442 and want to ask some question here about doing
that, if thats ok, i'll hope so.
I'll fixed the decorator not to apply shales validator renderer if the
renderer family matches the ajax stuff, which let them work again.
However this seams not the ultimate approach
Am Dienstag, 1. April 2008 schrieb Torsten Krah:
WARNING: bad headers - Duplicate header field: Reply-To
Something off-topic, i'll wrote the mail 3 times now and 2 got not delivered
because the list produces invalid mail headers (it inserts a reply-to header
instead of replacing the existing
We got the mail three times - at least I did :-)
On Tue, Apr 1, 2008 at 1:37 AM, Torsten Krah
[EMAIL PROTECTED] wrote:
Something off-topic, i'll wrote the mail 3 times now and 2 got not delivered
because the list produces invalid mail headers (it inserts a reply-to header
instead of
