[D7] Drizzle [#2833038]

Drizzle (https://getdrizzle.com) is a free, full-stack solution for premium content creators to start selling their best content directly to website visitors. Once installed, you can sell paywalled content, set memberships and engage website visitors to increase number of paying users.

Learn more by watching 2 min video:
https://vimeo.com/182750960

This module will let you hide virtually any content in your posts (text, images, videos, links, and digital downloads). Your website visitors will be offered to pay for your content with just one click, or will be asked to provide non-monetary value -- such as sharing their contact information via signup or taking an action, such as page like, on social media.

Hide content by manually by including it in the following shortcode: [drizzle] Your great content. [/drizzle]
Alternatively paywall hundreds of pages by using our automated feature.

Our current customers double sales in 3 months after installing Drizzle.

Current Drupal module is successfully used on: https://coachesonly.breakingmuscle.com

Sandbox Link : https://www.drupal.org/sandbox/getdrizzle/2832019

Git clone : git clone --branch 7.x-1.x https://git.drupal.org/sandbox/getdrizzle/2832019.git

Comment	File	Size	Author
#8	Dizzle-issue.png	82.48 KB	muthukumar sri
#8	Drizzle-setting.png	86.51 KB	muthukumar sri
	Content Managment.png	45.44 KB	getdrizzle
	Key Configuration.png	14.41 KB	getdrizzle

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

5 December 2016 at 09:38

getdrizzle created an issue. See original summary.

Comment #2

getdrizzle CreditAttribution: getdrizzle commented 5 December 2016 at 09:39

Title:

Drizzle

» [D7] Drizzle

Comment #3

PA robot CreditAttribution: PA robot commented 5 December 2016 at 11:23

Issue summary:

View changes

Fixed the git clone URL in the issue summary for non-maintainer users.

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

Comment #4

3ssom CreditAttribution: 3ssom commented 5 December 2016 at 12:20

Assigned:

getdrizzle

» Unassigned

Hello,

Please dont assign this to yourself!

Thanx

Comment #5

3ssom CreditAttribution: 3ssom commented 5 December 2016 at 13:35

Status:

Needs review

» Needs work

Hello getdrizzle,

Automated Review

found some minor errors @
https://pareview.sh/node/286

Note that perfect adherence to Drupal Coding Standard is NOT a reason to block an application, except for total disregard of them. However, modules should follow them as closely as possible.

Manual Review

Individual user account

[Yes: Follows] the guidelines for individual user accounts.

No duplication

[Yes: Does not cause] module duplication and/or fragmentation.

Master Branch

[Yes: Follows] the guidelines for master branch.

Licensing

[Yes: Follows] the licensing requirements.

3rd party assets/code

[Yes: Follows] Also please read this the guidelines for 3rd party assets/code.

README.txt/README.md

[No: Does not follow] the guidelines for in-project documentation and/or the README Template.

Code long/complex enough for review

[No: Does not follow] the guidelines for project length and complexity.

Secure code

[Yes: Meets the security requirements. / No: List of security issues identified.]

Coding style & Drupal API usage

[List of identified issues in no particular order. Use (*) and (+) to indicate an issue importance. Replace the text below by the issues themselves:

automated test found some errors
(*) in your file .module .. line:21 you can fine yourself adding a library for jQuery and included a file ,, you should use Drupal in your favor here! by using jquery_update instead of using a file in your project .. just make it a dependency in your .info file.
(*) your implements of hook_menu() and using access arguments which is fine but why not making your own permissions ? why attach your pages with others(Use the administration pages and help)? you can use hook_permission() and then attach this menu to it! this goes for all of your items there.
(*) you are missing a .install file ,, you have a lof variables needs to be addressed in case uninstalling the module.
(+)There is no README file .. when you add it please see the the link here
(+) remove the line 346
(+) Please cover your drizzle_form_node_admin_content_alter function with t() where it needs to be added! also in the file drizzle.admin.inc the markup inst using t() there!
(+) Would be helpful if you implement hook_help().

Please can you provide a test API Key in your original issue so me or other reviewers can make a complete review without us registering ?

This is review for the files ,, I'll need the API Key to do a full review for the project! I'm putting this as "Needs work" for the notes mentioned above until a Key is provided and those were covered

The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.

If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.

This review uses the Project Application Review Template.

Comment #6

getdrizzle CreditAttribution: getdrizzle commented 9 December 2016 at 08:24

Hello 3ssom,

I have reviewed project as per given instructions from https://pareview.sh and fixed all the possible errors and bugs. please have a look once more and let me know your inputs.

Thanks

Comment #7

3ssom CreditAttribution: 3ssom commented 9 December 2016 at 11:48

Hello,

I see you covered the automated test for coding standards here which is good!

But what other inputs mentioned in my review ..along with the key so I can complete my review

Thanks

Comment #8

muthukumar sri CreditAttribution: muthukumar sri at Ameex-Drupal Geeks commented 9 December 2016 at 11:50

File	Size
Drizzle-setting.png	86.51 KB
Dizzle-issue.png	82.48 KB

Hi,

I have installed and enabled the module on a Drupal 7 site. Check the below issue

Issue:

If i enter the invalid entry in 'API Key *' field. I received error message. Refer screen shots.

Comment #9

getdrizzle CreditAttribution: getdrizzle commented 16 December 2016 at 09:58

Hello All,

I have fixed the given issues and also setup a demo site so that you can review it more. Please find the details bellow

Admin Login
User : admin
Pass: changeme
http://162.243.29.173/user

Drizzle Contents
http://162.243.29.173/admin/config/drizzle/content

Also if any one want to generate own key then you can do it from here-
https://app.getdrizzle.com/setup

Thanks to all of you for your reviews and waiting for you to hear if anything need to fix.

Thanks
Drizzle

Comment #10

3ssom CreditAttribution: 3ssom commented 18 December 2016 at 09:24

Status:

Needs work

» Needs review

you should have changed the status to Needs review ..

anyway I did that and I'll complete the request for you in a little bit ..

Thanx

Comment #11

3ssom CreditAttribution: 3ssom commented 18 December 2016 at 10:13

Status:

Needs review

» Needs work

Here we go ..

Coding style & Drupal API usage

[List of identified issues in no particular order. Use (*) and (+) to indicate an issue importance. Replace the text below by the issues themselves:

You still have some errors showing by pareview.sh

(+)when enabling your module this errors show:

    Notice: Undefined property: stdClass::$data in drizzle_http_post() (line 228 of /sites/all/modules/drizzle/drizzle.module).
    Notice: Undefined property: stdClass::$headers in drizzle_http_post() (line 231 of /sites/all/modules/drizzle/drizzle.module).
    Notice: Undefined property: stdClass::$data in drizzle_http_post() (line 231 of /sites/all/modules/drizzle/drizzle.module).

(+) you still have some texts there => Please cover your drizzle_form_node_admin_content_alter function with t() where it needs to be added! also in the file drizzle.admin.inc the markup inst using t() there!
(+) Would be helpful if you implement hook_help(). at the top of you .module
(+) I would suggest you create a folder inside your module directory called (include) and move drizzle.admin.inc in there .. it make is easier to look at the files :)
(+)in you file:drizzle.admin.inc .. the $msg can be easily replaced with drupal_set_message(t('API Key is invalid'), 'error') or 'status' in the second parameter so it shows a success msg!
(+)in you file:drizzle.admin.inc please use t() in your markup!
(*) I registed in the site(getdrizzle.com) then got my own ,, but it does not work:
API Key is invalid!

So I couldn't also complete the review because of the key!

Comment #12

getdrizzle CreditAttribution: getdrizzle commented 21 December 2016 at 11:01

Hello 3ssom,

Thanks for your review, we have fixed all the issues given in your review, please have a look once and let me know if anything need to be fixed.

Thanks!!

Comment #13

3ssom CreditAttribution: 3ssom commented 22 December 2016 at 10:50

Hello,

(2) is still as it is .. the errors isn't gone.!

(3) I can see you used t() in your markup .. but the way you used is WRONG .. don't put the whole code into the function? you can us this get_t() also links in a @link!

(8) still the key isnt working and giving a (API Key is invalid!) msg!

Comment #14

getdrizzle CreditAttribution: getdrizzle commented 23 December 2016 at 08:58

Hello 3ssom,

I have checked for that key issue two times, would you please give me some steps so that i can reproduce it at my end ?

Thanks for you reviews

Comment #15

getdrizzle CreditAttribution: getdrizzle commented 23 December 2016 at 11:08

Also i have fixed that markup t() function, please have a look now and provide your review.

Thanks

Comment #16

PA robot CreditAttribution: PA robot commented 13 January 2017 at 11:26

Status:

Needs work

» Closed (won't fix)

Closing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).

I'm a robot and this is an automated message from Project Applications Scraper.