// Add your reply above here
==================================================
Nick Legg updated this ticket at December 28th, 2010 @ 06:46 PM
Using "bric_soap delete" to deactivate an asset causes that asset to be republished and expired (and deleted from its preview and publish destinations), but the asset remains stuck in a checked-out state to the bric_soap user. This appears to always (and only) affect stories with multiple Output Channels. This behavior has been observed in Bricolage 1.10.9. Here's a the "story" and "story_instance" entries for one such affected story in my database:
SELECT * FROM story WHERE id = 16014;
id | uuid | priority | source__id | usr__id | element_type__id | primary_uri | first_publish_date | publish_date | expire_date | current_version | published_version | workflow__id | desk__id | publish_status | active | site__id | alias_id
-------+--------------------------------------+----------+------------+---------+------------------+--------------------------------------------+---------------------+---------------------+---------------------+-----------------+-------------------+--------------+----------+----------------+--------+----------+----------
16014 | 0EF21F1A-4B5B-11DC-AF68-4B0C5EB2C18E | 3 | 1133 | 1045 | 1044 | /offices/humanresources/december_2000.html | 2007-08-15 18:15:00 | 2010-12-28 18:09:36 | 2010-12-28 18:09:36 | 1 | 1 | 0 | 0 | t | f | 100 |
(1 row)
SELECT * FROM story_instance WHERE story__id = 16014;
id | name | description | story__id | version | usr__id | slug | primary_oc__id | cover_date | note | checked_out
--------+---------------+-------------+-----------+---------+---------+---------------+----------------+---------------------+------+-------------
39751 | December 2000 | | 16014 | 1 | 1082 | December_2000 | 1 | 2007-08-15 18:12:00 | | f
152499 | December 2000 | | 16014 | 1 | 1045 | December_2000 | 1 | 2007-08-15 18:12:00 | | t
(2 rows)
--------------------------------------------------------------------------------
Assigned: Bugs (at bricolage)
State: new
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/235-bric_soap-delete-on-an-asset-causes-that-asset-to-be-expired-properly-but-it-becomes-stuck-in-a-partially-checked-out-state
Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/235-bric_soap-delete-on-an-asset-causes-that-asset-to-be-expired-properly-but-it-becomes-stuck-in-a-partially-checked-out-state/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com
==================================================
Nick Legg updated this ticket at December 28th, 2010 @ 06:46 PM
Using "bric_soap delete" to deactivate an asset causes that asset to be republished and expired (and deleted from its preview and publish destinations), but the asset remains stuck in a checked-out state to the bric_soap user. This appears to always (and only) affect stories with multiple Output Channels. This behavior has been observed in Bricolage 1.10.9. Here's a the "story" and "story_instance" entries for one such affected story in my database:
SELECT * FROM story WHERE id = 16014;
id | uuid | priority | source__id | usr__id | element_type__id | primary_uri | first_publish_date | publish_date | expire_date | current_version | published_version | workflow__id | desk__id | publish_status | active | site__id | alias_id
-------+--------------------------------------+----------+------------+---------+------------------+--------------------------------------------+---------------------+---------------------+---------------------+-----------------+-------------------+--------------+----------+----------------+--------+----------+----------
16014 | 0EF21F1A-4B5B-11DC-AF68-4B0C5EB2C18E | 3 | 1133 | 1045 | 1044 | /offices/humanresources/december_2000.html | 2007-08-15 18:15:00 | 2010-12-28 18:09:36 | 2010-12-28 18:09:36 | 1 | 1 | 0 | 0 | t | f | 100 |
(1 row)
SELECT * FROM story_instance WHERE story__id = 16014;
id | name | description | story__id | version | usr__id | slug | primary_oc__id | cover_date | note | checked_out
--------+---------------+-------------+-----------+---------+---------+---------------+----------------+---------------------+------+-------------
39751 | December 2000 | | 16014 | 1 | 1082 | December_2000 | 1 | 2007-08-15 18:12:00 | | f
152499 | December 2000 | | 16014 | 1 | 1045 | December_2000 | 1 | 2007-08-15 18:12:00 | | t
(2 rows)
--------------------------------------------------------------------------------
Assigned: Bugs (at bricolage)
State: new
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/235-bric_soap-delete-on-an-asset-causes-that-asset-to-be-expired-properly-but-it-becomes-stuck-in-a-partially-checked-out-state
Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/235-bric_soap-delete-on-an-asset-causes-that-asset-to-be-expired-properly-but-it-becomes-stuck-in-a-partially-checked-out-state/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com