This module provides a way to integrate with Peanutlabsmedia.The Peanut Labs Media Monetization Platform is designed specifically to work with virtual currencies and goods in the new digital economy - be they social applications on Facebook, Myspace or Linkedin, or leading Games and Gaming communities.
You can learn more about Peanut Labs at http://www.peanutlabsmedia.com/.
* You can see this module in action at http://bliss-dev.com/drupalcontributions/take-survey/get-points
* The Administrator can configure the settings from here http://bliss-dev.com/drupalcontributions/admin/settings/peanutlabsmedia
Please Login with Username: demo Password:demo
The module is ready, verified with coder and tested for functionality.
We plan to contribute a number of modules back to the community -- this is just the start. A few details about us can be found in the attached presentation. You can also read about the modules at www.blisstering.com/blog .
Thank you.
PS. We had applied for a CVS account earlier to start this process of contributing modules to the community. Specifically, we had started with the autocreategroup module. We had assigned the task to a newbie as part of his Drupal training process. That individual is no longer with the company. We will ensure that all subsequent modules will be managed by seasoned Drupalers at Blisstering.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | peanutlabsmedia.zip | 2.81 KB | blisstering |
| #6 | peanutlabsmedia.zip | 4.35 KB | blisstering |
| #1 | peanutlabsmedia.zip | 2.86 KB | blisstering |
| #1 | Blisstering Drupal Overview v6.ppt | 326.5 KB | blisstering |
Comments
Comment #1
blisstering commentedUploaded the zip format of the module and Blisstering Company Overview.
Comment #2
blisstering commentedChanging status to needs review.
Comment #3
avpadernoHello, and thanks for applying for a CVS account. I am adding the review tags, and some volunteers will review the code of the proposed project.
Comment #4
blisstering commentedHi kiamlaluno,
This is just a gentle nudge to remind you to review our CVS application. If you find some time can you please tell us the status of this application, so that it will help us to contribute this proposed project to drupal.org community as soon as possible. Once we figure the mechanics of doing this once, we have several more modules to contribute (you can learn more at blisstering.com/blog).
Thank you.
Comment #5
avpadernoThere is no need to set Drupal variables on
hook_install(); the second argument ofvariable_get()is the value that will be returned when the variable has not been set before. As Drupal variables are loaded in memory each times Drupal bootstraps, if every module would initialize its persistent variables in that way, the used memory would increase.Deleting variables as done in
hook_uninstall()is not suggested. The code could delete variables used by other modules. There is nothing that forbids to a developer to create a module called peanutlabsmedia_services, in example, and the code would deleted the variables of that module too.Permission string should use the verb in lower case (, , etc).
Strings used as titles should be in sentence case ().
To avoid conflict with other modules, the menu path should include the module short name.
There is a Drupal function with the same purpose; the module should use Drupal functions, where there are functions suitable for the purpose.
Comment #6
blisstering commentedHi Kiamlaluno,
Thank You for your valuable review. I done the following changes as per your previous post. Please find the attached module for further review.
* Removed the code that sets the drupal variable on hook_uninstall(); as per your first point.
* Changed the code in hook_uninstall which deletes the variables on hook_uninstall(); as per your first point.
* Permission string is in lower case now as per your second point.
* Changed the title to sentence case as per your third point.
* Changed the menu path as per your fourth point first section.
* Changed the code which include files using the drupal api function module_load_include($type, $module, $name = NULL); as per your fourth point second section.
Changing the status to needs review.
Thank You.
Comment #7
avpadernoMenu titles, and descriptions should not be passed to
t()as that is already done by Drupal core code.Except for what reported in the previous point, strings used in the user interface should be translated.
l()should not be used togethert(); the first fragment needs to be changed to useurl()instead ofl().The code should use
variable_del().Comment #8
blisstering commentedHi kiamlaluno,
Once again thank you for your valuable review. Here is the update module with the changes mentioned in the previous post. Please find the below changes in the attached module.
* Removed t() function from menu titles and description as per your first point.
* As per your second point first fragment url() is used with t() function.
* As per you second point second fragment all the user interface strings except menu titles are wrapped inside t() function.
* As per your third point variable_del() is used instead of db_query().
Changing the status to needs review.
Thank You
Comment #9
avpadernoThat call is already done by
variable_del().The first argument of
t()must be a literal string; differently, the script that extracts the string to translate to create the translation template will not be able to extract the string, which would not be translatable (if not in the case another module uses the same exact string, but it's rather difficult it happens, when the string is dynamically changed).The correct code should use
t()-placeholders.Thank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the dedicated reviewers as well.
Comment #10
blisstering commentedHi Kiamlaluno,
We are glad to hear from you and thank you for giving access to CVS account. We are excited to on board with Drupal Community and looking forward to maintain and contribute many modules in near by future.
We will make the changes mentioned in the above post and will follow all the necessary coding practices for the upcoming projects.
Thank You.
Comment #13
avpaderno