Closed (fixed)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
30 Jul 2009 at 16:48 UTC
Updated:
4 Oct 2019 at 08:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dave reidPlease attach the module's code as a follow-up here.
Comment #2
yazna commentedInfowordpress module depends of infoutilities
Comment #3
avpadernoA module normally uses
hook_menu()to define menu callbacks that are present in its code; this module uses as callback functions that are defined in another module. It would be better to move on Infoutilities the menu callbacks that are relative to that module.Comment #4
yazna commentedComment #5
yazna commentedComment #6
avpaderno@yazna: The status can be changed to fixed only by AjK, which will approve your application.
Comment #7
avpadernoIf the name of the theme function is the one that Drupal would use, it's perfectly useless to define it. Each function a module define should respect its namespace (if the module is nodewords.module, then its functions must have a name starting with "nodewords_".
Comments should be in English.
trim()is called twice for the same string.It would be better to change it to use normal variables, and change the code to something similar to
"mostrar" is another not English word.
The code works only in the case URLs are allowed in calls to
fopen(); this is not always the case, and some web server providers don't allow that. The code must function without to take assumptions on the PHP configuration, if not the ones that Drupal already does.It would be better if the settings of the module are saved using
variable_set(), and obtained withvariable_get(). Using those functions would remove the need of an extra SQL query; Drupal variables are also cached, and that makes the system faster.The code must place spaces around the operators; the code should be rewritten as
Variables should be named using English words. The code you are developing must be understandable also from other people.
Submit functions should not depend on values like
$form_state['clicked_button']['#value']; it's possible to assign a submit function to each button present in a form, and that should be the way to assign submit functions, when the submit buttons are more than one.It's not necessary to set
$form_state['rebuild'], when$form_state['storage']is set.Rather than using
infowordpress_admin_delete(), it would be better to just defineinfowordpress_confirm_delete_form()as menu callback (or as argument for the menu callback); different menus can use the same callback function.Comment #8
yazna commentedComment #9
avpadernoSome of the things I reported before are still valid (especially for infoutilities.module).
I would also check the encoding for infoutilities.module because some characters are only visible setting the encoding to UTF-8; doing that, then, it's not possible to see the accented vowels you use in another part of the code.
I will check what encoding is suggested to use for the files uploaded on CVS, and I will report here.
Comment #10
avpadernoOne of the modules uses global variables, but they are not named following those rules.
An alternative of using global variables is using static variables inside a function that is called to set, or get the value of those variables.
Comment #11
yazna commentedComment #12
yazna commentedPrevious infoutilities module has errors, rewiev this attached here
Comment #13
yazna commentedI made some changes at infowordpress module
Comment #14
avpadernoComment #15
avpadernoComment #18
avpaderno