>> Is disabling the override as simple as commenting out a section?, ie:
>>
>> > File "/home/zope/qutang-zope29/parts/qutang-plone25-products/
>> > > Plone4ArtistsAudio/pythonlib/plone/app/form/overrides.zcml", line
>> > 7.2-13.8
>
> yup.
>
>
>> What negative effects is that likely to have on P4A?
>
> negligible, both overrides are in effect doing the same thing.  
> having just one accomplishes the same thing, and get rids of the  
> conflict.
>
> -kapil



Mille Grazie!

Thanks, Kapil, I really appreciate your input!

I'll see how this works out.
Seems I tried removing p4a altogether at one point, and still ran into  
a hurdle.
Well... one at a time ;-)

Now... about how one might handle such things in a buildout...

Cheers

PF

On 11 Dec 2008, at 11:59 AM, Kapil Thangavelu wrote:

>
>
> On Thu, Dec 11, 2008 at 12:47 PM, Peter Fraterdeus <[email protected] 
> > wrote:
>
>
>
> On 11 Dec 2008, at 9:19 AM, Kapil Thangavelu wrote:
>
> > for this particular error, you'll need to disable either the getpaid
> > override or the p4a's custom plone.app.form override. Their both
> > attempting to register a custom error widget. for plone 3, getpaid
> > doesn't register this override.  there are other issues (as i eluded
> > to  in previous email ) from p4a's monkey patching of formlib in
> > plone 2.5. They basically monkey patch Five.formlib directly into
> > zope.formlib which breaks stuff using Five.formlib correctly as
> > decoding/marshalling variables is then performed multiple times. As
> > i recall some of the admin ui thus breaks.
> >
> > -kapil
>
> Hi Kapil, Chris, Horacio
>
> Thanks much for the input!
> Black magic indeed ;-)
>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"getpaid-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to