I've seen that before, but not with deleted stories. Active
stories
that end up with multiple rows tend to show up twice in the
UI and lead
to all sorts of problems with current desk, etc. I've not
been able to
determine what leads to this condition in the first place
though.
-----Original Message-----
From: Matt Rolf [mailto:rolfm denison.edu]
Sent: Tuesday, August 14, 2007 2:27 PM
To: userslists.bricolage.cc
Subject: Re: Soap and Interface unable to find story
Aha! Perhaps this is it. Missing stories have 2 entries
in the
member row.
-Matt
On Aug 14, 2007, at 12:42 PM, Lanning, Scott wrote:
> Unf.... maybe it's something to do with the member
table.
>
> We know the story has id = 6747.
>
> select * from story_member where object_id = 6747;
>
> That returns a row.
>
> select * from member where id in
> (select member__id from story_member where object_id =
6747);
>
> That should return at least one, maybe two rows.
> You can check which groups they are with
>
> select * from grp where id in
> (select grp__id from member where id in
> (select member__id from story_member where object_id
= 6747));
>
> It should at least have 'All Stories' and sometimes it
has a desk one.
> If the member row is missing for some reason, I think
that makes
> the story not show up. If so, maybe you can try to
reconstruct
> the story's member rows.... or eliminate it altogether
from the
> database....
>
> Then again, maybe it's something simpler. 
>
> -----Original Message-----
> From: Matt Rolf [mailto:rolfmdenison.edu]
> Sent: Tue 8/14/2007 6:18 PM
> To: userslists.bricolage.cc
> Subject: Re: Soap and Interface unable to find story
>
> Nope, active = "t"
>
>
> On Aug 14, 2007, at 12:09 PM, Lanning, Scott wrote:
>
>> It seems "normal" to me, for a story
that's been "deleted".
>> Presumably in the 'story' table, active = 'f' ?
>>
>> [sucky outlook web interface....]
>> -----Original Message-----
>> From: Matt Rolf [mailto:rolfmdenison.edu]
>> Sent: Tue 8/14/2007 5:51 PM
>> To: userslists.bricolage.cc
>> Subject: Soap and Interface unable to find story
>>
>> We are having an interesting error where we have
stories that in the
>> past were published, but now have disappeared from
the interface.
>> SOAP is also unable to find them. However, when we
try to create
>> stories which overwrite their uris, the system
suddenly says, hey,
>> you can't do that, there's already a story by that
name there.
>>
>> In the database, the "missing" stories
are all there in the story,
>> story_instance, and story_uri tables.
>>
>> The SOAP error we get when we try to publish one of
the missing
>> stories is as follows:
>>
>> # /usr/local/bricolage/bin/bric_soap --username
rolfm workflow
>> publish story_6747
>> Password:
>> Call to Bric::SOAP::Workflow->publish failed:
>>
>> Unable to find story for story_id
"6747".
>>
>> Check the Apache error log for more detail.
>>
>> *****
>>
>> [Tue Aug 14 15:45:34 2007] [error]
SOAP::Serializer::envelope: Server
>> Application error Unable to find story for story_id
"6747".n[/usr/
>>
local/bricolage/lib/Bric/SOAP/Workflow.pm:212]n[/usr/local/
lib/
>> perl5/
>>
site_perl/5.8.8/SOAP/Lite.pm:2569]n[/usr/local/lib/perl5/si
te_perl/
>>
5.8.8/SOAP/Transport/HTTP.pm:327]n[/usr/local/lib/perl5/sit
e_perl/
>>
5.8.8/SOAP/Transport/HTTP.pm:621]n[/usr/local/bricolage/lib
/Bric/
>> SOAP/Handler.pm:169]
>>
[/usr/local/bricolage/lib/Bric/SOAP/Handler.pm:249]
>>
[/usr/local/lib/perl5/site_perl/5.8.8/SOAP/Lite.pm:2649]
>>
[/usr/local/lib/perl5/site_perl/5.8.8/SOAP/Lite.pm:1505]
>>
[/usr/local/lib/perl5/site_perl/5.8.8/SOAP/Lite.pm:761]
>>
[/usr/local/lib/perl5/site_perl/5.8.8/SOAP/Lite.pm:2624]
>>
[/usr/local/lib/perl5/site_perl/5.8.8/SOAP/Transport/HTTP.pm
:338]
>>
[/usr/local/lib/perl5/site_perl/5.8.8/SOAP/Lite.pm:2617]
>>
[/usr/local/lib/perl5/site_perl/5.8.8/SOAP/Transport/HTTP.pm
:327]
>>
[/usr/local/lib/perl5/site_perl/5.8.8/SOAP/Transport/HTTP.pm
:621]
>>
[/usr/local/bricolage/lib/Bric/SOAP/Handler.pm:169]
>>
>>
>> The only similar type issue thread I found was this
one
>>
>> http://marc.info/?l=bricolage-general&m=1
10617074930348&w=2
>>
>> but that seems to be a completely different type of
problem. Any
>> suggestions? I'll be happy to provide whatever
information I can if
>> it is needed
>>
>> Thanks very much,
>>
>> Matt
>>
>
>
|