> For the complete documentation index, see [llms.txt](https://doc.simax.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.simax.fr/technique/configuration-daffichage-du-site-php/possibilite-de-desactiver-laffichage-force-du-bouton-filtrer-en-extranet.md).

# Possibilité de désactiver l'affichage forcé du bouton filtrer en extranet

Dans le cadre de l'extranet, il est possible de ne plus forcé l'affichage du bouton filtrer (et donc de tenir compte du paramétrage - action liste pour laquelle la case à cocher "A confirmer" est coché. -) .

&#x20;

Pour configurer cela :

&#x20;

Par le site d'administration :

Se rendre sur le site d'administration du client web (en local racine du site/admin)

Menu "configuration d'affichage"

Premier sous menu affiché automatiquement ("Configuration d'affichage de base")

Cocher la case à cocher "Boutons filtrer en mode extranet, ne pas forcer l'affichage ?" afin de ne pas forcer le bouton "filtrer"

Le bouton sera affiché ou non en fonction du paramétrage

&#x20;

Par le fichier de configuration d'affichage:

Ouvrir le fichier de configuration d'affichage ("config\_display.inc.ini.php" à la racine du client

web)

Modifier la ligne DESACTIVATE\_FORCE\_BTN\_FILTER\_EXTRANET en mettant sa valeur à true :&#x20;

-> DESACTIVATE\_FORCE\_BTN\_FILTER\_EXTRANET="false"

Enregistrer le fichier

Le bouton sera affiché ou non en fonction du paramétrage


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.simax.fr/technique/configuration-daffichage-du-site-php/possibilite-de-desactiver-laffichage-force-du-bouton-filtrer-en-extranet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
