IMPORTANT: This version of Sitefinity CMS is out of support and the respective product documentation is no longer maintained and can be outdated. Use the version selector to view a supported product version.
The dynamic modules that you created through the module builder also expose events you can subscribe to. This article provides a list of all those events and the data they pass in your event handler arguments.
This interface is implemented by all events which fire for dynamic modules. Use it if you want to subscribe to all of them. Use the following code to subscribe.
In the event handler, you can access the ID of the currently logged in user.
This interface is implemented by all events which fire before a dynamic content item is created. There's only one such built-in event, but you should subscribe using the interface rather than the class that implements it. Subscribe using the following code.
In the event handler you can access the following information:
This interface is implemented by all events which fire after a dynamic content item has been created. There's only one such built-in event, but you should subscribe using the interface rather than the class that implements it. Subscribe using the following code.
This interface is implemented by all events which fire before a dynamic content item is updated. There's only one such built-in event, but you should subscribe using the interface rather than the class that implements it. Subscribe using the following code.
This interface is implemented by all events which fire after a dynamic content item has been updated. There's only one such built-in event, but you should subscribe using the interface rather than the class that implements it. Subscribe using the following code.
This interface is implemented by all events which fire before a dynamic content item is deleted. There's only one such built-in event, but you should subscribe using the interface rather than the class that implements it. Subscribe using the following code.
In the event handler you can access the following information.
This interface is implemented by all events which fire after a dynamic content item has been deleted. There's only one such built-in event, but you should subscribe using the interface rather than the class that implements it. Subscribe using the following code.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important