Closed (duplicate)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
4 Jul 2013 at 07:02 UTC
Updated:
9 Sep 2018 at 23:23 UTC
Jump to comment: Most recent
Comments
Comment #1
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 #1.0
PA robot commentedAdd review of other project
Comment #1.1
pandaski commentedUpdate git repo
Comment #2
bogdanru commentedHi,
Better use an explicit list of your own variables in taxonomy_autotagging_uninstall(). That way you will not accidentally delete variables of submodules, if someone creates one.
I try it out your module, but it gives me this error PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'entity_id' cannot be null: .... in _taxonomy_autotagging_setting_form_submit() (line 161 of /Applications/MAMP/htdocs/drupal7/sites/all/modules/taxonomy_auto_tagging/taxonomy_autotagging.module).
Enabled auto-tagging with default settings. I need to do more?
Comment #3
pandaski commented@bogdanru Thank you for the review.
Regarding the uninstall variables, thanks for the reminder. I will update it right now
Regarding the error, I will need more work since while we create a new node, we don't have node id yet, so I will update the hook to until got node id, then update the field value.
Comment #4
PA robot commentedProject 1: https://drupal.org/node/2034575
Project 2: https://drupal.org/node/2035383
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 #4.0
PA robot commentedAdd review of project link.
Comment #4.1
pandaski commentedUpdate the projcet desc.
Comment #5
avpaderno