Re: Strange NULL entries in database

On Fri, 14 Sep 2007, Simon Wilcox wrote:
> Phillip Smith wrote:
>> And any new stories that I create also receive NULL
values. Has anyone 
>> experienced this behavior before? Any thoughts on
possible culprits?
>
> We've seen this, or something like it, when a job calls
publish on another 
> job. If one succeeds and the other fails, the
successful resources are 
> distributed but the failure rolls back the publish
status on all resources 
> published in that transaction. It *doesn't* then remove
the resources from 
> the site. Presumably because it doesn't know how to
roll them back to a 
> previous version and just deleting them may not be
safe.

Ugh, that could get ugly...
I don't want a headache before noon on Monday,
so I'm forgetting about this. 

So we got the following error when we tried to publish
stories from  
one of the categories in our site.  Turned out that the
problem was  
we had an identically uri'd category in another site.

The template line that caused the problem is the following:

	my $cat2 = Bric::Biz::Category->lookup({ uri =>
'/'.$categories 
[1].'/'.$secondaryCat });

Which leads to this error:

Too many Bric::Biz::Category objects found.
[/usr/local/bricolage/lib/Bric/Biz/Category.pm:275]
[/usr/local/bricolage/data/burn/comp/oc_1/css_and_topnav.mc:
71]
[/usr/local/lib/perl5/site_perl/5.8.8/HTML/Mason/Component.p
m:135]
[/usr/local/lib/perl5/site_perl/5.8.8/HTML/Mason/Request.pm:
1251]
[/usr/local/bricolage/data/burn/comp/oc_1/autohandler:62]
[/usr/local/lib/perl5/site_perl/5.8.8/HTML/Mason/Component.p
m:135]
[/usr/local/lib/perl5/site_perl/5.8.8/HTML/Mason/Request.pm:
1251]
[/usr/local/lib/perl5/site_perl/5.8.8/HTML/Mason/Request.pm:
460]
[/usr/local/lib/perl5/site_perl/5.8.8/HTML/Mason/Interp.pm:3
42]
[/usr/local/bricolage/lib/Bric/Util/Burner/Mason.pm:268]
[/usr/local/bricolage/lib/Bric/Util/Burner.pm:1586]
[/usr/local/bricolage/lib/Bric/Util/Burner.pm:1362]
[/usr/local/bricolage/lib/Bric/Util/Job/Pub.pm:191]
[/usr/local/bricolage/lib/Bric/Util/Job.pm:1889]
[/usr/local/bricolage/bin/bric_queued:245]
[/usr/local/bricolage/bin/bric_queued:214]

Looks like we can fix it by using this?

list Bric::Biz::Category($crit);

Would it be useful to have the first call by default look in
the site  
the template's being run in?

-Matt

On Sep 17, 2007, at 01:50, Scott Lanning wrote:

> Ugh, that could get ugly...
> I don't want a headache before noon on Monday,
> so I'm forgetting about this. 

The upshot is that distribution is not in the transaction.
There's no  
way to roll it back. The way that transactionality works in 

publishing should probably be re-evaluated.

Best,

David