Description
The module adds the ability to modify the list of countries(native drupal list of countries). For example, on page "admin/config/regional/settings". The setting is on the page "admin/config/setup_countrygetlist".
The module adds type field "Country list" and ability to modify the list of countries(native drupal list of countries) for each instance.
Usage
- Disables countries or adds new countries in the list of countries(native drupal list of countries) with help blacklist and whitelist.
- Use field (Country list) to any Drupal fieldable entity
- Modify the list of countries(native drupal list of countries) for each instance of field (Country list).
Features
- Does not require additional modules
- Adds field (Country list) to any Drupal fieldable entity
- Сan add the country (and even fantastic country) and disable unnecessary country as for the drupal system and for instance of field "Country list".
Similar Projects
Countries (https://www.drupal.org/project/countries)
The difference from mentioned above module:
- Module "Setup countries" is independent from other contributory modules.
- Module "Setup countries" simpler than module "Countries"
Project Sandbox link
https://www.drupal.org/sandbox/acaster/2302869
Git clone link
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/acaster/2302869.git
Pareview.sh passed
http://pareview.sh/pareview/httpgitdrupalorgsandboxacaster2302869git
Reviews of other projects (Review bonus program)
Role expose: https://www.drupal.org/node/2294899#comment-9056087
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | warning.png | 3.03 KB | pushpinderchauhan |
| #8 | xss_alert.png | 44.18 KB | pushpinderchauhan |
| #8 | article_node_choose_country_list_field.png | 6.8 KB | pushpinderchauhan |
| #8 | article_content_type_country_list_field.png | 2.37 KB | pushpinderchauhan |
Comments
Comment #1
acaster commentedComment #2
acaster commentedComment #3
acaster commentedComment #4
acaster commentedComment #5
acaster commentedComment #6
acaster commentedComment #7
PA robot commentedWe 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 #8
pushpinderchauhan commented@acaster, thank you for your work and contribution.
Automated Review
Best practice issues identified by pareview.sh / drupalcs / coder. None.
Manual Review
<script>alert("XSS");</script>|<script>alert("XSS");</script>under Whitelist of the country.This is vulnerable to XSS exploits. Every time If I choose this, will get a nasty javascript popup. You need to sanitize this before rendering, make sure to read https://www.drupal.org/node/28984 again.
admin/config/setup_countrygetlistform and country list form comes with content type field are different. If both are same then they are not sync yet and if both are separate then what is the use of Country blacklist form. As regarding this no where is mention so it confused me as I checkedZimbabwefrom Country blacklist form but is unchecked on content type field form. Also I am getting following warning every time, need to fix.configure = admin/config/setup_countrygetlistin your .info file to make it directly accessible from module page.admin/config/setup_countrygetlistpage instead of using defaultadminister site configuration. Also you should keep this form in separateadmin.incfile.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.
Please don't remove the security tag, we keep that for statistics and to show examples of security problems.
As I am not a git administrator, so I would recommend you, please help to review other project applications to get a review bonus. This will put you on the high priority list, then git administrators will take a look at your project right away :-)
Thanks Again!
Comment #9
acaster commentedComment #10
acaster commentedComment #11
acaster commentedComment #12
acaster commentedComment #13
acaster commentedComment #14
acaster commentedComment #15
PA robot commentedProject 1: https://www.drupal.org/node/2336221
Project 2: https://www.drupal.org/node/2320107
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #16
avpaderno