Mailing List Archive

Tom,
Try looking at the story table to see if the story you are having trouble with is confused:
select id, usr__id, primary_uri, workflow__id, desk__id from story
where id=$story_id

There should only be a user__id value if there is also a workflow__id and desk__id greater than 0. I suspect that you will find there is a usr__id, but not the others.

If this is the case, you should try changing the usr__id to ''(blank), and have Nick Harvey try to check the story out and back in again.

Of course, hacking into the database is not without risk, so please backup and backup again before trying to manually update anything.

Adam
RFX Technologies

-----Original Message-----
From: users@lists.bricolagecms.org [mailto:users@lists.bricolagecms.org] On Behalf Of Tom Ash
Sent: Tuesday, April 24, 2012 6:47 AM
To: users@lists.bricolagecms.org
Cc: Charlie Harvey; Nick Harvey
Subject: Unable to check in story which is checked out, but thinks it's not

Hi,

We have a story on our site ('front page' - so a fairly important one) which shows up as checked out to one of our users ('Nick Harvey') but which he can't check in in any way (whether he chooses 'Check in and Publish' or 'Check in and Shelve' or 'Check in to [Other User]' or whatever). When he does so Bric gives the following error:

==
Cannot checkin non checked out versions

Error Details (hide)

Fault Class
Bric::Util::Fault::Exception::GEN
Description
General Exception
Timestamp
2012-04-24 03:18:09.000000
Package
Bric::Biz::Asset
Filename
/home/newint/bricolage2/lib/Bric/Biz/Asset.pm
Line
1738
Stack:

Trace begun at /home/newint/bricolage2/lib/Bric/Biz/Asset.pm line 1738
Bric::Biz::Asset::checkin('Bric::Biz::Asset::Business::Story=HASH(0x63986b0)') called at /home/newint/bricolage2/lib/Bric/App/Callback/Profile/Story.pm line 152
Bric::App::Callback::Profile::Story::checkin('Bric::App::Callback::Profile::Story=HASH(0x73cd180)') called at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 296 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 286 Params::CallbackRequest::request('Params::CallbackRequest=HASH(0x3708660)', 'HASH(0x4279500)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/MasonX/Interp/WithCallbacks.pm line 115 MasonX::Interp::WithCallbacks::make_request('MasonX::Interp::WithCallbacks=HASH(0x51ae770)', 'comp', '/workflow/profile/story/2308', 'args', 'ARRAY(0x7cef700)', 'ah', 'HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 868 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 867 HTML::Mason::ApacheHandler::prepare_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 822 HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 307 eval {...} at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 296
Bric::App::Handler::handler('Apache=SCALAR(0x550ed50)') called at PerlHandler subroutine `Bric::App::Handler::handler' line 1 eval {...} at PerlHandler subroutine `Bric::App::Handler::handler' line 1 Please report this error to your administrator. It may be helpful to include the error details in your report.
==

I'm not sure how to resolve this. It looks like Bric has got confused as to the checkin status of the story, and we'd need to reset this, but I'm not sure how. Is this something I can change in Bric's database, and if so in what table?

One possibly relevant factor is that I have a script running right now that's republishing this page frequently through bric_soap (because it's republishing the whole site to reflect some template changes, and our templates often republish the front page when another story is published). However, I've run that script before while users have checked the offending 'front page' story in and out with no problem.

Any pointers?

Thanks!
Tom

Thanks Adam, v useful to hear from someone who knows the database structure.

The 'front page' story has id 2308. But what I see when I run `select id, usr__id, primary_uri, workflow__id, desk__id from story where id=2308;` is:

id | usr__id | primary_uri | workflow__id | desk__id
------+---------+-------------+--------------+----------
2308 | 2450 | / | 101 | 101
(1 row)

Which is just what I see when I try checking out story id 3888 (plucked at random as a test case) myself:

id | usr__id | primary_uri | workflow__id | desk__id
------+---------+---------------------+--------------+----------
3888 | 2298 | /issues/1979/09/01/ | 101 | 101
(1 row)

Whereas when this is not checked out I see 0 for the last two columns, as you say:

id | usr__id | primary_uri | workflow__id | desk__id
------+---------+---------------------+--------------+----------
3888 | | /issues/1979/09/01/ | 0 | 0
(1 row)

Where can I go from here? :S

Thanks,
Tom


On 24 Apr 2012, at 13:48, Adam Wilson wrote:

