Title says it all.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 1186042-pi-content-extra-fields.patch | 1.06 KB | dave reid |
| #1 | 1186042-pi-content-extra-fields.patch | 944 bytes | dave reid |
Title says it all.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 1186042-pi-content-extra-fields.patch | 1.06 KB | dave reid |
| #1 | 1186042-pi-content-extra-fields.patch | 944 bytes | dave reid |
Comments
Comment #1
dave reidComment #2
dave reidComment #3
webchickGreat!
The patch in #1 had the help text at the top of the issue kind of showing up in random places, but the one in #2 correctly exposes all of the fields. I was able to re-order the fields and get the *@#ing revision fieldset down where it belongs. YAY!
Code looks good and conforms to coding standards. I don't believe this needs automated tests, because it's just hooking into a CCK API, which should have its own tests. RTBC!
Comment #4
dwwThanks! Tested and working properly. Committed to 'master':
http://drupal.org/commitlog/commit/1894/06935546b7aac96b2b916fa335dfd65e...
However, I noticed that core CCK using trailing periods for these name fields, so I added those for consistency:
http://drupal.org/commitlog/commit/1894/d18542ef3d4d012d591d89c08c78dfb2...
Another step closer to #1036132: Provide a mechanism for issue summaries ... ;)
Comment #5
webchickOops. Good catch.
Thanks SO much for the commit, dww! :D YAY! :D