It looks like once this module is installed it overwrites the standard comment functionality for any content type. The "Job" comment functionality should only be in effect if creating a comment on a job node. Thanks and great work.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 380666.png | 91.81 KB | roball |
Comments
Comment #1
jeremy commentedWhat are you referring to? Please provide more details as to what you are experiencing.
Comment #2
bfsworks commentedTo specify further, once the Jobtrack module is installed it does not matter if you create default page or story content type when you add a comment the "Job Track" comment form is displayed instead of the default durpal comment form. The module needs to be edited to filer by content type so it does not interfere with content types that do not apply to Jobtrack. I hope this helps.
Comment #3
Krupp commentedSame problem here. Comments on any content type require to specify Jobtrack info.
Comment #4
roball commentedCan confirm this bug. Attached is a screenshot showing how it looks when someone wants to add a comment to a "page" node post. Jeremy, can you now confirm this bug?
Comment #5
jeremy commentedI'll review this before I roll the next release. On my system the only code running is jobtrack, which is why I would not have run into this myself.
Comment #6
jeremy commentedFix committed.
Comment #7
roball commentedWow, thanks a million for the super-quick fix!
Comment #8
roball commentedI have just upgraded to v6.x-1.x-dev (2009-Mar-09) and can confirm that the bug is gone now. That version is working great!