> Tom,
> Try looking at the story table to see if the story you are having trouble with is confused:
> select id, usr__id, primary_uri, workflow__id, desk__id from story
> where id=$story_id
>
> There should only be a user__id value if there is also a workflow__id and desk__id greater than 0. I suspect that you will find there is a usr__id, but not the others.
>
> If this is the case, you should try changing the usr__id to ''(blank), and have Nick Harvey try to check the story out and back in again.
>
> Of course, hacking into the database is not without risk, so please backup and backup again before trying to manually update anything.
>
> Adam
> RFX Technologies
>
> -----Original Message-----
> From: users@lists.bricolagecms.org [mailto:users@lists.bricolagecms.org] On Behalf Of Tom Ash
> Sent: Tuesday, April 24, 2012 6:47 AM
> To: users@lists.bricolagecms.org
> Cc: Charlie Harvey; Nick Harvey
> Subject: Unable to check in story which is checked out, but thinks it's not
>
> Hi,
>
> We have a story on our site ('front page' - so a fairly important one) which shows up as checked out to one of our users ('Nick Harvey') but which he can't check in in any way (whether he chooses 'Check in and Publish' or 'Check in and Shelve' or 'Check in to [Other User]' or whatever). When he does so Bric gives the following error:
>
> ==
> Cannot checkin non checked out versions
>
> Error Details (hide)
>
> Fault Class
> Bric::Util::Fault::Exception::GEN
> Description
> General Exception
> Timestamp
> 2012-04-24 03:18:09.000000
> Package
> Bric::Biz::Asset
> Filename
> /home/newint/bricolage2/lib/Bric/Biz/Asset.pm
> Line
> 1738
> Stack:
>
> Trace begun at /home/newint/bricolage2/lib/Bric/Biz/Asset.pm line 1738
> Bric::Biz::Asset::checkin('Bric::Biz::Asset::Business::Story=HASH(0x63986b0)') called at /home/newint/bricolage2/lib/Bric/App/Callback/Profile/Story.pm line 152
> Bric::App::Callback::Profile::Story::checkin('Bric::App::Callback::Profile::Story=HASH(0x73cd180)') called at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 296 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 286 Params::CallbackRequest::request('Params::CallbackRequest=HASH(0x3708660)', 'HASH(0x4279500)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/MasonX/Interp/WithCallbacks.pm line 115 MasonX::Interp::WithCallbacks::make_request('MasonX::Interp::WithCallbacks=HASH(0x51ae770)', 'comp', '/workflow/profile/story/2308', 'args', 'ARRAY(0x7cef700)', 'ah', 'HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 868 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 867 HTML::Mason::ApacheHandler::prepare_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 822 HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 307 eval {...} at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 296
> Bric::App::Handler::handler('Apache=SCALAR(0x550ed50)') called at PerlHandler subroutine `Bric::App::Handler::handler' line 1 eval {...} at PerlHandler subroutine `Bric::App::Handler::handler' line 1 Please report this error to your administrator. It may be helpful to include the error details in your report.
> ==
>
> I'm not sure how to resolve this. It looks like Bric has got confused as to the checkin status of the story, and we'd need to reset this, but I'm not sure how. Is this something I can change in Bric's database, and if so in what table?
>
> One possibly relevant factor is that I have a script running right now that's republishing this page frequently through bric_soap (because it's republishing the whole site to reflect some template changes, and our templates often republish the front page when another story is published). However, I've run that script before while users have checked the offending 'front page' story in and out with no problem.
>
> Any pointers?
>
> Thanks!
> Tom

Hi Tom,

Now look at the most recent records in story_instance:

SELECT * FROM story_instance WHERE story__id = 2308 ORDER BY id DESC
LIMIT 5;

Here, you'll see the latest versions of the front page. If a story is
checked out correctly, you'll see two records with the same version id:
one checked in and one checked out.

If you don't see that, write back and let us know what you do see.

Hope this helps,

Bret


--
Bret Dawson
Producer
Pectopah Productions Inc.
(416) 895-7635
bret@pectopah.com
www.pectopah.com


