Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
2 Apr 2016 at 13:44 UTC
Updated:
29 Jun 2016 at 16:24 UTC
Jump to comment: Most recent
Comments
Comment #2
PA robot commentedProject 1: https://www.drupal.org/node/2699013
Project 2: https://www.drupal.org/node/2697809
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/httpgitdrupalorgsandboxVikkyShostak2698997git
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
koddr commentedOk. I fixed: http://pareview.sh/pareview/httpgitdrupalorgsandboxvikkyshostak2698997git
Comment #5
PA robot commentedClosing 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.
Comment #6
koddr commentedComment #7
asiby commentedYou can help your module gain more priority and get reviewed by manually reviewing at least three modules.
Comment #8
chi commentedHi. Thanks for the application. Here is my review.
Info file:
Why? Are there some other modules in this package? I would recommend leave this so it falls into default 'Other' group.
The file lacks configure link.
Module file:
The comment is not very helpful in this case.
What is this about? I guess you need more specific form alter hook like hook_form_FORM_ID_alter() or hook_form_BASE_ID_alter().
Doesn't it load all site users? This will cause high memory consumption if the site has a good number of registered accounts.
I don't know how telegram will handle this. Maybe you need to sanitize the title using check_plain().
I would use url() function with absolute option.
Usually CURL or drupal_http_request() are more preferable for making http requests. I also recommend you check telegram response here and log any errors to watchdog.
Why do you remove the destination?
You've set redirect destination twice before. Doesn't it work without this? Btw, why do you need the redirect at all?
Admin file
It's default weight. If you configure form elements sequentially you don't have to specify their weights.
Same as about settings page. The comment duplicates the element title.
The text is too long. It's usually recommended to split such texts into small translatable strings as follows:
Then you can implode it or output as a list using theme_item_list(). Also try to avoid using markup inside t().
Don't put urls into translatable strings but use placeholder instead like this:
t('If you looking for screencast, see <a href="!url">this blogpost</a>.', array('!url' => 'http://blizzy.ru/node/11');In this particular case I would move this to README.txt.These strings need to be translatable.
'' can be omitted.
Keep
<p/>outside t() as follows:The content type form element obviously needs validation handler.
Install file
There is a small chance that the field with a given name already exists. I would check it first.
All variables declared in module should be deleted in hook_uninstall().
Comment #9
chi commentedComment #10
PA robot commentedClosing 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.