Webform Advanced Report gives you a better way to generate report from webform submissions.
You can include user data from user profile, and not just the user name like the original webform report feature, included custom user fields generated with Fields module.
Possibility to select multiple webform, coming from different content types, for one single report. As any webform should have a different structure, the module will format the data shifting the empty cells to let data appear under the right column.
Select an entity field, for every content checked for report generation, to act as filter in report page. This is a useful option if your webforms content types have an entity field where they are grouped by, so you can easily choose from which nodes you want to generate report for, just selecting the parent node.
It's also possible to partialize webform and user fields to exclude unwanted fields from the report, filter your results by a specific date range, and, obviously, export the result data in CSV, XML or HTML.
Link to sandbox project: http://drupal.org/sandbox/hiryu/1985184
Comments
Comment #1
PA robot commentedProject 1: http://drupal.org/node/1978434
Project 2: http://drupal.org/node/1985214
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 #2
hiryu commentedThis is not a duplicate of my other module "User Auto Tag". This is a complete different module.
Can I have two open projects at the same time?
Comment #3
PA robot commentedProject 1: http://drupal.org/node/1978434
Project 2: http://drupal.org/node/1985214
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
klausi@hiryu: no, please open only one project application. Once the first application has been successfully approved, then the applicant can promote other projects without review.
Comment #5
hiryu commentedMy other project is now published so I can reopen this one now.
Comment #6
PA robot commentedProject 1: https://drupal.org/node/1985214
Project 2: https://drupal.org/node/1978434
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 #7
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://ventral.org/pareview/httpgitdrupalorgsandboxhiryu1985184git
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 #8
paul rowell commentedHey hiryu,
Now you've had your first project approved (the Auto Tag one) you don't need to have future projects reviewed, you can promote this project without others having to approve it first.
Hope that clears it up :)
Comment #9
hiryu commentedOh thanks for the tip Paul, I didn't know!
Anyway I think is better, if someone have time to take a look, to have some advise on how to improve the module and, obviously, a bit of bug fixing, before to put this module downloadable for everybody.
I take this opportunity to ask about the error message reported by the robot.
The errors regard code formatting in an external class I've used in my module, I have to format manually the code according to drupal coding standard? It's a nightmare!!
Comment #10
hiryu commentedComment #11
willieseabrook commentedStarting review...
Comment #12
willieseabrook commentedHi @hiryu
http://pareview.sh/pareview/httpgitdrupalorgsandboxhiryu1985184git
1. Project Page and Documentation
https://drupal.org/sandbox/hiryu/1985184
Improve the project page to clearly show installation and setup steps, perhaps some clearer headers. So a user who doesn't know what it is or why it's valuable can easily follow some step by step instructions and see what it does.
2. PAReview: 3rd party code
class DOMi appears to be 3rd party code. 3rd party code is not generally allowed on Drupal.org and should be deleted. This policy is described in the getting involved handbook. It also appears in the terms and conditions you agreed to when you signed up for Git access, which you may want to re-read, to be sure you're not violating other terms.
The Libraries API module is a recommended method for adding 3rd party dependencies without directly including the code on Drupal.org.
See below for an example of how to work with a third party library from devel.module
3. Constants
I don't see why WEBFORM_ADVANCED_REPORT_MODULE_TITLE and WEBFORM_ADVANCED_REPORT_PATH_NAME are necessary. Nor is this an approach generally used by other modules. Just use the text itself.
3. Database API & Security
This is a security risk and not the standard way to use the db api. See https://drupal.org/writing-secure-code and https://drupal.org/node/310069
You need to fix this in all places you make database queries.
There are lots of other things, but fix those 3 things and try again, you will have made a big step forward and someone can do the next review for you to get it release quality.
Comment #13
kscheirerProject: https://drupal.org/node/1978434
Once their first application has been successfully approved, then an applicant can promote other projects without review. Because of this, posting multiple applications are not necessary, and results in additional workload for reviewers!
Instead, you can post to the Peer Review group for feedback, here:
https://groups.drupal.org/peer-review/about
With this in mind, I have marked your application as 'closed(duplicate)'. If this is incorrect, and you do not yet have the ability to create full projects, then please feel free to re-open this application.
----
Top Shelf Modules - Crafted, Curated, Contributed.
Comment #13.0
kscheirerupdated description
Comment #14
avpaderno