Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
13 May 2013 at 17:45 UTC
Updated:
17 Jul 2013 at 06:47 UTC
Integrates the Helponclick Live Chat Software to the website.
Project pge:
http://drupal.org/sandbox/bnorbi/1993672
Git repository:
git clone --branch master bnorbi@git.drupal.org:sandbox/bnorbi/1993672.git
| Comment | File | Size | Author |
|---|---|---|---|
| helponclick.jpg | 14.34 KB | bnorbi |
Comments
Comment #1
ankitchauhan commentedwelcome
It appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Review of the master branch:
while waiting for an in-depht review of your module you can start out fixing some coding style issues detected by automated tools:http://ventral.org/pareview/httpgitdrupalorgsandboxbnorbi1993672git
We do really need more hands in the application queue and highly recommend to get a review bonus so we will(/can) come back to your application sooner.
Comment #2
bnorbi commentedThank you ankitchauhan to helped me on this topic.
I have followed all of your helpful instructions and fixed the code-style issues and also made a 7.x-1.x branch according to the instructions.
So here is my appropriate git repository:
Thanks again!
Comment #3
ankitchauhan commentedUpdating status
Comment #4
lchang commentedHi, bnorbi
The README.txt doesn't contain a basic overview of what your module does and how someone may use it.
The contents of the file may be a repeat of the synopsis on your project page.
Comment #5
bnorbi commentedI forgot it, sorry. Now I added the contents to the README.txt file.
Thanks!
Comment #6
stefan lehmannHi there!
Automatic review: The code is clean.
Manual review:
Actually I don't really get what your module does, which you couldn't achieve (even better) with a couple of clicks with the native block system? Please explain what extra functionality you get by using your module instead of the block system.
Comment #7
stefan lehmannComment #8
bnorbi commentedComment #9
stefan lehmannI still don't see how your module integrates this special service. You can basically copy / paste any embed code into your embed text field. As long as it contains the string "helponclick" somewhere in the markup it will be accepted as a valid embed code and will be displayed on the website.
I could see some kind of integration if you would provide a textfield where the user enters a code provided by the "Helponclick Live Chat" website and your module would generate the appropriate embed code. At the moment your module doesn't seem to do anything useful, which couldn't be done better by using a standard block (apart from checking that the string "helponclick" is part of the saved content). Sorry I don't want to be rude, but that's just my opinion.
Comment #10
kscheirerI agree with Stefan, it would be better to use a plain block. Blocks already have a method for setting visibility on various regions/pages/urls/users.
In fact, that's what the docs on http://www.helponclick.com/live-chat-software/integration/drupal.html describe.
If you feel strongly that this module would make it easier to use your service, perhaps it could define a default block and use the same embed code? That would integrate a little better with Drupal.
----
Top Shelf Modules - Enterprise modules from the community for the community.
Comment #11
bnorbi commentedOk Guys,
You are right.
I don't want to populate this module anymore.
When I make an other more useful module, I will.
Thank you for your help.