Adding two policies with same name (neglecting case) causes error

Testbot could not apply your patch. It looks to me like the problem is the patch file does not have a newline character at the end of the last line in the file. I'm not sure how that happens. Vim indicated this with "[noeol]". Resaving seemed to fix.

By the way, it looks like line 17 of the patch adds a trailing space.

Thanks for the patch.

Fixed aforementioned newline problem and removed trailing space.

Running tests locally you can get a snapshot of the page after each request. That should be elucidating. Am running the tests locally now.

The problem with the code in the patch: If you edit and save an existing policy, you get "Duplicate policy name."

To reproduce: Create a new policy, save, then edit, and re-save.

The test failed because it just happens to edit an existing policy as part of the test, which causes the "Duplicate policy name."

Same problem as in #2: no newline character at end of last line in patch file. Are you producing your patches using Git? The following should work:

git diff >foo.patch

Are you familiar with git add -p? That is what I use most often for picking out some changes from many for a patch. You add selectively to the index from the working tree, then git diff --staged >foo.patch to diff the index versus HEAD. Maybe you already know about it, but I had been using Git for a while before I started using it.

Looks good to me. Two minor changes:
1. Remove hyphen from "case-sensitive". (I think the grammar rule is compound modifiers following the noun they modify do not get a hyphen.)
2. Change $dup_name to $dupe_name to avoid abbreviation. ("dupe" is informal adjective meaning the same as duplicate per at least one dictionary.)

It might be more conventional to solve this by having a human-readable name and a machine name--not sure. But this patch seems to fix the bug and that is most important.

The return TRUE; line in the validate function is pointless, I think, but it can be removed separately.

Went ahead and committed. Thanks for the fix!

The changes in #22 are not functional changes and can be fixed later if I have erred.