bric_soap publishing

Not sure how to fix this:

I'm trying to create and publish a story (from crontab) via
bric_soap... I can create no problem, then manipulate in web
UI, but what I need to do is run the newly created story
through it's processing templates to do some magic
(associating stories). What's happening is I'm violating
"ck_story__publish_status" constraint. The
constraint makes sense, but the created story (as it sits in
DB isn't violating constraint (Otherwise, I guess it
wouldn't be there ;)), but trying to publish violates the
constraint ... so what am I missing to have it published and
run through it's templates?

======

OK -- this msg has now been sitting in my 'edit' queue for a
day while I looked for more info... I built a story on a
fresh 1.10.2 installation, bric_soap exported it... cp the
resulting .xml to newfile.xml, edit the newfile.xml for new
<name> and <slug>, bric_soap created a new story
with the newfile.xml, bric_soap moved it to publish desk and
then published, no problems. On this production system,
however, I get the below error msg.





Complete log msg:

[Wed Jun 20 09:39:02 2007] [error]
SOAP::Serializer::envelope: Server Application error Unable
to execute SQL statement: DBD::Pg::st execute failed: ERROR:
 new row for relation "story" violates check
constraint "ck_story__publish_status"n [for
Statement "UPDATE story SET uuid = ?, priority = ?,
source__id = ?, usr__id = ?, element_type__id = ?,
first_publish_date = ?, publish_date = ?, expire_date = ?,
current_version = ?, published_version = ?, workflow__id =
?, publish_status = ?, primary_uri = ?, active = ?, desk__id
= ?, site__id = ?, alias_id = ? WHERE id=? " with
ParamValues: 2='3', 3='1'] at
/home/tyeefish/bricolage/lib/Bric/Util/DBI.pm line 1083,
<GEN141> line 19.nnStack:n 
[/home/tyeefish/bricolage/lib/Bric/Util/DBI.pm:1083]n 
[/home/tyeefish/bricolage/lib/Bric/Biz/Asset/Business/Story.
pm:2389]n 
[/home/tyeefish/bricolage/lib/Bric/Biz/Asset/Business/Story.
pm:1865]n 
[/home/tyeefish/bricolage/data/burn/comp/oc_1/util/roundup.m
c:216]n 
[/usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/Component.pm:13
5]n 
[/home/tyeefish/bricolage/data/burn/comp/oc_1042/Newsletter/
Daily/newsletter_story.mc:49]n 
[/usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/Component.pm:13
5]n 
[/home/tyeefish/bricolage/lib/Bric/Util/Burner/Mason.pm:557]
n 
[/home/tyeefish/bricolage/data/burn/comp/oc_1042/Newsletter/
autohandler:5]n 
[/usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/Component.pm:13
5]nn[/home/tyeefish/bricolage/lib/Bric/Util/DBI.pm:1084]n
[/home/tyeefish/bricolage/lib/Bric/Biz/Asset/Business/Story.
pm:2389]n[/home/tyeefish/bricolage/lib/Bric/Biz/Asset/Busin
ess/Story.pm:1865]n[/home/tyeefish/bricolage/data/burn/comp
/oc_1/util/roundup.mc:216]n[/usr/lib/perl5/vendor_perl/5.8.
4/HTML/Mason/Component.pm:135]n[/usr/lib/perl5/vendor_perl/
5.8.4/HTML/Mason/Request.pm:1250]n[/home/tyeefish/bricolage
/data/burn/comp/oc_1042/Newsletter/Daily/newsletter_story.mc
:49]n[/usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/Component
.pm:135]n[/usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/Reque
st.pm:1255]n[/usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/Re
quest.pm:916]n[/home/tyeefish/bricolage/lib/Bric/Util/Burne
r/Mason.pm:557]n[/home/tyeefish/bricolage/data/burn/comp/oc
_1042/Newsletter/autohandler:5]n[/usr/lib/perl5/vendor_perl
/5.8.4/HTML/Mason/Component.pm:135]n[/usr/lib/perl5/vendor_
perl/5.8.4/HTML/Mason/Request.pm:1250]n[/usr/lib/perl5/vend
or_perl/5.8.4/HTML/Mason/Request.pm:461]n[/usr/lib/perl5/ve
ndor_perl/5.8.4/HTML/Mason/Interp.pm:323]n[/home/tyeefish/b
ricolage/lib/Bric/Util/Burner/Mason.pm:268]n[/home/tyeefish
/bricolage/lib/Bric/Util/Burner.pm:1493]n[/home/tyeefish/br
icolage/lib/Bric/Util/Burner.pm:1269]n[/home/tyeefish/brico
lage/lib/Bric/Util/Job/Pub.pm:191]n[/home/tyeefish/bricolag
e/lib/Bric/Util/Job.pm:1889]n[/home/tyeefish/bricolage/lib/
Bric/Util/Job.pm:1808]n[/home/tyeefish/bricolage/lib/Bric/S
OAP/Workflow.pm:294]n[/usr/lib/perl5/vendor_perl/5.8.4/SOAP
/Lite.pm:2322]n[/usr/lib/perl5/vendor_perl/5.8.4/SOAP/Trans
port/HTTP.pm:286]n[/usr/lib/perl5/vendor_perl/5.8.4/SOAP/Tr
ansport/HTTP.pm:464]n[/home/tyeefish/bricolage/lib/Bric/SOA
P/Handler.pm:169]n[PerlHandler subroutine
`Bric::SOAP::Handler::handler':1]


-- 

-bch
http://www.methodlogic.net

> Unable to execute SQL statement: DBD::Pg::st execute
failed: 
> ERROR:  new row for relation "story" violates
check constraint 
> "ck_story__publish_status"n [for Statement
"UPDATE story SET uuid = ?, 
> priority = ?, source__id = ?, usr__id = ?,
element_type__id = ?, 
> first_publish_date = ?, publish_date = ?, expire_date =
?, current_version = 
> ?, published_version = ?, workflow__id = ?,
publish_status = ?, primary_uri = 
> ?, active = ?, desk__id = ?, site__id = ?, alias_id = ?
WHERE id=? " with 
> ParamValues: 2='3', 3='1'] at
/home/tyeefish/bricolage/lib/Bric/Util/DBI.pm 
> line 1083, <GEN141> line 19.

Looks like this bug:
http://
bugs.bricolage.cc/show_bug.cgi?id=1230

If you could, please confirm the patches there.... :}

On Thu, Jun 21, 2007 at 10:10:39AM +0200, Scott Lanning
wrote:
> >Unable to execute SQL statement: DBD::Pg::st
execute failed: 
> >ERROR:  new row for relation "story"
violates check constraint 
> >"ck_story__publish_status"n [for
Statement "UPDATE story SET uuid = ?, 
> >priority = ?, source__id = ?, usr__id = ?,
element_type__id = ?, 
> >first_publish_date = ?, publish_date = ?,
expire_date = ?, current_version 
> >= ?, published_version = ?, workflow__id = ?,
publish_status = ?, 
> >primary_uri = ?, active = ?, desk__id = ?, site__id
= ?, alias_id = ? 
> >WHERE id=? " with ParamValues: 2='3', 3='1']
at 
> >/home/tyeefish/bricolage/lib/Bric/Util/DBI.pm line
1083, <GEN141> line 19.
> 
> Looks like this bug:
> http://
bugs.bricolage.cc/show_bug.cgi?id=1230
> 
> If you could, please confirm the patches there.... :}

OK -- I had to read twice to see that there's a patched
patch there, but it (seems to) work... The patches are
slightly off, and for convenience, I've attached a
combined-patch that works with the two 1.10.2 installations
I was dealing with.

The affected file is lib/Bric/Util/Burner.pm (MD5
(original_Burner.pm) = 512ac7acd0201a1745a2be14a9bea547),
and I've attached my working "combination" patch.
David's two submissions didn't _quite_ work on my copies of
the file, but is fixed in my attachment.

-- 

-bch
http://www.methodlogic.net

On Jun 22, 2007, at 04:33, brad harder wrote:

> OK -- I had to read twice to see that there's a patched
patch  
> there, but it (seems to) work... The patches are
slightly off, and  
> for convenience, I've attached a combined-patch that
works with the  
> two 1.10.2 installations I was dealing with.

Thanks. I've closed that bug report.

Best,

David