Warm-up: FlatPress 1.5 - Community Test

[macadoum]

Nice it's working now ! Thank you Fraenkiman.

But is this gdpr disclaimer still necessary ? I heard EU eased the legal aspects of it.

[fraenkiman]

I am writing as a German citizen, and I assume that the situation is similar in France.

Yes – if the YouTube embed (iframe) loads when the page is accessed, you still need consent before loading (and understandable advance information). In Germany, this is not only GDPR, but also § 25 TDDDG (access/storage on the end device, e.g., cookies/identifiers) – basically only with consent, except when "absolutely necessary."
https://dsgvo-gesetz.de/ttdsg/25-ttdsg/

The plugin offers a 2-click solution (first notice/placeholder, then "play video"). This is still the common, more legally secure way, because no data should be sent to YouTube before the click. Data protection supervisory authorities describe exactly this principle: preview without transmission, transmission only after active click plus sufficient information.
https://www.baden-wuerttemberg.datenschutz.de/videos-einbinden/

The fact that supervisory authorities take this issue seriously can be seen, for example, in the fact that in 2025, the BfDI identified YouTube embeds without consent as violations and wrote to the relevant authorities about this.
https://www.bfdi.bund.de/SharedDocs/Kurzmeldungen/DE/2025/13-teilautomatisierte-Webseitenpr%C3%BCfung.html

What has been "simplified" or is currently being discussed:
In November 2025, the EU Commission announced proposals to reduce the flood of cookie banners (including through more centralized consent management). However, this is a proposal/process, not a free pass that automatically makes YouTube embeds “without consent” today.
https://digital-strategy.ec.europa.eu/en/faqs/digital-package

Important note: This is not legal advice. Find out about the current legal situation in your country.
Best regards,
Frank

[macadoum]

My tests on commenting a blog post :

- As a visitor I cannot enter a link using the [url] method : word is banned. But I can still post a link. Strange behavior.

- mathematical spam question : I was asked 1 minus 7, I entered -6 but it was a false answer. I should have entered 6 so the comment can be processed. It's difficult for a visitor to post a comment as a lot of these mathematical questions contain a small number minus a bigger one. There should be only big number minus a smaller one.

- As an administrator, I can't edit my comment. If I see a typo, I must first delete the comment then publish a new one...

- As an administrator, if I choose to approve comments before publication, there should be a notification or a color to alert me if a new comment is in the waiting list. I shouldn't have to manually check for comments each time ?

- When I open a blog post( exemple https://macadoum.free.nf/?u=/2025/12/17 ... d-youtube/) I should see the 9 comments attached to it directly. I shouldn't need to use an extra clic to see the comments ?

[macadoum]

I'll add another one :

There are some alignment problems with the comments. It seems than if you put a list in a comment, the next comment is misaligned and becomes a part of the list from the previous comment

See : https://macadoum.free.nf/?u=/2025/12/17 ... /#comments

[RainerBielefeld]

- As a visitor I cannot enter a link using the method : word is banned. [/quote] I ... /myfp]here in a similar environment to this blog.
"URL" can be posted by a guest in Comment, also "[", but "[url" will be banned. And yes, I can't see any logic why a link can be posted in comment.

I did an additional Tes with a flatpress 1.3.1. Blog
* The URL Tag also is banned in Free Commenting
* The same contents with URL Tags will be sent, and after I have approved the comment as Admin the Comment will be shown. But shown crippled:


BBC Source code shown instead of Words with link behind it.

And so I think: Its a bug, not a feature!

I have not yet tested that proceeding with 1.5 But I think for moderated comments URL tag should be allowed and be shown correctly in the comment.

CU

Rainer

[RainerBielefeld]

I have not yet tested

Now I did! My results with 1.5.Master:

1. In Free Commenting the "[url" string also is forbidden word here
2. Here now also in Moderated Commenting the "[url" string is forbidden word
3. Even commented out as "Code" the string will remain forbidden
4. And still in 1.5 FlatPress allows "naked" URL in Moderated and also in Free Commenting

[RainerBielefeld]

And still in 1.5 FlatPress allows "naked" URL in Moderated and also in Free Commenting

My workaround to allow the URL Tag_

1. open <..../fp-plugins/qspam/plugin.qspam.php> in text editor
2. in Line 28 in taling "['href', '[url'];" delete the contents between the square brackets, so that a line " $BAN_WORDS = isset($qscfg ['wordlist']) ? (array) $qscfg ['wordlist'] : [];" remains
3. Save plugin.qspam.php
4. ready, do your test

But I can't tell whether that might cause problems somewhere in other functions

[macadoum]

I'm not an expert with Github, but I sent a PR : https://github.com/flatpressblog/flatpress/pull/746

It's an updated version of the french translation using Copilot. This is only 1 file just to be sure the way I do it is good. Let me know.

[macadoum]

I'm not an expert with Github, but I sent a PR : https://github.com/flatpressblog/flatpress/pull/746

It's an updated version of the french translation using Copilot. This is only 1 file just to be sure the way I do it is good. Let me know.

Update : I tested the file produced by Copilot on my own 1.5 rc installation and it's working fine !

See :

[fraenkiman]

I'm not an expert with Github, but I sent a PR : https://github.com/flatpressblog/flatpress/pull/746

Thank you very much for the revision. Merged after a minor correction.

Best regards,
Frank