Content version's author defaults to prior version's author resulting in users contributing content on behalf of others
Last updated 2016-07-28 ·Reference W-2557472 ·Reported By 9 users
Upon contributing a new version of Content the author is unexpectedly defaulting to the previous Author of the Content.
This results in the content version details showing the content as uploaded on behalf of another user despite whether or not users have the library permissions to author content on behalf of others.
1. Create a library with two members, User A and User B and set their library permissions so that "Add Content" is selected without the "Manage Library" and "Add Content on Behalf of Others" permissions.
2. Contribute content to the library as User A.
3. Navigate to the content as User B and upload a new version
Actual Results: When User B contributes a new version of the content the author is being automatically set to the previous version's author (User A) by default. As a result the Content's version information shows as By: User B On behalf of User A and the Author field on the content detail page is not updated to reflect that User B contributed the latest version.
Expected Results: A new version should not be posted on behalf of another user unless explicitly specified by changing the author to a different user on upload.
None, outside of temporarily granting access to the field so that users can manually change the content version's Author value upon uploading new versions.
Administrators may temporarily expose the Author field for users on upload by granting the "Manage Library" and/or "Add Content on Behalf of Others" library permissions for affected users.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.