Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
10 Mar 2012 at 22:55 UTC
Updated:
14 Dec 2012 at 19:16 UTC
Jump to comment: Most recent file
Comments
Comment #1
donpwinston commentedComment #2
donpwinston commentedComment #3
patrickd commentedwelcome,
we got about 150 applications in the queue, all of them want a review, you don't have to put it into the title ;-)
You are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Please take a moment to make your project page follow tips for a great project page.
Please remove the LICENSE.txt file. Drupal will add the appropriate version automatically during packaging so your repository should not include it.
while waiting for an in-depht review of your module you can start out fixing some coding style issues detected by automated tools:
http://ventral.org/pareview/httpgitdrupalorgsandboxdonpwinston1476774git
You can also get a review bonus and we will come back to your application sooner.
regards
Comment #4
patrickd commentedoh, yes and only reviewers should assign themselfs (so 2 reviewers won't do the same work twice).
Comment #5
donpwinston commentedok.
thanks
Comment #6
donpwinston commentedDone.
Comment #7
donpwinston commentedFirst time, so might have missed a few things..
Comment #8
donpwinston commentedI'm not saving the filter settings properly although it sort of works as is.
Comment #9
donpwinston commentedI think I've found some Drupal documentation that will help me code the filter settings properly. I'll resubmit it for review later.
Comment #10
donpwinston commentedFigured out how to code the admin settings for a filter properly. It's a little different then the ordinary admin settings. Unlike the Drupal 6 version you do not use the variable_set/get functions! Also, had to make significant changes from the Drupal 6 version to implement xml validation. I think it's ok now. (I will test it some more over the next couple of days)
I could not find any other modules that do this. I think this could be very useful if you had a lot of xml content to load into Drupal. You just load it and create a stylesheet for each kind of xml data. Or you could have different formats for the same kind of data for whatever reason (like a summary or selections of specific item(s)).
Comment #11
weebpal commentedReview of the 7.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Get a review bonus and we will come back to your application sooner.
Comment #12
donpwinston commentedprefixed all function names with the module name.
The so called code "style" issues are silly and defeat the purpose of using PHP. I'm not doing most of these. (It looks like many of the "ERRORS" in the automated error checker are not correct for whatever reason. For example it complains about tabs and whitespace after an end of line character).
Comment #13
klausiYou need to set the status to needs review if you want to get a review, see http://drupal.org/node/532400
You have not listed any reviews of other project applications in your issue summary as strongly recommended here: http://drupal.org/node/1011698
Comment #14
patrickd commentedComment #15
donpwinston commented"You have not listed any reviews of other project applications in your issue summary as strongly recommended here:"
Don't know what this means. Why I should I "list reviews of other project applications"? I don't believe I have any to list.
This is "finished".
Comment #16
patrickd commentedWe have a huge lack of reviewers, this sentence only says that we recommend reviewing other application so yours get higher priority.
Are you closing because your giving up on this ? :(
I'm very sorry for delay, hope you come another time
Comment #17
donpwinston commentedNo, I'm not complaining about a delay. I just didn't understand what they're talking about. I think this is more or less "done".
Comment #18
donatasp commenteddonpwinston, your project looks good, but if you want an in-depth review and approval, you'll have to fix indentation, comments, and other syntax issues described in http://ventral.org/pareview/httpgitdrupalorgsandboxdonpwinston1476774git . Drupal has codings standards and contributed modules are expected to follow them if they are to be hosted on drupal.org.
You should also expand your README file (see https://drupal.org/node/447604 ), follow tips ( https://drupal.org/node/997024 ) to make your sandbox project page better.
Comment #19
patrickd commentedNote that many of the issues found are minor and should not be required for approval, therefore please do not insist on having them fixed and do not switch the issue to needs work if there are no major issues found.
Comment #20
donpwinston commentedok, maybe when I get some time I'll polish this up. I'm not big on "indentation" and other code presentation things.
Comment #21
misc commentedDoing a manual review, and assigning this to myself, will get back soon.
Comment #22
misc commentedManual review:
$format = $node->body['und'][0]['format'], why?And one important issue here, how are you handling the security? There are some big security risks here. You are not adding any permissions, and you do not filter the xml file, or am I missing something?
Comment #23
misc commentedForgot to change status.
Comment #24
misc commentedAnd unassigning myself...
Comment #25
donpwinston commentedShould I use some function to get the appropriate language?
field_language()?
It's just validating the xml/xsl. The actual content does not matter.
Comment #26
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.