[prev in list] [next in list] [prev in thread] [next in thread]
List: bricolage-bugs
Subject: [Bug 1351] Removing an output channel and publishing does not remove
From: bugs () lists ! bricolage ! cc
Date: 2008-09-30 15:23:26
Message-ID: 20080930152326.C471AD33B4 () mail ! exclupen ! com
[Download RAW message or body]
http://bugs.bricolage.cc/show_bug.cgi?id=1351
David Wheeler <david@kineticode.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #1 from David Wheeler <david@kineticode.com> 2008-09-30 11:23:26 ---
Fixed in r8302. I actually rewrote the expiration stuff to be a lot more
intelligent -- and simpler! The `publish()` method in Burner now waits until
all jobs are created for a given document, and then simply finds any files
associated with that asset but not with the just-created jobs. This properly
identifies all stale files, regardless of their paths, URIs, or output
channels, unlike the previous approach, which has been subject to many, *many*
bugs over the years.
I think that this approach should fix the issue once and for all.
Thanks for the bug report.
--
Configure bugmail: http://bugs.bricolage.cc/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic