adam at RFXTechnologies
Apr 24, 2012, 5:48 AM
Views: 700
Permalink
|
|
RE: Unable to check in story which is checked out, but thinks it's not
[In reply to]
|
|
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 [at] lists [mailto:users [at] lists] On Behalf Of Tom Ash
Sent: Tuesday, April 24, 2012 6:47 AM
To: users [at] lists
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
|
RE: Unable to check in story which is checked out, but thinks it's not