Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
30 Jan 2012 at 17:05 UTC
Updated:
31 Aug 2012 at 10:24 UTC
Inspired by the djangohandbook.com this module allows you to place comments in-line within a piece of content.
To add an in-line comment block to a peice of content simply wrap the content as follows:
<div id="inline-comments-{integer}">
<!-- Content -->
</div>Where {integer} is replaced with a positive integer that is unique to that section within that node. Simples!
Project Page: http://drupal.org/sandbox/edb/1420684
Git Repo: git clone --branch 7.x-1.x http://git.drupal.org/sandbox/edb/1420684.git
Drupal Version: 7.x
Comments
Comment #1
rudiedirkx commentedThe README is a little short. "Inspired by the djangohandbook.com" is not enough for a reader to know what this module does.
Don't tell me. Put it in the README (and on you project page).
Comment #2
rudiedirkx commentedYou should be able to call
$comment_formdirectly. No$variables. A list of available variables would be very helpful, not just the file doc. Likepage.tpl.php.Comment #3
edb commentedThanks for the feedback, I have updated the README, project page and the tpl file. The changes have been committed.
Comment #4
chrisroane commentedMANUAL REVIEW
--------------
1. I enabled the module and verified that it works. However, the hover of the content doesn't match the height of content that it is wrapped around? This is in Chrome.
2. The previous button just closed the comment popup and nothing happened (Chrome).
3. When I got to a page with these comments when I am not logged in....it still does the on hover (gray), but when I click on it, it opens a blank popup.
4. Correct me if I'm wrong, but I think people would like options such as: Allow anonymous comments and the format of the comments that they allow (or just allow plain text).
5. With a large page that has many of these comments, it seems like human error could easily miss number the "id" values of the blocks. Why couldn't you just use one class around these divs? I'm not sure exactly how you would determine exactly which comments belong to which div, but this doesn't seem like a very user friendly way of doing this. One option that came to mind is still use id values, but generate a db value and do a search and replace when they save.
AUTO REVIEW
------------
Nothing came up via Coder or the online PAReview tool.
Comment #5
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.