17 July 2016 This is the culmination of 5 minor releases correcting a bunch small but in some cases critical problems.
Fixed issues in Persona Copy (P228, P249) [ACTION REQUIRED]
When creating a new Persona and selecting a Persona to copy from, there were several issues that had to be fixed in a sequence of releases culminating in this version. Any Persona you created as a copy of another should be checked for two kinds of errors.
First, prior to 4.4.1, a copied Persona would post to Venues in the original Persona! Ouch. That has been fixed for some time now and in all cases where the issue was reported, I fixed the problem by hand in addition to updating the code to keep it from happening again. If you feel you have this issue, just open the workflows that are using Venues as output, select the Venue, and hit save. This update will fix the problem.
Second, the Script workflow did not copy correctly. Specifically, the wrong script file was selected. To fix, simply select the correct script and hit save.
Third, Delay and Scheduler workflows did not copy. Check your workflows and recreate these flows if they are missing.
Clone double posting to Venues (P253)
Originally reported for the WordPress venue, it was true of all other Venues as well. In all cases where a Venue was the output of a Clone, the posting happened twice. If there was an intermediate folder, this did not occur. The problem is now fixed and no action is required.
Reset tags and categories when WordPress channel changed
When you select different channel credentials on a WordPress Venue the tags and categories will be reset. This represent the most common case and protects users (especially new ones) from a common error.
Alphabetize the Persona selection menu (P245)
The drop down now shows the list of Personas in alphabetic order
Can’t delete folders that were referenced in workflows (P247)
This only happened in cases of a copied Persona where a folder was referenced by a copied workflow. When the workflow was changed and the folder no longer referenced, it could still not be deleted. This is now fixed and no action is required.