How do controllers handle memory management?

Controllers use the hostDisconnected and destroy methods to clean up resources such as window intervals, event listeners, and data subscriptions when they are no longer needed.

Why use UmbControllerBase when creating controllers?

Extending UmbControllerBase provides automatic registration with the host element and ensures that lifecycle methods like destroy() are called correctly to prevent memory leaks.

What is an Umbraco Controller?

An Umbraco Controller is a specialized class that encapsulates logic or side effects while maintaining a connection to a host element's lifecycle, enabling clean logic reuse in the backoffice.

Can Umbraco Controllers access global CMS data?

Yes, controllers can use the getContext or consumeContext methods to interact with Umbraco's context API, such as accessing the notification or authentication services.

Umbraco Backoffice Controllers

Name: Umbraco Backoffice Controllers
Author: umbraco

byumbraco

•

Content Management

Builds and manages reusable logic components for the Umbraco CMS Backoffice using the lifecycle-aware controller pattern.

About

This skill provides specialized guidance for implementing controllers within the Umbraco Backoffice, allowing developers to decouple complex logic from UI elements. It facilitates the creation of robust classes that manage side effects, timers, and subscriptions while remaining synchronized with an element's lifecycle (connected, disconnected, and destroyed). By leveraging the Umbraco Controller API and UmbControllerBase, it ensures proper resource management and promotes modular, maintainable code structures for custom CMS extensions.

Key Features

Lifecycle management via hostConnected, hostDisconnected, and destroy methods
Standardized patterns for managing timers, intervals, and data subscriptions
Automated registration and deregistration with Umbraco Host Elements
Logic composition through nested controller hosting capabilities
Seamless access to Umbraco contexts like notifications and authentication
1 GitHub stars

Use Cases

Creating reusable business logic shared across multiple backoffice UI components
Implementing specialized API interaction wrappers with automatic cleanup
Managing complex background tasks and data polling within the CMS interface

About

Key Features

Lifecycle management via hostConnected, hostDisconnected, and destroy methods
Standardized patterns for managing timers, intervals, and data subscriptions
Automated registration and deregistration with Umbraco Host Elements
Logic composition through nested controller hosting capabilities
Seamless access to Umbraco contexts like notifications and authentication
1 GitHub stars

Use Cases

Creating reusable business logic shared across multiple backoffice UI components
Implementing specialized API interaction wrappers with automatic cleanup
Managing complex background tasks and data polling within the CMS interface