It's not a bug, and it's not going to be changed.  When you are logged in, and uploading a file to the Repository, your user information ( username and email address ) are used to identify you as the person who uploaded the file.  That's why the user name field is 'read-only', otherwise, if I was able to change that field, I would be able to upload a file and put in someone else's name which would be untrue.  If you are an administrator, then you will be able to edit that field, but anyone who's not an administrator will not.  The host account is not intended to be used to administer a portal, but to administer the host, so only a portal administrator can edit the username of an upload.

I hope that you understand the reasoning behind this design. The username is displayed on the uploaded items, if someone else uploaded a file and put my name on it and my email address I would be annoyed at the very least.

I agree with the reasoning behind not allowing members to edit this field, however, I respectfully submit that there is still a bug in the implementation of this functionality.  After receiving the same error in a number of situations, I have determined the following:

a. It is not limited to host usage - the same situation may occur for any user, including the site administrator.

b. Even the site admin can not edit this field on an upload.

c. The real reason that this error occurs is because it uses the name fields from the UserProfile record as opposed to the Users record! As is the case with all the profile fields, the FirstName/LastName fields can be made optional at the discretion of the site administrator. Even though a new user addition will auto-populate these fields from the Users record, the administrator can subsequently go in and blank them out (as can the member if they are made optional). In the case where these fields are blank, the Repository upload will not work. I would suggest that the FirstName/LastName should come from the Users record where they are always mandatory.

In the meantime, this problem can be worked around by marking the FirstName/LastName fields in the UserProfile "Required". If necessary, the host account profile can also be modified to supply these fields so that the host can also use the module.

 Ken