On Tue, 2012-04-24 at 14:06 +0100, Tom Ash wrote:
> Thanks Adam, v useful to hear from someone who knows the database structure.
>
> The 'front page' story has id 2308. But what I see when I run `select id, usr__id, primary_uri, workflow__id, desk__id from story where id=2308;` is:
>
> id | usr__id | primary_uri | workflow__id | desk__id
> ------+---------+-------------+--------------+----------
> 2308 | 2450 | / | 101 | 101
> (1 row)
>
> Which is just what I see when I try checking out story id 3888 (plucked at random as a test case) myself:
>
> id | usr__id | primary_uri | workflow__id | desk__id
> ------+---------+---------------------+--------------+----------
> 3888 | 2298 | /issues/1979/09/01/ | 101 | 101
> (1 row)
>
> Whereas when this is not checked out I see 0 for the last two columns, as you say:
>
> id | usr__id | primary_uri | workflow__id | desk__id
> ------+---------+---------------------+--------------+----------
> 3888 | | /issues/1979/09/01/ | 0 | 0
> (1 row)
>
> Where can I go from here? :S
>
> Thanks,
> Tom
>
>
> On 24 Apr 2012, at 13:48, Adam Wilson wrote:
>
> > Tom,
> > Try looking at the story table to see if the story you are having trouble with is confused:
> > select id, usr__id, primary_uri, workflow__id, desk__id from story
> > where id=$story_id
> >
> > There should only be a user__id value if there is also a workflow__id and desk__id greater than 0. I suspect that you will find there is a usr__id, but not the others.
> >
> > If this is the case, you should try changing the usr__id to ''(blank), and have Nick Harvey try to check the story out and back in again.
> >
> > Of course, hacking into the database is not without risk, so please backup and backup again before trying to manually update anything.
> >
> > Adam
> > RFX Technologies
> >
> > -----Original Message-----
> > From: users@lists.bricolagecms.org [mailto:users@lists.bricolagecms.org] On Behalf Of Tom Ash
> > Sent: Tuesday, April 24, 2012 6:47 AM
> > To: users@lists.bricolagecms.org
> > Cc: Charlie Harvey; Nick Harvey
> > Subject: Unable to check in story which is checked out, but thinks it's not
> >
> > Hi,
> >
> > We have a story on our site ('front page' - so a fairly important one) which shows up as checked out to one of our users ('Nick Harvey') but which he can't check in in any way (whether he chooses 'Check in and Publish' or 'Check in and Shelve' or 'Check in to [Other User]' or whatever). When he does so Bric gives the following error:
> >
> > ==
> > Cannot checkin non checked out versions
> >
> > Error Details (hide)
> >
> > Fault Class
> > Bric::Util::Fault::Exception::GEN
> > Description
> > General Exception
> > Timestamp
> > 2012-04-24 03:18:09.000000
> > Package
> > Bric::Biz::Asset
> > Filename
> > /home/newint/bricolage2/lib/Bric/Biz/Asset.pm
> > Line
> > 1738
> > Stack:
> >
> > Trace begun at /home/newint/bricolage2/lib/Bric/Biz/Asset.pm line 1738
> > Bric::Biz::Asset::checkin('Bric::Biz::Asset::Business::Story=HASH(0x63986b0)') called at /home/newint/bricolage2/lib/Bric/App/Callback/Profile/Story.pm line 152
> > Bric::App::Callback::Profile::Story::checkin('Bric::App::Callback::Profile::Story=HASH(0x73cd180)') called at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 296 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 286 Params::CallbackRequest::request('Params::CallbackRequest=HASH(0x3708660)', 'HASH(0x4279500)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/MasonX/Interp/WithCallbacks.pm line 115 MasonX::Interp::WithCallbacks::make_request('MasonX::Interp::WithCallbacks=HASH(0x51ae770)', 'comp', '/workflow/profile/story/2308', 'args', 'ARRAY(0x7cef700)', 'ah', 'HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 868 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 867 HTML::Mason::ApacheHandler::prepare_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 822 HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 307 eval {...} at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 296
> > Bric::App::Handler::handler('Apache=SCALAR(0x550ed50)') called at PerlHandler subroutine `Bric::App::Handler::handler' line 1 eval {...} at PerlHandler subroutine `Bric::App::Handler::handler' line 1 Please report this error to your administrator. It may be helpful to include the error details in your report.
> > ==
> >
> > I'm not sure how to resolve this. It looks like Bric has got confused as to the checkin status of the story, and we'd need to reset this, but I'm not sure how. Is this something I can change in Bric's database, and if so in what table?
> >
> > One possibly relevant factor is that I have a script running right now that's republishing this page frequently through bric_soap (because it's republishing the whole site to reflect some template changes, and our templates often republish the front page when another story is published). However, I've run that script before while users have checked the offending 'front page' story in and out with no problem.
> >
> > Any pointers?
> >
> > Thanks!
> > Tom
>
>

Thanks Bret, I don't see that - I see *5* versions of the story and all have the checked_out field set to 'f':

