Closed (fixed)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
15 Sep 2009 at 13:21 UTC
Updated:
7 Oct 2019 at 07:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
JFN commentedComment #2
avpadernoComment #3
avpadernoComment #4
JFN commentedOK, thanks for the feedback:
1. LICENSE.txt removed
2. 3rd party files no longer included, instructions provided in README.txt, standard display format is in a table
Comment #5
JFN commentedSorry, update the status to "needs review", see my previous post.
Comment #6
avpadernoIt should be better to avoid to escape the quote character on strings that needs to be translated; the script to extract those strings would probably extract the escape character too
The code doesn't seem correct.
trim()is removing any , , , , and ; thenexplode()should create an array item each time it finds an occurrence of , which cannot be found as those characters have been removed. See the examples in http://it2.php.net/manual/en/function.trim.php, where it is clear that the last parameter oftrim()is a list of characters to be removed.Comment #7
JFN commented1. Corrected by using single quotes and no escape character, the escape character solution was actually from Dries his Mollom module ;)
2. With RFI attempts there are 2x http strings in the URL, we are only interested in the 'middle' http string, the leading http string is from the website hosting Drupal. When we explode with the middle http string the first array key contains the Drupal domain, the second array key contains the domain of the RFI script. This is the reason why it is required to trim the leading http string.
Comment #8
avpadernoThe coding standards say that a space should be added before and after a
=, or after a comma in the parameter list of a function.Rather than concatenating translatable strings, the code should use placeholders. In this way, people who create the translation for the module have a context that allow them to better translate the string (as a translation can be context-dependend).
The code should use Drupal functions, when available. In this case the function to call should be
drupal_set_header().Comment #9
JFN commentedThanks a lot for your help!
The module is now available for download.
Comment #10
avpadernoThere is no need to close a fixed issue. They are automatically closed after 14 days.
Comment #13
avpaderno