_createdBy should be getting assigned from admin portal

[karl-thomas]

Currently, the _createdBy field, or fields similar to it are not being filled out automatically when an admin creates a bit of content. this causes a lot of errors on the front end and leads to a lot checking if the user is there or not, where if the content was created on the front end, it would almost always be explicitly assigned.
Possible issues with adding this

• admin wants to assign a different user to have created something rather than themselves.
• _createdBy could not be the name of the field
• admin could want no created by user on a specific item for some reason.

[ashanan]

@rockrgrrl @cstallings1 do either of you know if this was done for a particular reason or is this a bug?

[cstallings1]

@ashanan I wouldn't call it a bug but I'm not sure that it was purposefully never added in. If anything I would say that we try to keep the admin portal pretty flexible and this is assuming:

1. • there is a field called '_createdBy' that references a User object
2. • the admin user should be the name displayed as the one who created it

So pretty much the issues Karl pointed out. But I'm not sure that those are big enough issues to warrant not adding it.