Maybe this won't be necessary, but I imagine it will...

It would be great to create a mechanism to ignore false positives. The coder module has this feature now and it seems likely it will be necessary here as well.

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Here's an example:

--- openpublic_splash/openpublic_splash.module 2011-03-12 14:39:54.000000000 -0700
+++ ../old/openpublic_splash/openpublic_splash.module 2011-03-12 13:30:36.000000000 -0700
@@ -261,7 +261,6 @@ function openpublic_splash_toggle_demo_c
//module_load_include('inc', 'system', 'system.admin');
if (module_exists('openpublic_demo_content')) {
module_disable(array('openpublic_demo_content'));
- // @todo 7 In drupal_set_message(): One or more of the replacement parameters to t() is not guaranteed to be check_plain() safe.
drupal_set_message(t('Demo content has been disabled. !link', array('!link' => l(t('Reenable demo content'), 'admin/content/demo-toggle'))));
}
else {

Can we make it smarter so it knows that the !link is filtered by l but does not have html => TRUE?