- Issue created by @van.dordafog
set
$settings['swiper_formatter__forbid_remote'] = TRUE;in settings.php- 🇳🇱Netherlands nk_
Could you please elaborate on GDPR compliance and Swiper, the license type? Willing to hear the idea behind this request.
Other than that, at the first glance it seems like an edge case rather, which should probably be resolved per case, I think it's even doable in CSS (hide radio). Unless end users (clients) are enemies who look thoroughly how to undermine their own platform : )
Excuse the wording. The idea would be to guarantee that no external assets are being loaded. With a relatively simple check on all module libraries, instead of having to analyze the config. I think there's GDPR aspect to this but probably the main the concern is a supply chain attack
- 🇳🇱Netherlands sebastian hagens Breda, Netherlands
With this feature, with what section of the GDPR would it comply with?
I would suggest to move the forbid boolean to a generic configuration entity (which does not exist, but it could be
swiper_formatter.settings.yml).