---
title: "Content"
manual: "Klaro! Consent Manager"
version: "3.0"
permalink: "https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:for-editors-configuration-content@3.0"
source: "Editor/Configuration/Content/Index.rst"
rendered: "2026-09-24T10:59:28+00:00"
---

# Content {#for-editors-configuration-content}

![Content tab of a Klaro configuration record](../../../Images/Configuration-Content.png)

-   [Hide Buttons](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:hide-buttons@3.0)
-   [Append Buttons](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:append-buttons@3.0)
-   [Translations](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:translations@3.0)

## Hide Buttons {#hide-buttons}

### Hide Decline All {#hide-decline-all}

-   **hide_decline_all**

    -   *type:* boolean
    -   *Default:* false

    Setting `hideDeclineAll` to `true` will hide the "decline" button in the consent modal and force the user to open the modal in order to change his/her consent or disable all third-party services. We strongly advise you to not use this feature, as it opposes the "privacy by default" and "privacy by design" principles of the GDPR (but might be acceptable in other legislations such as under the CCPA)

### Hide Learn More {#hide-learn-more}

-   **hide_learn_more**

    -   *type:* boolean
    -   *Default:* false

    Setting `hideLearnMore` to `true` will hide the "learn more / customize" link in the consent notice. We strongly advise against using this under most circumstances, as it keeps the user from customizing his/her consent choices.

### Hide Toggle All {#hide-toggle-all}

-   **hide_toggle_all**

    -   *type:* boolean
    -   *Default:* false

    Setting `hideToggleAll` to `true` will hide the "toggle all" link in the consent notice.

## Append Buttons {#append-buttons}

### Append Show Button {#append-show-button}

-   **append_show_button**

    -   *type:* boolean
    -   *Default:* false

    If this option is set, a button is created in the frontend (via JavaScript)
    directly in front of the closing body tag, which triggers the opening of
    the Klaro consent management. For links in existing page content, see
    [Trigger Links](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:features-trigger-links@3.0).

### Append Reset Button {#append-reset-button}

-   **append_reset_button**

    -   *type:* boolean
    -   *Default:* false

    If this option is set, a button is generated in the frontend (via
    JavaScript) directly in front of the closing body tag, which triggers the
    resetting of all settings and the opening of the Klaro consent management.
    For links in existing page content, see [Trigger Links](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:features-trigger-links@3.0).

## Translations {#translations}

### Fluid Template Root Path {#configuration-content-fluidtemplaterootpath}

-   **fluidtemplate_rootpath**

    -   *type:* string
    -   *Default:* ''

    As an alternative to the [TypoScript configuration](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:configuration-typoscript-constants@3.0) under
    `plugin.tx_klaroconsentmanager.view`, a Fluid root path can be defined here.
    This path has a higher priority than the paths configured in TypoScript.
    The directories `/Layouts/`, `/Partials/`, and `/Templates/` are expected
    under this path. Fluid templates created here are used to enrich Locallang
    labels with additional functionality or to replace them completely. Fluid
    templates that override labels are expected in `/Templates/Labels/`. The
    path convention is described in [Fluid enriched labels](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:howto-fluid-enriched-labels@3.0).

### Locallang Path {#configuration-content-locallangpath}

-   **locallang_path**

    -   *type:* string
    -   *Default:* ''

    Optional path to an additional XLIFF file that overwrites the default labels
    or adds new labels, for example for [custom purposes](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:howto-custom-purpose@3.0) or [custom services](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:howto-custom-service@3.0).
    If Fluid templates exist for these labels, the templates take precedence
    over the XLIFF text. It is common to render the original XLIFF label from
    the Fluid template through the `Label` partial.