- Issue created by @jstoller
- First commit to issue fork.
- π¬π§United Kingdom scott_euser
Updating title, actually going through the code there is nothing else to suppress other than bypass error logging. Will similarly make the field names and labels reflect that.
Similarly I do not think its a huge ask for a site builder to specify the domains to restrict suppressing the error message for. Leaving blank for all means a config override can be added like the below to settings.local.php for local development for example.
$config['cloudflare.settings']['suppress_bypass_errors'] = TRUE;
Similarly could be wrapped in a more dynamic statement to have it bypassed on non-live hosts that automatically spin up environments like using PANTHEON_ENVIRONMENT for instance.
- last update
over 1 year ago Composer require failure - Status changed to Needs review
over 1 year ago 5:17am 25 October 2023 - π¬π§United Kingdom scott_euser
Here are the form inputs shown in the attached MR. The hostnames is conditional (form #states) on the suppress checkbox being checked.
- First commit to issue fork.
- π¬π§United Kingdom andreastkdf
The last commit is a re-roll for 2.0.x - merged 2.0.x and fixed conflicts. Pls ignore the other previous ones showing here, they are wrong, I've done a force reset, so the MR on git is ok and only showing my merge/fix conflicts commit.
- π¬π§United Kingdom pasive
As a side note to avoid other warnings the use of this MR requires a Database update and correct export of cloudflare config.
Pay a special attention to behaviour when use config split module. - π¬π§United Kingdom scott_euser
Thanks for your comment
The pipeline issues are part of the main branch and unrelated to this: https://git.drupalcode.org/project/cloudflare/-/pipelines - this does not introduce new issues, so that should be resolved elsewhere.
The fact that update hooks update config is expected, you can read more on that here: https://www.drupal.org/node/2535454 β
If the issue itself is resolved for you (ie, no more flooded logs) after using the merge request, perhaps you could mark it as 'Reviewed & tested by the community' to help progress the issue.
Thanks!