Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 Feb 2014 at 17:44 UTC
Updated:
3 Jun 2014 at 16:26 UTC
Jump to comment: Most recent
Comments
Comment #1
sandykadam commentedComment #2
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxsandykadam2189611git
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #3
sandykadam commentedFixed the automated coder review issues. Please review again.
Comment #4
th_tushar commentedIt seems that the git branch is not named as per Git Branch Naming Conventions. Please follow the drupal git branch naming conventions for it.
Code looks fine to me.
Comment #5
th_tushar commentedRemoving the PAReview: review bonus, as you have not done any manual reviews of the modules rather than copied the result from the pareview.sh automated result.
You can do another 3 manual reviews of the modules and add the PAReview: review bonus tag.
Comment #6
sandykadam commentedGit changes done
Comment #7
th_tushar commentedPlease update the proper git repository URL in the issue summary.
You haven't done any manual reviews of the other projects, so please do another 3 manual reviews of the modules and add the PAReview: review bonus tag.
Comment #8
sandykadam commentedComment #9
sandykadam commentedUpdated!
Comment #10
sandykadam commentedComment #11
sandykadam commentedComment #12
sandykadam commentedAdded manual reviews again & modified issue tag to PAReview: review bonus
Comment #13
abghosh82 commentedFirst of all the idea behind the module is good, but do we have any such custom modules already in D7? I haven't come across any though.
Before I jump into the code for manual review I tried to install the module. Here are some of suggested improvements:
If the module is intended to be a D7 module then change this issue name to something like "[D7] Google A/B Testing", this is the nomenclature that is followed while creating issues to propose a module.
Add module name with the git clone command provided above, something like below:
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/sandykadam/2189611.git google_abtesting
So that it will clone to correct module directory with a meaningful name.
If the module is intended to be a D7 module then the module info file has a fault, please correct it
core = 7.x-1.x-dev should be core = 7.x
The Readme file should have some information about how to get the experiment key from Google.
With the above comments setting it to needs work.
Comment #14
abghosh82 commentedComment #15
sandykadam commentedComment #16
sandykadam commented@abghosh82 Thanks for reviewing. I have updated the module as you mentioned.
Comment #17
nonsieHow is this module different from https://drupal.org/project/multivariate ?
Comment #18
sandykadam commented@nonsie Multivariate has it's own logic of setting up multi variant pages and find out the winner, it does not use Google Analytics. Also it is bit complicated to use and doesn't support multilanguage and panel pages.
Where as this "Google AB Testing" module interface is easy to use and it helps you to integrate AB Testing from Google Analytics. You just need to create your different variant pages and add it in Google Experiment and get the code which you need to enter in CMS for that particular page. Once the experiment is started you can start tracking stats in Google Analytic interface. You can add it for panel page or node pages.
Comment #19
klausiYou should add the differences to existing projects to your project page, so that users can make an educated choice.
There is also
https://drupal.org/project/google_website_optimizer
https://drupal.org/project/split_test
I think this should be merged into the google_website_optimizer project. Module duplication and fragmentation is a huge problem on drupal.org and we prefer collaboration over competition. Please open an issue in the google_website_optimizer issue queue to discuss what you need. You should also get in contact with the maintainer(s) to offer your help to move the project forward. If you cannot reach the maintainer(s) please follow the abandoned project process.
If that fails for whatever reason please get back to us and set this back to "needs review".
Comment #20
sandykadam commented@klausi Thanks for your review.
Well if you go through each module you mentioned above you will find lot of difference and almost out of date.
google_website_optimizer - Was using old google "Website Optimizer" service which is already closed by Google you can read here - https://support.google.com/analytics/answer/2661700?hl=en-GB. This module still has the old process of implementing Website optimizer which doesn't work as Google itself not providing those kind of JS code which are mandatory fields in this module. If you see above Google support link they have created new service to cater Google AB Experiments and that is what my new module is going to do.
split_test - Is ages behind and has D5 version. It has basic concept of tracking hits on given page and gives you report. It is not an AB testing in real world
So I would suggest please go through my module and have a look at it and also have a look at Google Experiments in https://www.google.com/analytics
Thanks
Comment #21
klausiI see, then please add the differences to the existing projects to your project page. See https://drupal.org/node/997024
Comment #22
sandykadam commented@klausi Thanks updated the project page
Comment #23
klausimanual review:
<script>alert('XSS');</script>as experiment path I will get a nasty JavaScript popup on the overview table. You need to sanitize user provided text before printing. Make sure to read https://drupal.org/node/28984 again. And please don't remove the security tag, we keep that for statistics and to show examples of security problems.5'; alert('XSS'); a='as Domain name I will get a nasty javascript popup on pages that have an experiment configured. You must either make sure that the domain is sanitized properly before it is used in the script tag or you mark the administrative permission used to set this value as "restrict access" => TRUE, which means that only high level admins can use your module who can take over the site anyway.Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Comment #24
PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application (see also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.