Re: Issue, not sure how to solve

Dirk H Bartley <[email protected]> Tue, 16 Aug 2011 15:45:26 -0400
Newsgroups gmane.comp.cms.opengroupware.xmlrpc.devel
Message-ID <[email protected]>
Ok,  .. ..   I am feeling dumb.  I was figuring it was non-printable
characters, but did not see any in the single line string.  Even now,
when I search for 0E, vi is telling me that searching for 0E yields no
results.  So how do I find the offending customer record this time??

Then, How do I prevent such offending characters in from being put in in
php in the future.

I assume I need to do some direct posgresql querries for searching for
records with nonprintable charachters.  My guess is that if there is one
there are more.

Ahhhhh, the joys of users doing unexpected things.

Thank you so kindly for your assistance.

Dirk

On Tue, 2011-08-16 at 14:21 -0400, Adam Tauno Williams wrote:
> On Tue, 2011-08-16 at 13:04 -0400, Dirk H Bartley wrote:
> > Hi
> > Ok, so I'm a total slacker and am still using OGO legacy.
> > But my php application is getting an xml-rpc error.  In my syslog I get
> > Aug 16 09:47:21 mta1 httpd: zOGI recevied an XML-RPC fault (2: Invalid
> > return payload: enable debugging to examine incoming payload)
> > Hmm, this occurs anytime I search for all companies with the text martin
> > in the name.
> > criteria is : Array ( [0] => Array ( [key] => name [value] => %martin%
> > [expression] => ILIKE ) )
> > ogo legacy is sending :
> > http://www.schupan.com/deleteme/deleteme
> > (I pulled it up in firefox and firefox even described it as malformed)
> 
> Fix the data; it is just putting in the field what is there.  But that
> is not a valid character for the content encoding.  Typically this can
> happen if someone cut-n-pastes values from Excel and the front-end does
> not sanitize the value.  The backend will happily store it - assuming it
> is valid UTF-8 - but the client's XML parser will probably barf.
> 
> 
> > Is there anything to do to solve or do I just need to schedule a few of
> > days to convert over from legacy to coils.
> 
> So go into the table and eliminate the invalid character.
> The issue is you have \00\0E in a telephone number.
> 
> 


-- 
OpenGroupware.org XML-RPC
[email protected]
http://mail.opengroupware.org/mailman/listinfo/xmlrpc