no-reply at lighthouseapp
Aug 2, 2011, 1:28 PM
Post #1 of 4
// Add your reply above here
[Bricolage #277] PUBLISH_RELATED_FAIL_BEHAVIOR behaves inconsistently
Nick Legg updated this ticket at August 2nd, 2011 @ 07:57 PM
I'm having some trouble with PUBLISH_RELATED_FAIL_BEHAVIOR and publishing stories. There are two different ways to publish via the UI: from my Workspace and/or a Desk or from within the Edit Profile on the story I want to publish.
*CASE 1* - If PUBLISH_RELATED_FAIL_BEHAVIOR = warn, I receive a nice Ajax popup that tells me I cannot publish my story because one of its related stories is checked out. Shouldn't this only happen when PUBLISH_RELATED_FAIL_BEHAVIOR = fail? Furthermore, the publish job for the story I want to publish is not created - so I might as well be on the "fail" setting.
*CASE 2* - If PUBLISH_RELATED_FAIL_BEHAVIOR = fail, the story "fades" off the Workspace/Desk, but no job is ever created. Upon refreshing the Workspace/Desk, the story is back. Apparently the error is silent, which is really misleading.
*CASE 3* - If PUBLISH_RELATED_FAIL_BEHAVIOR = warn, I receive a 500 error page after performing a Checkin & Publish. No publish job is not created. Here's the error log entry:
[Tue Aug 02 19:36:39 2011] [error] [client xxx.xxx.xxx.xxx] Can't use string ("Some of the related assets were ") as an ARRAY ref while "strict refs" in use at /usr/local/bricolage/lib/Bric/App/Callback/Desk.pm line 377, <GEN13> line 3153.\n, referer: https://bric.denison.edu/workflow/profile/story/21641/?checkout=1
*CASE 4* - If PUBLISH_RELATED_FAIL_BEHAVIOR = fail, I'm kicked out to my Workspace where I see the following error message at the top (the story gets checked in but doesn't publish, of course):
Story "Catalog Builder" saved and checked in to "Ucomm".
Cannot auto-publish related story "Political Science" because it is checked out.
Publish aborted due to errors above. Please fix the above problems and try again.
The fourth case behaves as expected, but the first three do not. For 1 and 2, the publish job should always be created and execute normally if PUBLISH_RELATED_FAIL_BEHAVIOR = warn; additionally, the user should be given some kind of warning message. For 3, the user should be presented with an error along the same lines as the one received in 4 (or, perhaps better, the error popup used in case 1).
Assigned: Bugs (at bricolage)
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/277-publish_related_fail_behavior-behaves-inconsistently
Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/watching/9a5aa53ab1426026e1d7876f419088672f6de42d
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support [at] lighthouseapp or http://help.lighthouseapp.com