Carefully control encodings.

The problem you are encountering is the simplest form of the nightmare that is character encoding. Rule one in handling encoding issues is to always control the encoding. In your case, this HTML should really be stored un-encoded in the DB, allowing for a single use of the twig raw output filter.

Consider the implications if you don't know whether the HTML needs to be decoded. For instance, if someone intended to show a < (<) in the text, and the html wasn't encoded, then applying html_entity_decode will turn that encoded < into a real one, and break the HTML. (Browsers will think you're starting a new TAG).

Forms submitting html

I'm going to guess that elsewhere in your app, there are forms which allow people to submit HTML. HTML forms encode data before posting, PHP $_POST handling usually auto applies htmlentities onto posted fields.

Whatever methods of your application are handling the storing of such Posted HTML, or add/changes these entities, should use html_entity_decode to ensure it is stored as raw html.

This way, you always know that HTML is stored in you database in exactly the state it needs to be rendered on the page. If it needs to be encoded and decoded again somewhere for some reason, you're not left hoping that some of the content won't be double-decoded. (Or as in your case, missing a decode step and spitting out raw HTML).

Rendering HTML in twig

One way or another, you need to get that content to your twig, passed through the raw filter, in the exact state it needs to be put on the page. While this can be done in twig, or with twig functions, this really should be done in the Controller.

Consider that path this data is traveling:

1. Form (raw HTML)
2. PHP POST (encoded HTML)
3. DB (encoded HTML)
4. SELECT Query
5. PHP Controller (encoded HTML)
6. Twig
7. Rendered HTML

The earlier you can get the data in the correct state, the better. Doing so makes the data easier to work with, reduces the performance impact, and prevents code-duplication later in those steps. (What happens if you want to use this html in other Controllers or Twig templates? Code duplication.) Hense, my first suggestion to get it in the database cleanly.

If clean data is not an option...

Clean the data in your controller, maybe even with a static function in the entity.

The only other clean-ish way to handle this, is to loop through and decode the html before passing it to Twig. Doing it this way however, or later in the Tiwg template as you're currently doing, you run the risk of double-decoding that I mentioned earlier.

Veille

Class Veille
{

    . . .

    public static function decodeArray(?array $vielleList): ?array
    {
        foreach ($vielleList as $vielle) {
            if (!$vielle instanceof self) {
                continue;
            }

            $vielle->setVText(html_entity_decode($vielle->getVText()));
        }

        return $vielleList;
    }

    public function getVText(): ?string
    {
        return htmlentities("<h3>Encoded HTML Test</h3>Good data &gt; parsing bad data.");
    }

    public function setVText(?string $text): void
    {

    }
}

Controller

$listactufree = $repository->findBy(
    array('vStatus' => '4'), // Critere
    array('vDatePublished' => 'desc'),        // Tri
    5,                              // Limite
    0                               // Offset
);


$listactufree = Veille::decodeArray($listactufree);

Twig

{% for veille in listactufree %}

    {{ veille.vTexte|raw }}

{% endfor %}

Note, this same code could clean your data.

Plugging the contents of the decodeArray method into a command, and running that command, along with persist/flush, would store decoded HTML for all of your entities. Just make sure you only decode ONCE, and any methods which can add or edit these entities store the HTML unencoded. That's the key. Unencoded data.