Closed (fixed)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
18 Oct 2010 at 08:10 UTC
Updated:
9 Mar 2019 at 18:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
manuelBS commentedPlease review this module to get a project on drupal.org. It checks nodes for unique content using phonem to match equal strings that only sounds equal but do not match the exact string (like "drupal" and "trupal" does).
Comment #2
avpadernoHello, and thank you for applying for a CVS account. I am adding the review tags, and some volunteers will review the code, pointing out what it needs to be changed.
As per requirements, the motivation message should be expanded to contain more features of the proposed project. For themes, it should include also a screenshot of the theme, and (when possible) a link to a working demo site; for modules, it should include also a comparison with the existing solutions.
Comment #3
manuelBS commentedok thanks for your first feedback. Where can I edit my motivation for the modul? Simply post it as another comment?
Comment #4
FernandoTapiaRico commentedYes, to extend the motivation message just post a new comment.
Comment #5
manuelBS commentedHere is my new Motivation:
The module bs_uniquenode provides an option for each content type and each CCK Field to make sure content is unique regarding one ore more content fields, including title and cck fields. The most important thing is that strings are not only matched exactly (using the operator ==) but using phonem string comparisons (based on sound string-matching) For example "drupal" and "trupal" will match using phonem. This method can be used on any"text"-field.
The setting "Enable override" on each node type lets you decide if content of a node must be unique or if the user can decide if equal nodes can be inserted anyway.
Phonetic comparison needs a special comparison-index. It is created automatically during cron runs. The index is stored in a separate table in the drupal database.
Comment #6
avpadernoThank you for your reply.
Comment #7
avpadernoI am adding the review tags.
Comment #8
drupalshrek commentedHi,
Sounds like a very interesting module. I've taken a first look. Here's the things I've noticed:
The good:
1) Great idea!
2) You clearly know what you're doing
3) t() is used for translation
4) query parameters appear properly escaped
5) query tables appear properly in {}
The work:
1) All modules should ideally have a README.txt (explaining what it does, how to install [usual stuff, but assume yours is the first module the person has ever installed and you won't go far wrong], how to administer it, how to use it etc.). See http://drupal.org/node/161085. In the end, you're submitting it because you want others to use it, so the better documented, the more that is likely to happen. Remember of course that 90% of admins may not be able to read the code at all, but might still want to be able to use it.
2) Install the Coder module and fix the warnings from that (mostly spaces instead of tabs):
Coder found 1 projects, 2 files, 1019 normal warnings
See also:
http://drupal.org/coding-standards
http://drupal.org/node/161085
http://drupal.org/node/1354
3) I think the correct form of the hook comments is with 3rd person singular verb and the function brackets, e.g.:
* Implements hook_cron()
4) The module does not appear to be themeable (I'm not an expert in this domain so I may be wrong). Basically, whenever you generate HTML you are likely to need to wrap the code in themeable way so that themer gurus can do their magic, just like wrapping text in t() allows translators to do their multilingual magic.
For example, code like the following needs to be themeable:
Pages on the subject of making code themeable:
http://drupal.org/node/165706
http://api.drupal.org/api/drupal/includes--theme.inc/group/themeable/6
Comment #9
drupalshrek commentedComment #10
manuelBS commentedhi, I have done my work:
- coder module doesn't show any warning
- README.txt added
- made the frontend functions of the module themable
- changed the comments on hook implementations.
I hope this works, if not, let me know i will do my workk again ;-)
Comment #11
manuelBS commentedI dont know if this will work within this issue but here is another module id like to contriubute. I have checked for warnings by coder module and all the other things i did wrong on my first application. If this is too much for one issue, i will create another one for sure.
--- About This Module --- (more information in readme .tx file)
This module redirects the page /node to a custom page. Even in many big Drupal projects the page /node is often ignored by content and theming. In most cases the front page of drupal in "website settings" is changed from the default /node to a custom page. But the problem is : The page /node will exists and may display many nodes (in many cases even test nodes!!). You could set all nodes to not "display on frontpage" or simply active this tiny module. But the you will see the default page "Welcome to your new drupal website"
If a visitor of your page visits the page /node, he will either be redirected to your real frontpage entered in "website settings" or you can enter a custom destination for the redirect.
Comment #12
avpadernoI am approving the application for the first module.
Welcome on board!
Comment #13
manuelBS commentedThanks! Feels good to be on board!
Comment #14
avpadernoComment #17
avpaderno