newint2=> SELECT * FROM story_instance WHERE story__id = 2308 ORDER BY id DESC LIMIT 5;
id | name | description | story__id | version | usr__id | slug | primary_oc__id | checked_out | note | cover_date
-------+-------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------+---------+---------+------+----------------+-------------+------+---------------------
58956 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 719 | 2450 | | 1 | f | | 2010-07-21 19:59:00
58908 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 718 | 2298 | | 1 | f | | 2010-07-21 19:59:00
58898 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 717 | 2450 | | 1 | f | | 2010-07-21 19:59:00
58870 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 716 | 1135 | | 1 | f | | 2010-07-21 19:59:00
58826 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 715 | 2450 | | 1 | f | | 2010-07-21 19:59:00
(5 rows)


On 24 Apr 2012, at 14:16, Bret Dawson wrote:

> Hi Tom,
>
> Now look at the most recent records in story_instance:
>
> SELECT * FROM story_instance WHERE story__id = 2308 ORDER BY id DESC
> LIMIT 5;
>
> Here, you'll see the latest versions of the front page. If a story is
> checked out correctly, you'll see two records with the same version id:
> one checked in and one checked out.
>
> If you don't see that, write back and let us know what you do see.
>
> Hope this helps,
>
> Bret
>
>
> --
> Bret Dawson
> Producer
> Pectopah Productions Inc.
> (416) 895-7635
> bret@pectopah.com
> www.pectopah.com
>
>
> On Tue, 2012-04-24 at 14:06 +0100, Tom Ash wrote:
>> Thanks Adam, v useful to hear from someone who knows the database structure.
>>
>> The 'front page' story has id 2308. But what I see when I run `select id, usr__id, primary_uri, workflow__id, desk__id from story where id=2308;` is:
>>
>> id | usr__id | primary_uri | workflow__id | desk__id
>> ------+---------+-------------+--------------+----------
>> 2308 | 2450 | / | 101 | 101
>> (1 row)
>>
>> Which is just what I see when I try checking out story id 3888 (plucked at random as a test case) myself:
>>
>> id | usr__id | primary_uri | workflow__id | desk__id
>> ------+---------+---------------------+--------------+----------
>> 3888 | 2298 | /issues/1979/09/01/ | 101 | 101
>> (1 row)
>>
>> Whereas when this is not checked out I see 0 for the last two columns, as you say:
>>
>> id | usr__id | primary_uri | workflow__id | desk__id
>> ------+---------+---------------------+--------------+----------
>> 3888 | | /issues/1979/09/01/ | 0 | 0
>> (1 row)
>>
>> Where can I go from here? :S
>>
>> Thanks,
>> Tom
>>
>>
>> On 24 Apr 2012, at 13:48, Adam Wilson wrote:
>>
>>> Tom,
>>> Try looking at the story table to see if the story you are having trouble with is confused:
>>> select id, usr__id, primary_uri, workflow__id, desk__id from story
>>> where id=$story_id
>>>
>>> There should only be a user__id value if there is also a workflow__id and desk__id greater than 0. I suspect that you will find there is a usr__id, but not the others.
>>>
>>> If this is the case, you should try changing the usr__id to ''(blank), and have Nick Harvey try to check the story out and back in again.
>>>
>>> Of course, hacking into the database is not without risk, so please backup and backup again before trying to manually update anything.
>>>
>>> Adam
>>> RFX Technologies
>>>
>>> -----Original Message-----
>>> From: users@lists.bricolagecms.org [mailto:users@lists.bricolagecms.org] On Behalf Of Tom Ash
>>> Sent: Tuesday, April 24, 2012 6:47 AM
>>> To: users@lists.bricolagecms.org
>>> Cc: Charlie Harvey; Nick Harvey
>>> Subject: Unable to check in story which is checked out, but thinks it's not
>>>
>>> Hi,
>>>
>>> We have a story on our site ('front page' - so a fairly important one) which shows up as checked out to one of our users ('Nick Harvey') but which he can't check in in any way (whether he chooses 'Check in and Publish' or 'Check in and Shelve' or 'Check in to [Other User]' or whatever). When he does so Bric gives the following error:
>>>
>>> ==
>>> Cannot checkin non checked out versions
>>>
>>> Error Details (hide)
>>>
>>> Fault Class
>>> Bric::Util::Fault::Exception::GEN
>>> Description
>>> General Exception
>>> Timestamp
>>> 2012-04-24 03:18:09.000000
>>> Package
>>> Bric::Biz::Asset
>>> Filename
>>> /home/newint/bricolage2/lib/Bric/Biz/Asset.pm
>>> Line
>>> 1738
>>> Stack:
>>>
>>> Trace begun at /home/newint/bricolage2/lib/Bric/Biz/Asset.pm line 1738
>>> Bric::Biz::Asset::checkin('Bric::Biz::Asset::Business::Story=HASH(0x63986b0)') called at /home/newint/bricolage2/lib/Bric/App/Callback/Profile/Story.pm line 152
>>> Bric::App::Callback::Profile::Story::checkin('Bric::App::Callback::Profile::Story=HASH(0x73cd180)') called at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 296 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 286 Params::CallbackRequest::request('Params::CallbackRequest=HASH(0x3708660)', 'HASH(0x4279500)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/MasonX/Interp/WithCallbacks.pm line 115 MasonX::Interp::WithCallbacks::make_request('MasonX::Interp::WithCallbacks=HASH(0x51ae770)', 'comp', '/workflow/profile/story/2308', 'args', 'ARRAY(0x7cef700)', 'ah', 'HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 868 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 867 HTML::Mason::ApacheHandler::prepare_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 822 HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 307 eval {...} at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 296
>>> Bric::App::Handler::handler('Apache=SCALAR(0x550ed50)') called at PerlHandler subroutine `Bric::App::Handler::handler' line 1 eval {...} at PerlHandler subroutine `Bric::App::Handler::handler' line 1 Please report this error to your administrator. It may be helpful to include the error details in your report.
>>> ==
>>>
>>> I'm not sure how to resolve this. It looks like Bric has got confused as to the checkin status of the story, and we'd need to reset this, but I'm not sure how. Is this something I can change in Bric's database, and if so in what table?
>>>
>>> One possibly relevant factor is that I have a script running right now that's republishing this page frequently through bric_soap (because it's republishing the whole site to reflect some template changes, and our templates often republish the front page when another story is published). However, I've run that script before while users have checked the offending 'front page' story in and out with no problem.
>>>
>>> Any pointers?
>>>
>>> Thanks!
>>> Tom
>>
>>
>

