Closed (won't fix)
Project:
Drupal core
Version:
8.0.x-dev
Component:
forum.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
30 Apr 2009 at 03:55 UTC
Updated:
29 Jul 2014 at 18:15 UTC
I started development in the forum install profile. Link to releases.
Comments
Comment #1
mitchell commentedand views
Comment #2
catchBy CCK do you mean replacing the forum / taxonomy dependency with field API? I'd be more tempted to use something like book / menu does for the hierarchy handling. Does this need to be postponed on views in core then?
Comment #3
damien tournoud commentedYou should not name any of the drupal.org project using the same name as a core module. This would prevent us to extract move modules out of core at a later stage.
Please rename your module.
Comment #4
michelleI complained about this 18 weeks ago and have been ignored: #349794: Change project name to avoid namespace conflict with forum.module Thought I admit the namespace needs of core forum moving to contrib hadn't occured to me. I was just concerned about having something that isn't related to core forum named "forum". That's a very good point about the core->contrib path.
Michelle
Comment #5
damien tournoud commentedComment #6
mitchell commented@catch: Yes, a major design improvement, imho, is that this implementation does not depend on taxonomy. The content types use node references, and it works very nicely.
A major portion of this is postponed till #286665: SEE ISSUE #1805996 -- Moving Views into Drupal Core and even more so #363410: Port Views to the Drupal 7 database layer. However we can still cover other aspects here, such as modeling the content types, discussing functionality, etc.
@Damien Tournoud: Please avoid changing issues away from the author's intent. As Michelle pointed out, an issue already exists: #349794: Change project name to avoid namespace conflict with forum.module. Please continue that discussion or create another issue in the Drupal.org webmasters queue.
Comment #7
webchickComment #8
giorgio79 commentedHello opensanta,
Is this still on the plate? :)
I have found this by searching on how to put a forum on each node. Kind of like Amazon's product pages where each product gets a forum.
There was a discussion here as well for the same request:
http://drupal.org/node/137456
Comment #9
catchOn the plate to the same extent that Views in core is on the plate. However look at advanced_forum in contrib for most things forum related.
Comment #10
michelleJust doing some cleanup... Views is not going into D8. Moving the forum to "CCK" makes no sense, even if you substitute "Field UI". While it may be possible that core forum gets radical changes some day, I seriously doubt it will be in D8 and there's not a lot of point in keeping this issue open, even postponed, when it will be years, at least, before anything happens. If someone decides to do a massive change of core forum, I'm sure they can handle making a new issue for it. :)
Michelle
Comment #11
webchickSorry, but why is Views not going into D8? We are in code thaw, after all. :) Anything's on the table. There are also initiatives to at least put entity-level listing pages into core, ala #1210366: Per-bundle node listing pages, blocks, feeds..
Comment #12
michelleSorry, I thought merlinofchaos said it wouldn't happen in D8. If I'm mis-remembering, I apologize. I mostly closed this one since it's an old, mixed up issue that's changed focus once already. I figured if anyone decides to mount an effort to put a Views-based forum into core that a nice fresh issue would make more sense. If I'm wrong, feel free to re-open. I was just trying to clean up. :)
Michelle