Code point \u000B is not a valid character in XML

I'm trying to bulk republish via bric_soap and encountering
this error
message (from the logs):

[error] SOAP::Serializer::envelope: Server Code point
\u000B is not a
valid character in XML at
/home/bricolage/lib/Bric/SOAP/Util.pm line 658

I found this thread, but I didn't see a resolution:

http://marc.info/?l=bricolage-general&m=1
15257205519741&w=2


Chris Schults
Web Production Manager
Grist
710 Second Avenue, Suite 860
Seattle, WA  98104
Phone: 206-876-2020, ext. 204
Fax: 253-423-6487
<http://www.grist.org>

On Mon, 19 Mar 2007, Chris Schults wrote:
> I'm trying to bulk republish via bric_soap and
encountering this error
> message (from the logs):
>
> [error] SOAP::Serializer::envelope: Server Code point
\u000B is not a
> valid character in XML at
/home/bricolage/lib/Bric/SOAP/Util.pm line 658
>
> I found this thread, but I didn't see a resolution:
>
> http://marc.info/?l=bricolage-general&m=1
15257205519741&w=2

Does your XML validate?

> Does your XML validate?
 
I'm not sure, how does one validate the XML of a bric_soap
output?
 
Chris

On Tue, 20 Mar 2007, Chris Schults wrote:
>> Does your XML validate?
>
> I'm not sure, how does one validate the XML of a
bric_soap output?

Oh, I read too fast before...
What command are you doing, exactly?
The error is coming from XML::Writer. In Bric::SOAP::Util:

     $writer->dataElement("data", $data,
                          element =>
$element->get_key_name,
                          order   =>
$element->get_place - $diff);

Presumably we're handling something wrong, though I don't
know
what the correct unicode-handling would be.

To the workaround:
Which story is failing? What's different about it,
like it has a weird character I guess? (Elementary, my dear
Watson.)
Can you export it with bric_soap? (I'd guess not.)

> On Tue, 20 Mar 2007, Chris Schults wrote:
>>> Does your XML validate?
>> 
>> I'm not sure, how does one validate the XML of a
bric_soap output?
>
> Oh, I read too fast before...
> What command are you doing, exactly?
> The error is coming from XML::Writer. In
Bric::SOAP::Util:
>
>    $writer->dataElement("data", $data,
>                         element =>
$element->get_key_name,
>                         order   =>
$element->get_place - $diff);
>
> Presumably we're handling something wrong, though I
don't know
> what the correct unicode-handling would be.
>
> To the workaround:
> Which story is failing? What's different about it,
> like it has a weird character I guess? (Elementary, my
dear Watson.)
> Can you export it with bric_soap? (I'd guess not.)
>

To help with your debugging, maybe see 
http://marc.info/?l=bricolage-general&m=1
16543699704883&w=2

Looks like I encountered a similar thing this past
December.

John

So we've got some php code  - just a phpinfo() - that we
want to hit 
on the Bricolage Apache instance. Apache comes up as having
php 
installed, but when we hit the file, it doesn't get rendered
- we 
just see the source.  When we start up Apache without
Bricolage, php 
works.

Is there something Bricolage does to inhibit phpness?


-- 
Matt Rolf, J.D.
Web Technology Analyst
Computing Services
Denison University
(740) 587-6537

> What command are you doing, exactly?



bric_soap story list_ids --search
primary_uri=/comments/interactivist/% | bric_soap story
export -> keyword_interactivist.xml --timeout 0

I should note that I get a similar error for another
category, but not for the rest of my categories, which makes
me think it has to do with the story's content.

> Which story is failing? What's different about it,
> like it has a weird character I guess? (Elementary, my
dear Watson.)

What's the best method for trying to figure this out
(keeping in mind that there are hundreds of stories).

Thanks,

Chris

-----Original Message-----
From: slanninglocalhost.localdomain on behalf of Scott
Lanning
Sent: Tue 3/20/2007 10:06 AM
To: userslists.bricolage.cc
Subject: RE: Code point \u000B is not a valid character in
XML
 
On Tue, 20 Mar 2007, Chris Schults wrote:
>> Does your XML validate?
>
> I'm not sure, how does one validate the XML of a
bric_soap output?

Oh, I read too fast before...
What command are you doing, exactly?
The error is coming from XML::Writer. In Bric::SOAP::Util:

     $writer->dataElement("data", $data,
                          element =>
$element->get_key_name,
                          order   =>
$element->get_place - $diff);

Presumably we're handling something wrong, though I don't
know
what the correct unicode-handling would be.

To the workaround:
Which story is failing? What's different about it,
like it has a weird character I guess? (Elementary, my dear
Watson.)
Can you export it with bric_soap? (I'd guess not.)

On Mar 20, 2007, at 10:42, Matt Rolf wrote:

> So we've got some php code  - just a phpinfo() - that
we want to  
> hit on the Bricolage Apache instance. Apache comes up
as having php  
> installed, but when we hit the file, it doesn't get
rendered - we  
> just see the source.  When we start up Apache without
Bricolage,  
> php works.
>
> Is there something Bricolage does to inhibit phpness?

No, but if you're hitting the Bricolage virtual host on the
server,  
it might be disabled. Try hitting PHP on another virtual
host on the  
same box.

Best,

David

On Mar 20, 2007, at 11:24, Matt Rolf wrote:

> I didn't configure a VH when I set it up - is that the
default  
> behavior of the app?

Yes, Bricolage creates a virtual host for you.

Best,

David

>Well, Bricolage handles all requests to its domains, so
it would 
>intercept the php request and, of course, not fire it
off to PHP 
>(check the error logs).

After staring at the httpd and bricolage confs long enough,
we made 
our way to the /comp/lib/Bric/App/ApacheConfig.pm file. 
Things make 
a lot more sense now.

When we add the location in the bricolage VH, we still get
nothing. 
I'm guessing the reason is that we don't have a proper
PerlHandler 
for the php files.  Of course, this means that if you do
local 
previews, php files won't get interpreted, correct?

-- 
Matt Rolf, J.D.
Web Technology Analyst
Computing Services
Denison University
(740) 587-6537