Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Nov 2013 at 13:41 UTC
Updated:
22 Dec 2015 at 11:44 UTC
Jump to comment: Most recent
Comments
Comment #1
sch4lly commentedComment #2
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxsch4lly2135763git
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 #3
sch4lly commentedJust fixed the errors found by the PA robot.
Comment #4
neerajskydiver commentedStill getting following errors
http://pareview.sh/pareview/httpgitdrupalorgsandboxsch4lly2135763git
Also you should not use "master" branch in git. You should create a version specific branch.
Comment #5
sch4lly commentedNow i'm using the 7.x branch (is this correct?) and replaced the call to t() (which was causing the warning) with format_string(), since the variable can be translated without t(), using i18n_variable.
Link to pareview: http://pareview.sh/pareview/httpgitdrupalorgsandboxsch4lly2135763git-7x
Comment #6
neerajskydiver commentedYou should delete the master branch.
Module functionality is working as expected
Try reducing number of lines of code especially in this function
You should try like this
Comment #7
sch4lly commentedI just deleted the master branch.
Are you sure i should reduce the number of lines? I think it's more clear what the code does, if it's one condition per if statement.
From Drupal coding standards :
Comment #8
sch4lly commentedComment #9
evanmwillhite commentedHey, good idea for a module and seems to be a unique option. Couple of remarks here:
Thanks!
Comment #10
sch4lly commentedThank you for your feedback! Now you can delete already existing duplicates. Also, i updated the project page: https://drupal.org/sandbox/sch4lly/2135763
Comment #11
sch4lly commentedComment #12
dan.ashdown commentedHi sch4lly,
Firstly your Git link in the summary should be:
git clone --branch 7.x http://git.drupal.org/sandbox/sch4lly/2135763.git taxonomy_unique
Your branch should be called "7.x-1.x" rather than "7.x" as you're not providing the version of the module; only the core requirement. This means you'd need to update the git path above again ;)
In "taxonomy_unique_is_term_unique()"
Would be better as
Nice module though, will definitely use this. I agree with neerajskydiver on the taxonomy_unique_is_term_unique() being too verbose.
Comment #13
sch4lly commentedComment #14
sch4lly commentedThanks!
I'm now working in the 7.x-1.x branch and updated the issue description to show the correct git url.
Also i refactored taxonomy_unique_is_term_unique() to be less verbose.
Comment #15
dan.ashdown commentedYour git url is still wrong :)
Look at the one in my comment, you've got your username in yours.
Comment #16
sch4lly commentedComment #17
sch4lly commentedComment #18
sch4lly commentedComment #19
sch4lly commentedComment #20
sch4lly commentedNow it should be the correct url! :)
Comment #21
a_thakur commentedOne of the principles of the Drupal project is collaboration. Would you consider merging your project into that one and collaborating with the authors of Taxonomy Dupcheck.
Comment #22
sch4lly commentedI considered writing a patch for taxonomy_dupecheck instead of writing my own module, but as i wrote, i wanted the dupecheck only for certain vocabularies. This would have meant, the admin settings would have changed "drastically", from one form under admin/config/taxonomy_dupecheck where you can enable the functionality, to the small settings in each vocabulary settings page. For existing users of the module this would be confusing, also a upgrade path would be necessary.
So, in short, i considered merging, but decided to write my own module instead.
Comment #23
perennial.sky commentedHello sch4lly ,
Great work , I just want to tell that ,
There are some coding standard problem and you can also reducing some number lines of code
You should try like this
Comment #24
perennial.sky commentedComment #25
sch4lly commentedHello akashjain132,
thanks for your review! I fixed the codestyle issues and refactored my if clause to your suggestion.
Comment #26
sch4lly commentedComment #27
devd commentedHi sch4lly ,
occurences is misspelled in taxonomy unique.info. It should be occurrences.
Comment #28
sch4lly commentedThanks, fixed.
Comment #29
sch4lly commentedAlso, is is misspelled in your comment. It should be is.
Comment #30
devd commentedHi ch4lly,
I am unable to create a term with same name under parent term.
e.g. i want to create following category as followings:
Sahara
News
Z-tv
News
But i am unable to create same News category more than one time in different parent term.
Comment #31
devd commentedThanks sch4lly.
Comment #32
sch4lly commentedThis is working as intended, the term name must be unique, regardless of the parent term.
Comment #33
dan.ashdown commentedHi Sch4lly,
No automated testing issues found, but one manual review issues:
alert(1);
" displays the alert on error. You should wrap filter_xss() around the string when it's output. Don't trust anyone. Even the admin :)
Comment #34
sch4lly commentedGood catch, thanks! Fixed and commited.
Comment #35
mile23It'd be great to have tests.
Add a minimal taxonomy tree using the API or DrupalWebTestCase::drupalPost(), and then try to post the same value as an existing term. Check that your validation error text appeared with assertText().
Check out the SimpleTest example if you need some guidance: https://drupal.org/project/examples
Comment #36
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.
Comment #37
sch4lly commentedWon't provide tests for 100 lines of code (more like 70 minus the comments), sorry.
Comment #38
sch4lly commentedComment #39
gotosolr commentedThere is an error on line 76
Parse error: syntax error, unexpected ';'
Looks like its missing a bracket for form_set_error .
Comment #40
sch4lly commentedWell this is embarassing. It's fixed now, thanks for your comment!
Comment #41
cbuvaneswaran commentedGreat work , I reviewd this module and it is working fine. Please add check_plain() for variables you used. This validates strings as UTF-8 to prevent cross site scripting attacks on Internet Explorer 6.
Example:
$term->tid and etc.
Comment #42
sch4lly commentedThanks for your review. The only user-facing string already goes trough filter_xss(), so no need for check_plain() here. I would suggest you do some reading on Cross-Site-Scripting, as it is no IE6 Problem but affects every browser. It also has nothing to do with UTF-8, and wrapping every used variable in check_plain() doesn't help either. A good place to start is https://docs.acquia.com/articles/introduction-cross-site-scripting-xss-a...
Comment #43
klausiA term ID is not user provided text, so it does not need to be run through check_plain().
Comment #44
cbuvaneswaran commented@sch4lly This link really helps.
Thanks.
Comment #45
DaReMe commentedWorks as expected.
Comment #46
klausiReview of the 7.x-1.x branch (commit 3bb3f5f):
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.
manual review:
But otherwise looks RTBC to me. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Assigning to er.pushoinderrana as he might have time to take a final look at this.
Comment #47
klausi@sch4lly: The Git commits are not connected to your user account. You need to specify an email address. See https://www.drupal.org/node/1022156 and https://www.drupal.org/node/1051722
Ah, crosspost with @Daniel.Redwig, who also thinks this is RTBC. Which means we can approve this right away.
Thanks for your contribution, sch4lly!
I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!
Thanks, 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.
Thanks to the dedicated reviewer(s) as well.
Comment #48
sch4lly commentedThank you very much!
... also i just fixed the missing t()s and wrong docblock.