---
title: "Override service registration"
manual: "TYPO3 Explained"
version: "11.5"
permalink: "https://docs.typo3.org/permalink/t3coreapi:services-configuration-registration-changes@11.5"
source: "ApiOverview/Services/Configuration/RegistrationChanges.rst"
rendered: "2026-10-21T15:30:00+00:00"
---

> [!WARNING]
> **Attention**
>
> TYPO3 v11 has reached end-of-life as of October 31th 2024 and
> is no longer being maintained. Use the version switcher on the top
> left of this page to select documentation for a supported version of TYPO3.
>
> Need more time before upgrading?
> You can purchase Extended Long Term Support (ELTS) for TYPO3 v11 here:
> [TYPO3 ELTS](https://typo3.com/services/extended-support-elts).

# Override service registration {#services-configuration-registration-changes}

The priority and other values of the original service registration can be
overridden in any extension's `ext_localconf.php` file. Example:

```php
 // Raise priority of service 'tx_example_sv1' to 110
$GLOBALS['TYPO3_CONF_VARS']['T3_SERVICES']['auth']['tx_example_sv1']['priority'] = 110;

 // Disable service 'tx_example_sv1'
$GLOBALS['TYPO3_CONF_VARS']['T3_SERVICES']['auth']['tx_example_sv1']['enable'] = false;
```

The general syntax is:

```php
$GLOBALS['TYPO3_CONF_VARS']['T3_SERVICES'][service type][service key][option key] = value;
```

Registration options are described in more details in
[Implementing a service](https://docs.typo3.org/permalink/t3coreapi:services-developer-implementing@11.5).
Any of these options may be overridden using the above
syntax. However caution should be used depending on the options.
`className` should not be overridden in such a way.
Instead a new service should be implemented using an alternate
class.