Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
26 Aug 2015 at 16:07 UTC
Updated:
19 Dec 2015 at 06:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
PA robot commentedProject 1: https://www.drupal.org/node/2558035
Project 2: https://www.drupal.org/node/2535442
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 #3
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxkporras072558027git
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
kporras07 commentedFixed errors reported by pareview.sh
js/select-widget-min.js is a library file; so it's minified and I don't have control over that file.
In sortable_lists.module there is a warning about input instead of values; I added a comment there about the reason of this.
Comment #5
kporras07 commentedRemoved library file. This now should be added in sites/all/libraries. Added hook_requirements for explaining this in status page.
Fixed some other coding standards issues.
Comment #6
prashant.cHi Kevin,
Follow the following template for your README.txt file.
Comment #7
prashant.cAlso coder showing the following warnings
function updateValue() {
function getId(text) {
function getItems(container) {
Comment #8
kporras07 commentedThanks @Prashant.c
About #6: I really tried to follow it; do you have any exact point where I failed?
About #7: Those files are JS; JS standard is camelCase.
Thanks,
Comment #9
prashant.cFor example,
In your README file you have described each heading as
*Introduction
If you need a form api element that provides any number of sortable lists and
you can move elements from one to another and order them; you could use the
element type that this module provides.
Here the format is wrong.
but it should be like following :
INTRODUCTION
--------------------
The Administration Menu module displays the entire administrative menu tree
(and most local tasks) in a drop-down menu, providing administrators one- or
two-click access to most pages. Other modules may also add menu links to the
menu using hook_admin_menu_output_alter().
You will have to take care of the line spacing and formatting.
Follow README TEMPLATE.
Comment #10
kporras07 commented@Prashant.c I had totally missed that.
Really thanks. I already fixed formatting, spacing and other stuff on README.md file.
Thanks,
Comment #11
pratik.mehta19 commentedHi kporras07,
I have found $form['input'] at line 171 in sortable_lists.module. Use $form['values'] instead.
Thanks.
Comment #12
kporras07 commentedHi @pratik.mehta19; yes; but it really should be there. As I explained in comment at line 169; I can't take that from values because I alter the value from javascript. However, I'm avoiding xss and other possible security risks in code.
Thanks,
Comment #13
rigoucrI think you have to add instructions in the README.md, Project page and hook_requirements() to indicate to the users how to name the external library, maybe something like that: Please add this name to your library folder : jquery-drop-down-widget.
Comment #14
klausiThe library naming sounds like a good improvement, but is surely not an application blocker. Anything else that you found or should this be RTBC instead?
Comment #15
rigoucrthanks for the correction @klausi, and only one more thing, when I test the form element the first time I only see the columns but I can't drag the column items:

After that I reviewed the navigator console and see this error:

I suppose is something with the drupal jquery. @kporras07 your module needs a specific jquery version?
Comment #16
kporras07 commented@rigoucr, @klausi really thanks for your feedback.
I had been in a project, so I hadn't had time for working on this. I just updated the code so that I removed the dependency on the external library and fixed the js error that @rigoucr reported.
It would be great if you could take a look to this module again.
Thanks in advance,
Comment #17
rigoucrHi @kporras07 thanks for the correction, now works perfectly, nice job!!!!
Comment #18
rigoucrSetting RTBC
Comment #19
kporras07 commentedAdded Manual Reviews and PAReview bonus tag.
Comment #20
kporras07 commentedHi there,
This is RTBC since 16/10; do I need to do something else for promoting it to full project?
Comment #21
cweagansThanks for your contribution!
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 #22
cweagansComment #23
kporras07 commented@cweagans thanks :D