I have a content type called 'event'. The FormID for this is called 'event_node_form'.
I put 'event_node_form' in the settings, and selected Whitelist, as I only want the alert to show in conjunction with this form.
I go to Create >> Event form and click some other link while there, but no alert.
I go to some other content type form ('Group') and click away and get the warning, even though I did not list this form ID (group_node_form).
I go to yet another content type ('Story') and click away: no warning.
I tell Dirty Forms settings to Blacklist 'group_node_form' but I still get the alert on that form, but no others.
I set it to 'Disabled' and I no longer get the alert on the Group form.
Since the alert will only seem to fire on my group node forms, I can only see any troubleshooting there. The 'highlight' setting has no effect, as our site is completely custom themed and throws out all the Drupal pink/unpublished classes and whatnot.
The Group form (which is yes an Organic Groups content type) is firing because it says the og_selective field changed, but of course it hasn't changed.
Any thoughts or suggestions are welcome. Thanks.
Comments
Comment #1
brockfanning commentedI could be wrong, but I believe I was also having the same problem when trying to add a single whitelisted item, and putting a comma after the item worked for me.
Comment #2
brockfanning commentededit: Yes I was wrong. I ended up getting it to work by making the rule more general, along with wildcards. My form's id was "node-form", but I couldn't get this to work until I used the rule: *node*
Seems like maybe my id was actually something other than "node-form", but that's what showed when examining the page source.
Comment #3
ccshannon commentedThanks, I will try this!
Comment #4
markus_petrux commentedPlease, visit the Dirty Forms settings panel and play with the troubleshooting section options.
hmm... this works for me.
In general, make sure there is no javascript error on the page. Also, enable the troubleshooting options to get some hints on what the module is doing. Also, if there's a WYSIWYG enabled textarea in the page, try disabling that to discard possible issues there.
If you enter more than one rule, separate them with commas. Note that hyphens will be converted to underscores prior to checking for matches in the form ids.
Not really sure what else to say here. It seems to work here, so I cannot reproduce malfunctions when checking for defined rules.
BTW, try with latest dev version to make sure your issue is not related to anything that has already been fixed.
Comment #5
bryan kennedy commentedI had the exact same problem. Thinks for your workaround. When I put *node* in I am able to filter the node-form form. I still think this is a bug, since that is the correct form id for the item.
Comment #6
arvindkt commentedYou still need to put *node* to make "node-form" work in whitelist.