Releases: nathanwoulfe/Plumber-2
v2.1.12
v2.1.11
Improves UI notifications when a workflow is completed but the save and publish action fails.
v2.1.10
Updates SignalR initialisation to fix a conflict with Deploy (and potentially other packages using SignalR). Bug impacted Umbraco 8 only, so Plumber 2 on Umbraco 9 need not update.
v10.1.1
- Fixes bug where native Send to publish button was still displayed after installing Plumber
- Fixes bug where content types where incorrectly filtered
- Fixes SQLite migration - SQLite will always be a fresh install, since no one is using this in production, right? RIGHT?!
v2.1.9
- Fixes bug where native Send to publish button was still displayed after installing Plumber
- Fixes bug where content types where incorrectly filtered
- Fixes bug where workflows were not cancelled when deleting a node
v10.1.0
- Fixes cross-compatibility bug with SQL and SQLite date-based queries
- Fixes UI issue where successful workflows showed an error state if a previous workflow scheduled the content, and the scheduled date had not yet passed
- Fixes issue where datepicker initialises before config object exists
Note breaking change in INotificationsService - calls to GetNotificationsForAction must provide the PublishResult from the triggering action.
v10.0.0
V10 supports (surprise) Umbraco 10 only - older Umbraco versions must remain on the v2 branch. This release adds no new features, but drops the multi-targeted package in favour of supporting the current Umbraco LTS release only.
v2.1.7
Fixes a bug where a duplicate unpublish button is added to the sub-buttons array, which breaks ng-repeat, and in turn breaks the publish button dropdown/sub-menu.
v2.1.6
Fixes a bug where the comment field on the initiate workflow view wasn't correctly length-limited. Updated to use the existing comments component, which has had logic improvements to better track the remaining character count.
v2.1.5
Fixes a bug where email generation mutates the active workflow, resulting in one or more additional tasks being added to the process, which prevents the workflow from advancing/completing automatically. Appears to only be an issue when an admin user actions a workflow, causing it to progress to a final stage where that user is also a group member, in which case the changes are published but the workflow does not complete.