dbro

Sorry needs to be ungreedy.. use this instead:

if ($minify_html_comments != 'no') {
  $process = preg_replace('/(<!--{)(.*?)(}-->)/','@#_###{$2}###_#@', $process);
  $process = preg_replace('/<!--(?!\s*(?:\[if [^\]]+]|<!|>))(?:(?!-->).)*-->' . $mod, '', $process);
  $process = preg_replace('/(@#_###{)(.*?)(}###_#@)/','<!--$2-->', $process);
}

Done.

Well a good start would be that any files that generate/create browser output are implemented as WordPress templates. That would allow the plugin to integrate better with WordPress themes. Functional hooks would still need to be added where appropriate in the business logic.

Once the plugin has a good software design structure it will make it more flexible to allow anyone to make all these small custom “cosmetic” changes. It would also reduce the amount of support effort/time of people asking for small custom changes, because everyone could now make the small changes that they need themselves without bothering the plugin developers.

I see by the activity of this forum that there is a need for a good GDPR solution. IMHO so far this plugin is the best from all of them available as far as GDPR completeness.