Hi Tom,

OK, that's your problem. Version 719 is the current one, but it's not
actually checked out, and the story table has it wrong. So try this:

UPDATE story SET usr__id = NULL WHERE id = 2308;

Then, when you do a search for that story, you should be able to
actually check it out, and then check it in and publish it.

Hope this helps,

Bret


--
Bret Dawson
Producer
Pectopah Productions Inc.
(416) 895-7635
bret@pectopah.com
www.pectopah.com


On Tue, 2012-04-24 at 14:50 +0100, Tom Ash wrote:
> Thanks Bret, I don't see that - I see *5* versions of the story and all have the checked_out field set to 'f':
>
> newint2=> SELECT * FROM story_instance WHERE story__id = 2308 ORDER BY id DESC LIMIT 5;
> id | name | description | story__id | version | usr__id | slug | primary_oc__id | checked_out | note | cover_date
> -------+-------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------+---------+---------+------+----------------+-------------+------+---------------------
> 58956 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 719 | 2450 | | 1 | f | | 2010-07-21 19:59:00
> 58908 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 718 | 2298 | | 1 | f | | 2010-07-21 19:59:00
> 58898 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 717 | 2450 | | 1 | f | | 2010-07-21 19:59:00
> 58870 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 716 | 1135 | | 1 | f | | 2010-07-21 19:59:00
> 58826 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 715 | 2450 | | 1 | f | | 2010-07-21 19:59:00
> (5 rows)
>
>
> On 24 Apr 2012, at 14:16, Bret Dawson wrote:
>
> > Hi Tom,
> >
> > Now look at the most recent records in story_instance:
> >
> > SELECT * FROM story_instance WHERE story__id = 2308 ORDER BY id DESC
> > LIMIT 5;
> >
> > Here, you'll see the latest versions of the front page. If a story is
> > checked out correctly, you'll see two records with the same version id:
> > one checked in and one checked out.
> >
> > If you don't see that, write back and let us know what you do see.
> >
> > Hope this helps,
> >
> > Bret
> >
> >
> > --
> > Bret Dawson
> > Producer
> > Pectopah Productions Inc.
> > (416) 895-7635
> > bret@pectopah.com
> > www.pectopah.com
> >
> >
> > On Tue, 2012-04-24 at 14:06 +0100, Tom Ash wrote:
> >> Thanks Adam, v useful to hear from someone who knows the database structure.
> >>
> >> The 'front page' story has id 2308. But what I see when I run `select id, usr__id, primary_uri, workflow__id, desk__id from story where id=2308;` is:
> >>
> >> id | usr__id | primary_uri | workflow__id | desk__id
> >> ------+---------+-------------+--------------+----------
> >> 2308 | 2450 | / | 101 | 101
> >> (1 row)
> >>
> >> Which is just what I see when I try checking out story id 3888 (plucked at random as a test case) myself:
> >>
> >> id | usr__id | primary_uri | workflow__id | desk__id
> >> ------+---------+---------------------+--------------+----------
> >> 3888 | 2298 | /issues/1979/09/01/ | 101 | 101
> >> (1 row)
> >>
> >> Whereas when this is not checked out I see 0 for the last two columns, as you say:
> >>
> >> id | usr__id | primary_uri | workflow__id | desk__id
> >> ------+---------+---------------------+--------------+----------
> >> 3888 | | /issues/1979/09/01/ | 0 | 0
> >> (1 row)
> >>
> >> Where can I go from here? :S
> >>
> >> Thanks,
> >> Tom
> >>
> >>
> >> On 24 Apr 2012, at 13:48, Adam Wilson wrote:
> >>
> >>> Tom,
> >>> Try looking at the story table to see if the story you are having trouble with is confused:
> >>> select id, usr__id, primary_uri, workflow__id, desk__id from story
> >>> where id=$story_id
> >>>
> >>> There should only be a user__id value if there is also a workflow__id and desk__id greater than 0. I suspect that you will find there is a usr__id, but not the others.
> >>>
> >>> If this is the case, you should try changing the usr__id to ''(blank), and have Nick Harvey try to check the story out and back in again.
> >>>
> >>> Of course, hacking into the database is not without risk, so please backup and backup again before trying to manually update anything.
> >>>
> >>> Adam
> >>> RFX Technologies
> >>>
> >>> -----Original Message-----
> >>> From: users@lists.bricolagecms.org [mailto:users@lists.bricolagecms.org] On Behalf Of Tom Ash
> >>> Sent: Tuesday, April 24, 2012 6:47 AM
> >>> To: users@lists.bricolagecms.org
> >>> Cc: Charlie Harvey; Nick Harvey
> >>> Subject: Unable to check in story which is checked out, but thinks it's not
> >>>
> >>> Hi,
> >>>
> >>> We have a story on our site ('front page' - so a fairly important one) which shows up as checked out to one of our users ('Nick Harvey') but which he can't check in in any way (whether he chooses 'Check in and Publish' or 'Check in and Shelve' or 'Check in to [Other User]' or whatever). When he does so Bric gives the following error:
> >>>
> >>> ==
> >>> Cannot checkin non checked out versions
> >>>
> >>> Error Details (hide)
> >>>
> >>> Fault Class
> >>> Bric::Util::Fault::Exception::GEN
> >>> Description
> >>> General Exception
> >>> Timestamp
> >>> 2012-04-24 03:18:09.000000
> >>> Package
> >>> Bric::Biz::Asset
> >>> Filename
> >>> /home/newint/bricolage2/lib/Bric/Biz/Asset.pm
> >>> Line
> >>> 1738
> >>> Stack:
> >>>
> >>> Trace begun at /home/newint/bricolage2/lib/Bric/Biz/Asset.pm line 1738
> >>> Bric::Biz::Asset::checkin('Bric::Biz::Asset::Business::Story=HASH(0x63986b0)') called at /home/newint/bricolage2/lib/Bric/App/Callback/Profile/Story.pm line 152
> >>> Bric::App::Callback::Profile::Story::checkin('Bric::App::Callback::Profile::Story=HASH(0x73cd180)') called at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 296 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 286 Params::CallbackRequest::request('Params::CallbackRequest=HASH(0x3708660)', 'HASH(0x4279500)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/MasonX/Interp/WithCallbacks.pm line 115 MasonX::Interp::WithCallbacks::make_request('MasonX::Interp::WithCallbacks=HASH(0x51ae770)', 'comp', '/workflow/profile/story/2308', 'args', 'ARRAY(0x7cef700)', 'ah', 'HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 868 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 867 HTML::Mason::ApacheHandler::prepare_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 822 HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 307 eval {...} at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 296
> >>> Bric::App::Handler::handler('Apache=SCALAR(0x550ed50)') called at PerlHandler subroutine `Bric::App::Handler::handler' line 1 eval {...} at PerlHandler subroutine `Bric::App::Handler::handler' line 1 Please report this error to your administrator. It may be helpful to include the error details in your report.
> >>> ==
> >>>
> >>> I'm not sure how to resolve this. It looks like Bric has got confused as to the checkin status of the story, and we'd need to reset this, but I'm not sure how. Is this something I can change in Bric's database, and if so in what table?
> >>>
> >>> One possibly relevant factor is that I have a script running right now that's republishing this page frequently through bric_soap (because it's republishing the whole site to reflect some template changes, and our templates often republish the front page when another story is published). However, I've run that script before while users have checked the offending 'front page' story in and out with no problem.
> >>>
> >>> Any pointers?
> >>>
> >>> Thanks!
> >>> Tom
> >>
> >>
> >
>
>

