Timeline for Inserting PublishedBy UserName into Component
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 11, 2013 at 11:20 | vote | accept | Sri | ||
Jun 10, 2013 at 11:51 | history | tweeted | twitter.com/#!/StackTridion/status/344059139435155457 | ||
Jun 4, 2013 at 14:50 | comment | added | Bjørn van Dommelen | Do you want to store this information in a separate, dedicated component or in the component being published? How will this work if a single component is published with multiple DCTs or when a page is published? If you are primarily interested in keeping an audit trail I would recommend to use the Event System and write a message into the event log every time a user creates a publish transation... | |
Jun 4, 2013 at 12:34 | comment | added | Nickoli Roussakov | As long as the event system always overwrites that field on a publish event, then editors can edit it all they want without any impact. | |
Jun 4, 2013 at 12:09 | comment | added | Sri | Exactly..users should not edit. Thanks Alvin and i will explore more about app data. | |
Jun 4, 2013 at 12:06 | history | edited | Sri | CC BY-SA 3.0 |
added 359 characters in body
|
S Jun 4, 2013 at 12:02 | history | suggested | Frank van Puffelen | CC BY-SA 3.0 |
changed \ to / where needed, marked inline code fragments
|
Jun 4, 2013 at 11:55 | review | Suggested edits | |||
S Jun 4, 2013 at 12:02 | |||||
Jun 4, 2013 at 11:44 | answer | added | Pankaj Gaur | timeline score: 4 | |
Jun 4, 2013 at 11:23 | comment | added | Alvin Reyes | The catch with this approach is users would be able to update that field. How will you use this user information? If for display on the site, consider adding it via templating. Otherwise if it's for audits or tracking, AppData may be a good candidate to store this independent of the component fields. | |
Jun 4, 2013 at 10:51 | review | First posts | |||
Jun 5, 2013 at 5:47 | |||||
Jun 4, 2013 at 10:36 | history | asked | Sri | CC BY-SA 3.0 |