Timeline for Resolver affected by event system in Tridion 2013
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 14, 2020 at 6:23 | vote | accept | Marko Milic♦ | ||
| S Mar 18, 2017 at 9:01 | history | bounty ended | Marko Milic♦ | ||
| S Mar 18, 2017 at 9:01 | history | notice removed | Marko Milic♦ | ||
| Mar 14, 2017 at 6:05 | history | edited | Marko Milic♦ | CC BY-SA 3.0 |
added 455 characters in body
|
| Mar 13, 2017 at 19:54 | comment | added | Albert Romkes | Some clarification: on component (un)publish you write the timestamp and component-uri to a (Apache MQ) queue. A (windows)service listens to this queue and updates the component-field with the core-service. It's not an ideal solution, but if you can't change the current implementation... | |
| Mar 13, 2017 at 19:39 | comment | added | Dominic Cronin | Could be worse.... I once inherited a system that did this on component save. | |
| Mar 13, 2017 at 14:38 | history | tweeted | twitter.com/StackTridion/status/841297335355355136 | ||
| Mar 13, 2017 at 14:12 | comment | added | Albert Romkes | One option could be to write the timestamp + component uri to an external database (With the eventsystem, possibly async). Write a windows service (or powershell script, or... you get it ;) ) and run this every hour. Or every minute. Or push it to a queue and write a queue listener... | |
| Mar 13, 2017 at 13:27 | answer | added | Hiren Kaku | timeline score: 3 | |
| Mar 13, 2017 at 8:59 | history | edited | Marko Milic♦ | CC BY-SA 3.0 |
added 17 characters in body
|
| S Mar 13, 2017 at 8:58 | history | bounty started | Marko Milic♦ | ||
| S Mar 13, 2017 at 8:58 | history | notice added | Marko Milic♦ | Authoritative reference needed | |
| Feb 13, 2017 at 14:14 | history | edited | Marko Milic♦ | CC BY-SA 3.0 |
edited tags
|
| Nov 2, 2016 at 10:32 | history | asked | Marko Milic♦ | CC BY-SA 3.0 |