Skip to main content

CMSService

The CMSService is an internal service, registered by the CMSModule. It acts as the intermediary between the CMSController and the configured CMSProvider.

Usage​

In a standard project, you should not need to interact with, extend, or override this service directly. It is managed by the framework.

Deep Dive​

Description: The CMSService is a singleton within the Archibald server that holds the reference to the currently active CMSProvider. When a request comes into the CMSController, the controller simply calls the corresponding method on the CMSService, which then forwards the call to the provider.

  • How To: This is an internal framework component. There is no public "How To" for using this service, as its use is encapsulated within the CMSModule. Understanding its role is useful for debugging the server-side request flow.

    Request -> CMSController -> CMSService -> CMSProvider -> CMS API

  • Best Practice: All custom CMS logic should be implemented in a CMSProvider, not by trying to override or extend the CMSService. The service is designed to be generic, while the provider is designed for specificity. This separation of concerns is a core architectural principle of the framework. Any attempt to modify the service would be fighting against the framework's design and would make your application harder to maintain and upgrade.