2 June 2018 This is a "cleanup" release to fix issues in some of the new features pushed into 4.6.0. Not all known deficiencies are fixed by this update, so another minor update will be rolled in about a week.
- RF-8 Enhance Turker management
This is a large piece of work covering all 4 tabs on the MTurkManagement page. Unfortunately, the (outdated) version of the MTurk API shows *very* low performance for some of these features. See RF-89 (below) and watch for additional improvements over the next two minor releases.
- RF-86 Correct the naming of tabs on the MTurk Management page
This is a minor point, but was confusing as non-standard terminology was being used.
- RF-83 Category selection control on WP Venue throws exception
This was actually an existing bug - from at least 2015 - that appeared only in very specific cases depending on the order of data returned by WordPress. The conditions triggering this failure required (a) that category hierarchy was used and (b) the order of categories returned by WordPress listed at least one child before its parent.
As an aside, when entering the category name manually, rather than selecting it from the "Add" popup dialog, the name entered is the category name, compared without regard to case - the category slug is NOT recognized by RF.
- RF-84 Author field has to be preserved through MTurk workflows
This update was needed internally. There are no user-facing workflows that currently use this feature, but you are welcome to use it if you like. The Scripting documentation will be updated to include it (it works just like title and description fields).
- RF-89 Downgrade features of Turkers tab to improve performance
To make the enhancements defined for RF-8 at least partially useful for the majority of users, the planned features have been whittled down to bare minimums. Even with that, the Turkers tab *will* fail for a few (very active) users. The next two minor updates will reimplement using newer MTurk APIs to restore the features defined for RF-8. As these improvements are added, they will appear as individually tracked issues in release notes.