Use nodes for Feedback messages

I think I agree. (although I intentionally chose to not use nodes for Feedback as this is rather a development module originally)

The question is, however, how do we ensure the following

- The "Feedback" content-type should not be displayed on the node/add page.
- The feedback form should not contain the usual extra fields for menu, comments, author, publishing options, etc.
- If Fivestar/Voting API comes into the game, I guess it should not be displayed on the feedback form, but rather when viewing existing feedback messages.

After further consideration, this issue depends on #293512: Abstract back-end for integration with 3rd party issue trackers, as Feedback should also be able to use Project Issue or CaseTracker as backend.

Here's another idea, rather than use messages as a node, have feedback create a node along side a message without using the node creation front end. The webmaster would be able to choose a tokenized title for the node, as well as which field to insert the message itself in. Then a node gets created without ever exposing the user to the form, and there would be no need for a new node type, the webmaster would be able to choose page, story, issue, or case as the case may be. :)

ok, that's so trivial that I even did not think about it. ;)

Anyway, to achieve this, the back-end needs to be pluggable/swappable. Hence, marking as postponed for now.

Hi, I wonder what the timeline for this is, because this actually sounds like something I can implement on my own even without a dedicated module. Going back to what you said about using a node form's interface, I can get the form in a block, apply hook form alter on it, and use one of the ajax modules to get ajax submission.

All in all I think I can get pretty close to my ideal setup without using the Feedback module. What are your thoughts on this?

You can uninstall probably 99% of all contributed modules by following this argumentation. Modules are here to standardize and improve certain features, behaviors, and functionalities.

While I understand that feedback using nodes would allow us to leverage all the fancy things that nodes allow us to do, I am a little concerned about privacy: I surely would not want that
- feedback nodes show up in search results
- allow everyone to read customer feedback by guessing its URL (trying node/1, node/2, etc. until something shows up).

since nodes adhere to drupal permissions, you as a system admin would have full control.
We would just have to specify the following permissions:

create feedback
delete all feedback
edit all feedback
delete own feedback
edit own feedback

I also feel this is a great idea, I would love to replicate User Voice functionality.

I'm available to help, so subscribing.