That fixes it! Thanks Bret (and Adam)...

Great mailing list...
Tom

On 24 Apr 2012, at 14:55, Bret Dawson wrote:

> Hi Tom,
>
> OK, that's your problem. Version 719 is the current one, but it's not
> actually checked out, and the story table has it wrong. So try this:
>
> UPDATE story SET usr__id = NULL WHERE id = 2308;
>
> Then, when you do a search for that story, you should be able to
> actually check it out, and then check it in and publish it.
>
> Hope this helps,
>
> Bret
>
>
> --
> Bret Dawson
> Producer
> Pectopah Productions Inc.
> (416) 895-7635
> bret@pectopah.com
> www.pectopah.com
>
>
> On Tue, 2012-04-24 at 14:50 +0100, Tom Ash wrote:
>> Thanks Bret, I don't see that - I see *5* versions of the story and all have the checked_out field set to 'f':
>>
>> newint2=> SELECT * FROM story_instance WHERE story__id = 2308 ORDER BY id DESC LIMIT 5;
>> id | name | description | story__id | version | usr__id | slug | primary_oc__id | checked_out | note | cover_date
>> -------+-------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------+---------+---------+------+----------------+-------------+------+---------------------
>> 58956 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 719 | 2450 | | 1 | f | | 2010-07-21 19:59:00
>> 58908 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 718 | 2298 | | 1 | f | | 2010-07-21 19:59:00
>> 58898 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 717 | 2450 | | 1 | f | | 2010-07-21 19:59:00
>> 58870 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 716 | 1135 | | 1 | f | | 2010-07-21 19:59:00
>> 58826 | The people, the ideas, the action in the fight for global justice | New Internationalist is the world's leading independent publisher of magazines and books on global social justice and sustainable development. Our online shop features fair trade, organic, eco friendly and recycled gifts and treats from around the world. Our blog is packed with perspectives from the majority world and stories from the frontline of activism. | 2308 | 715 | 2450 | | 1 | f | | 2010-07-21 19:59:00
>> (5 rows)
>>
>>
>> On 24 Apr 2012, at 14:16, Bret Dawson wrote:
>>
>>> Hi Tom,
>>>
>>> Now look at the most recent records in story_instance:
>>>
>>> SELECT * FROM story_instance WHERE story__id = 2308 ORDER BY id DESC
>>> LIMIT 5;
>>>
>>> Here, you'll see the latest versions of the front page. If a story is
>>> checked out correctly, you'll see two records with the same version id:
>>> one checked in and one checked out.
>>>
>>> If you don't see that, write back and let us know what you do see.
>>>
>>> Hope this helps,
>>>
>>> Bret
>>>
>>>
>>> --
>>> Bret Dawson
>>> Producer
>>> Pectopah Productions Inc.
>>> (416) 895-7635
>>> bret@pectopah.com
>>> www.pectopah.com
>>>
>>>
>>> On Tue, 2012-04-24 at 14:06 +0100, Tom Ash wrote:
>>>> Thanks Adam, v useful to hear from someone who knows the database structure.
>>>>
>>>> The 'front page' story has id 2308. But what I see when I run `select id, usr__id, primary_uri, workflow__id, desk__id from story where id=2308;` is:
>>>>
>>>> id | usr__id | primary_uri | workflow__id | desk__id
>>>> ------+---------+-------------+--------------+----------
>>>> 2308 | 2450 | / | 101 | 101
>>>> (1 row)
>>>>
>>>> Which is just what I see when I try checking out story id 3888 (plucked at random as a test case) myself:
>>>>
>>>> id | usr__id | primary_uri | workflow__id | desk__id
>>>> ------+---------+---------------------+--------------+----------
>>>> 3888 | 2298 | /issues/1979/09/01/ | 101 | 101
>>>> (1 row)
>>>>
>>>> Whereas when this is not checked out I see 0 for the last two columns, as you say:
>>>>
>>>> id | usr__id | primary_uri | workflow__id | desk__id
>>>> ------+---------+---------------------+--------------+----------
>>>> 3888 | | /issues/1979/09/01/ | 0 | 0
>>>> (1 row)
>>>>
>>>> Where can I go from here? :S
>>>>
>>>> Thanks,
>>>> Tom
>>>>
>>>>
>>>> On 24 Apr 2012, at 13:48, Adam Wilson wrote:
>>>>
>>>>> Tom,
>>>>> Try looking at the story table to see if the story you are having trouble with is confused:
>>>>> select id, usr__id, primary_uri, workflow__id, desk__id from story
>>>>> where id=$story_id
>>>>>
>>>>> There should only be a user__id value if there is also a workflow__id and desk__id greater than 0. I suspect that you will find there is a usr__id, but not the others.
>>>>>
>>>>> If this is the case, you should try changing the usr__id to ''(blank), and have Nick Harvey try to check the story out and back in again.
>>>>>
>>>>> Of course, hacking into the database is not without risk, so please backup and backup again before trying to manually update anything.
>>>>>
>>>>> Adam
>>>>> RFX Technologies
>>>>>
>>>>> -----Original Message-----
>>>>> From: users@lists.bricolagecms.org [mailto:users@lists.bricolagecms.org] On Behalf Of Tom Ash
>>>>> Sent: Tuesday, April 24, 2012 6:47 AM
>>>>> To: users@lists.bricolagecms.org
>>>>> Cc: Charlie Harvey; Nick Harvey
>>>>> Subject: Unable to check in story which is checked out, but thinks it's not
>>>>>
>>>>> Hi,
>>>>>
>>>>> We have a story on our site ('front page' - so a fairly important one) which shows up as checked out to one of our users ('Nick Harvey') but which he can't check in in any way (whether he chooses 'Check in and Publish' or 'Check in and Shelve' or 'Check in to [Other User]' or whatever). When he does so Bric gives the following error:
>>>>>
>>>>> ==
>>>>> Cannot checkin non checked out versions
>>>>>
>>>>> Error Details (hide)
>>>>>
>>>>> Fault Class
>>>>> Bric::Util::Fault::Exception::GEN
>>>>> Description
>>>>> General Exception
>>>>> Timestamp
>>>>> 2012-04-24 03:18:09.000000
>>>>> Package
>>>>> Bric::Biz::Asset
>>>>> Filename
>>>>> /home/newint/bricolage2/lib/Bric/Biz/Asset.pm
>>>>> Line
>>>>> 1738
>>>>> Stack:
>>>>>
>>>>> Trace begun at /home/newint/bricolage2/lib/Bric/Biz/Asset.pm line 1738
>>>>> Bric::Biz::Asset::checkin('Bric::Biz::Asset::Business::Story=HASH(0x63986b0)') called at /home/newint/bricolage2/lib/Bric/App/Callback/Profile/Story.pm line 152
>>>>> Bric::App::Callback::Profile::Story::checkin('Bric::App::Callback::Profile::Story=HASH(0x73cd180)') called at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 296 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/Params/CallbackRequest.pm line 286 Params::CallbackRequest::request('Params::CallbackRequest=HASH(0x3708660)', 'HASH(0x4279500)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/MasonX/Interp/WithCallbacks.pm line 115 MasonX::Interp::WithCallbacks::make_request('MasonX::Interp::WithCallbacks=HASH(0x51ae770)', 'comp', '/workflow/profile/story/2308', 'args', 'ARRAY(0x7cef700)', 'ah', 'HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'apache_req', 'HTML::Mason::Apache::Request=HASH(0x523bc50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 868 eval {...} at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 867 HTML::Mason::ApacheHandler::prepare_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /usr/lib/perl5/vendor_perl/5.8.4/HTML/Mason/ApacheHandler.pm line 822 HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0x5122f00)', 'Apache=SCALAR(0x550ed50)') called at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 307 eval {...} at /home/newint/bricolage2/lib/Bric/App/Handler.pm line 296
>>>>> Bric::App::Handler::handler('Apache=SCALAR(0x550ed50)') called at PerlHandler subroutine `Bric::App::Handler::handler' line 1 eval {...} at PerlHandler subroutine `Bric::App::Handler::handler' line 1 Please report this error to your administrator. It may be helpful to include the error details in your report.
>>>>> ==
>>>>>
>>>>> I'm not sure how to resolve this. It looks like Bric has got confused as to the checkin status of the story, and we'd need to reset this, but I'm not sure how. Is this something I can change in Bric's database, and if so in what table?
>>>>>
>>>>> One possibly relevant factor is that I have a script running right now that's republishing this page frequently through bric_soap (because it's republishing the whole site to reflect some template changes, and our templates often republish the front page when another story is published). However, I've run that script before while users have checked the offending 'front page' story in and out with no problem.
>>>>>
>>>>> Any pointers?
>>>>>
>>>>> Thanks!
>>>>> Tom
>>>>
>>>>
>>>
>>
>>
>