I'm guess this will be an issue with flag_abuse/flag 2.x and flag_note
Flag note using a different url
from flag_abuse 1.0
$vars['link_href'] = str_replace('unflag', 'reset', $vars['link_href']);
changed in 2.x to set action instead of changing the url, haven't tested it yet to see what will happen (near-production site this issue was having issues with, so can't risk upgrading to flag 2.x/flag abuse 2.x atm).
but flag_note 1.x changes the url
function flag_note_flag_link(&$flag, $action, $content_id) {
$token = flag_get_token($content_id);
return array(
'href' => "flag/note/$action/$flag->name/$content_id",
'query' => drupal_get_destination() .'&token='. $token,
);
}
so the reset url doesn't lead to the flag_page (flag/action/flagname/content type id) but to flag_note_page (flag/note/action/flagname_content type id), which doesn't handle anything but flag and unflag actions. Maybe flag_note issue instead; or rather a flag_note issue for flag 2.x when additional options are handled.
(for flag_abuse 1.x I did an additional str_replace to get rid of the /note. )
Comments
Comment #1
sirkitree commentedflag abuse 1.x is going away 2.x imminent