This website requires JavaScript.
Explore
Help
Register
Sign In
yv01p
/
Umbraco-CMS
Watch
1
Star
0
Fork
0
You've already forked Umbraco-CMS
Code
Issues
Pull Requests
Actions
Packages
Projects
Releases
Wiki
Activity
Files
912a460bd8e685994caae9e2be76e4ea8b7a117e
Umbraco-CMS
/
src
/
Umbraco.Core
/
Events
History
Stephan
9f7b82e20f
U4-8077 - ensure product name in migration event handlers
2016-02-24 13:59:15 +01:00
..
CancellableEventArgs.cs
adds AdditionalData to the event args so we can use that to check for specific keys/values when consuming events and maintain compatibility.
2016-01-20 11:19:04 +01:00
CancellableObjectEventArgs.cs
adds AdditionalData to the event args so we can use that to check for specific keys/values when consuming events and maintain compatibility.
2016-01-20 11:19:04 +01:00
ContentCacheEventArgs.cs
…
CopyEventArgs.cs
…
DatabaseCreationEventArgs.cs
…
DeleteEventArgs.cs
Ensures events for deleting, trashing and unpublishing are done using the event messages, updates UI to support showing these messages in the list view, Since we cannot change the
2015-07-29 15:12:12 +02:00
DeleteRevisionsEventArgs.cs
…
EventExtensions.cs
adds AdditionalData to the event args so we can use that to check for specific keys/values when consuming events and maintain compatibility.
2016-01-20 11:19:04 +01:00
EventMessage.cs
Developers can cancel an event with the CancelOperation method of the event with a custom message which will be used in place of the normal default cancellation message
2015-07-27 18:04:20 +02:00
EventMessages.cs
Gets the messages being pumped out to the UI. Updates the ContentService and MediaServices to have a SaveWithStatus in order to determine the response, we'll need to update most of the methods to also have this OperationStatus. Now messages can be added to the UI for Saving & publishing for media and content services, we'll need to update more to support everything.
2015-07-24 11:44:09 +02:00
ExportEventArgs.cs
…
IEventMessagesFactory.cs
Gets the messages being pumped out to the UI. Updates the ContentService and MediaServices to have a SaveWithStatus in order to determine the response, we'll need to update most of the methods to also have this OperationStatus. Now messages can be added to the UI for Saving & publishing for media and content services, we'll need to update more to support everything.
2015-07-24 11:44:09 +02:00
ImportEventArgs.cs
…
ImportPackageEventArgs.cs
…
MacroErrorEventArgs.cs
…
MessageType.cs
working on U4-5927 - this extends the base event class to have EventMessages which event consumers can add to, the trick is that there is a factory for these EventMessages, in a web context, the factory is a request based factory so that during a request all instances of the EventMessages are the same instance. All services then accept an instance of IEventMessagesFactory which they can then use when raising events. We'll then use this to send messages to the UI. Not sure if i should make this a resolver yet or not. Still a WIP!!
2015-07-23 20:04:40 +02:00
MigrationEventArgs.cs
U4-8077 - ensure product name in migration event handlers
2016-02-24 13:59:15 +01:00
MoveEventArgs.cs
Ensures events for deleting, trashing and unpublishing are done using the event messages, updates UI to support showing these messages in the list view, Since we cannot change the
2015-07-29 15:12:12 +02:00
MoveEventInfo.cs
working on U4-5927 - this extends the base event class to have EventMessages which event consumers can add to, the trick is that there is a factory for these EventMessages, in a web context, the factory is a request based factory so that during a request all instances of the EventMessages are the same instance. All services then accept an instance of IEventMessagesFactory which they can then use when raising events. We'll then use this to send messages to the UI. Not sure if i should make this a resolver yet or not. Still a WIP!!
2015-07-23 20:04:40 +02:00
NewEventArgs.cs
working on U4-5927 - this extends the base event class to have EventMessages which event consumers can add to, the trick is that there is a factory for these EventMessages, in a web context, the factory is a request based factory so that during a request all instances of the EventMessages are the same instance. All services then accept an instance of IEventMessagesFactory which they can then use when raising events. We'll then use this to send messages to the UI. Not sure if i should make this a resolver yet or not. Still a WIP!!
2015-07-23 20:04:40 +02:00
PublishEventArgs.cs
Ensures events for deleting, trashing and unpublishing are done using the event messages, updates UI to support showing these messages in the list view, Since we cannot change the
2015-07-29 15:12:12 +02:00
RecycleBinEventArgs.cs
…
RefreshContentEventArgs.cs
…
RollbackEventArgs.cs
…
SaveEventArgs.cs
adds AdditionalData to the event args so we can use that to check for specific keys/values when consuming events and maintain compatibility.
2016-01-20 11:19:04 +01:00
SendToPublishEventArgs.cs
…
TransientMessagesFactory.cs
Gets the messages being pumped out to the UI. Updates the ContentService and MediaServices to have a SaveWithStatus in order to determine the response, we'll need to update most of the methods to also have this OperationStatus. Now messages can be added to the UI for Saving & publishing for media and content services, we'll need to update more to support everything.
2015-07-24 11:44:09 +02:00
TypedEventHandler.cs
…