This might be a bug against forum.module, but I'll let someone else file it against that if that's so.
When you use mailhandler to gateway email into a forum, it's correctly assigning the tids so that the post is within the right forum taxonomy (forum table), but the other term table, term_node is not populated, so the forum posts do not appear within the forum itself. In other words, they are members of the forum category, but browsing the forum doesn't display them... (Yes, Forum uses 2 tables for the same thing... it's due for a fix)
Editing the node fixes this, as it adds the right term_node entry...
But that doesn't help us in this case, since mailhandler (or forum.module as called by mailhandler) creates the nodes with a problem, and we shouldn't have to edit them to fix it.
Comments
Comment #1
moshe weitzman commentedplease stop posting issues against mailhandler when they belong under a different module. mailhandler doesn't give a shit about any node type. it HANDLES INCOMING MAIL. thats all. it is up to modules to use hook_mailhandler to transform incoming mail. only the module itself understands how it needds its data
Comment #2
sethcohn commentedfine, bug report moved to forum.module... it IS a bug, and if mailhandler's not the place, this must be.
Comment #3
moshe weitzman commentedComment #4
magico commentedComment #5
liam mcdermott commentedAm changing the title to better reflect the underlying issue and marking #86998: Editing a forum node without an entry in the database "forum" table as a duplicate. Note: I have no idea whether this is possible (or even sensible), but it is what's being asked for in both these issues.
Comment #6
Emad commentedregarding forum & term_node tables:
from my understanding of forum module the forum table is used for performance issue otherwise queries become very complex, I don't think you will see "fix" of that soon.
maybe it saved in term_node but not in forum table, check forum_nodeapi --case 'insert' and reuse.
[written by Drupal newbie]
Comment #7
sethcohn commentedThe utter irony of this issue coming back to life (it was quiet since 2006) is that just yesterday, Moshe and I finally met in person, and were working on a project which involved replacing using forum.module (and og_forum) with only using content types/taxonomy/cck/etc (and og_vocab) and yet keeping the site looking and functioning the same otherwise.
Comment #8
webchickThe forum table is necessary in order to not break shadow copies. We already tried to get rid of it during the 6.x release cycle. See http://drupal.org/node/172643.
So if that's all this issue is about (it's kind of hard to tell), then it's won't fix.
Comment #9
liam mcdermott commentedI'm going to go out on a limb and mark this won't fix. If this is a fixable problem it would be better to raise a new issue anyway, this one is a little confused.
Comment #10
sethcohn commentedRenaming to better reflect the underlying question: forum nodes have to have a entry in the forum table. Other modules don't seem to deal well with this, including mailhandler (my initial cause for this issue), and other methods like changing/moving nodes. This should be dealt with someplace, and hopefully within the forum module itself... No idea how, but certainly the issue remains: you can create forum nodes in ways that don't correctly appear within the forum solely because they don't appear in the forum table, despite being correct in every other way... isn't there something the forum.module could/should do about that, especially if we aren't going to get rid of the forum table?
Comment #11
webchickAre you sure this is still an issue in 6.x/7.x? One of the forum improvements in 6.x is the ability to store any type of node as a forum node, and I believe it's taking care of managing the records in that table.
Comment #12
michelle@sethcohn - 7 months and no answer. Is this still an issue or should it be won't fixed?
Michelle
Comment #13
sethcohn commentedAgreed. Clearly, nobody cares enough to fix this for 5.x, despite that it's still broken. Forum module users are warned that the above issue can still happen.