November 2008 - Development - lists.drupal.org

Database creation on Install
by Amy Stephen 09 Jan '09

09 Jan '09

I apologize if this is not the appropriate place to ask this question but I am curious after checking out your fine development work. Why doesn't the Drupal Installation process try to create the database if it doesn't exist already? WordPress is the same. Joomla! will use the database if it exists - and create it, provided the ID has sufficient permissions. It's just another "make things easier" step (for both the "newbie" crowd, but also developers testing/working). I was curious if there were security concerns? Or, if it just never seemed to be someone's itch? Again, if I am out of place with this question, please let me know, and forgive my ignorance. Kind regards, Amy :)

10 15

New maintainer sought for Comment Upload, Elements, Flatcomments, Taxonomy Defaults and User Badges
by Heine Deelstra 25 Nov '08

25 Nov '08

I seek a new maintainer for the following modules: http://drupal.org/project/comment_upload http://drupal.org/project/elements http://drupal.org/project/flatcomments http://drupal.org/project/taxonomy_defaults http://drupal.org/project/user_badges (others aren't worth continuing imo). If you are interested, please reply on the issue queue for the relevant project and I'll assign the projects. Kind regards, Heine Deelstra

1 0

Drupal 7 could be awesome if...
by Karoly Negyesi 24 Nov '08

24 Nov '08

someone would take Plugin Manager, port to D7 (easy), clean up to code standards (not hard at all and you will get a lot of help). http://drupal.org/node/336743 the project has two active and hepful maintainers but as said, I myself and a number of people on #drupal would be glad to help. Any takers? Thanks NK

4 6

how to redirect user after login
by Aldo Martinez Selleras 21 Nov '08

21 Nov '08

how may i redirect the user to frontpage, exactly after user login, not when the user recieve a 403 error, when the user log in, always send him to frontpage! how can i do this! some module? any modification to user module ? -- ---------------------- Aldo Martinez Selleras Administrador del Nodo CITMATEL GND Camaguey Tel: 32-291661 E-mail: aldo(a)caonao.cu Linux User #364356

5 4

Make Scheduler more generic
by Eric-Alexander Schaefer 19 Nov '08

19 Nov '08

Hi list, we (a couple of scheduler.module users and I) have been thinking about making scheduler more generic because every other week somebody suggest another thing that needs to be scheduled. The plan is to make scheduler a provider for scheduled triggers. It would hook into the node form and let the user select a date and time and the action that is to be performed at that time (e.g. trigger "Make post sticky"-action at $date). I am about to begin coding, but I thought I should share the ideas with this list to get some more input before I start. Here are the ideas so far: http://drupal.org/node/276376 Thanks, Eric

2 1

Policy for setting issues to 'fixed'
by Eric-Alexander Schaefer 19 Nov '08

19 Nov '08

Hi List, for contributed modules, what is the prefered policy for setting issues to 'fixed' that have reviewed (!) patches attached: 1. when patch has been committed (providing the commit id) 2. when patch has been committed and is part of new release (providing release number) I have observed both ways, I believe. Thanks, Eric

5 5

disable the title link
by Aldo Martinez Selleras 19 Nov '08

19 Nov '08

may i disable the title link in one node where i will execute a php code ??? -- ---------------------- Aldo Martinez Selleras Administrador del Nodo CITMATEL GND Camaguey Tel: 32-291661 E-mail: aldo(a)caonao.cu Linux User #364356

2 1

Re-check "code needs work" patches
by Angela Byron 17 Nov '08

17 Nov '08

HEAD was broken today for about 4 hours after the commit of http://drupal.org/node/74645#comment-1110500. Because this patch was missing a hunk from install.inc, testing bot correctly flagged it as "code needs work" with a reason of "Failed to install HEAD." Unfortunately, because the patch then got committed to HEAD, that meant that *every* patch the testing bot tried thereafter failed for the same reason. So over 180 patches got marked "code needs work" as their turns came up in the testing queue. :\ The *good* news is that boombatower has some code ready that will test vanilla HEAD after each commit and immediately stop processing more testing results until this situation remedies itself, should it happen again (and it probably will). It will also ping the dev list and the core maitainers via email so that they can fix it ASAP. The *bad* news is that we don't have a real easy way to undo these CNWs so this will have to be a manual process. :\ http://pastebin.ca/1258476 has a list of all of the affected issues. If your patch is on the list, please set it back to CNR and click the "Submit for re-testing" link on the erroneous failure to get it re-tested. A good rule of thumb in the future is never set a patch RTBC until it's been pinged back from the testing bot, which will ensure: a) The patch applies b) The patch doesn't cause Drupal to fail to install c) The patch doesn't have a PHP syntax error d) All of the automated tests pass -Angie

1 0

Views 2 API hook_views_data and node relationships
by Domas Monkus 15 Nov '08

15 Nov '08

Hi, my module creates and maintains a table that basically links pairs of nodes together (it has two columns, both representing nids). I want to use views to show all nodes related through this table to the node that is currently being viewed. What should the hook_views_data look like? I read through the documentation, but didn't manage to figure this out. Thanks in advance, Domas

1 0

Add consistency to node hooks
by Henrique Recidive 14 Nov '08

14 Nov '08

Hello, a while ago I've submitted a patch to bring more consistency to node hooks, so they are inline with other drupal data hooks such as hook_user_*(), hook_file_*(). Node hooks are special, i.e. there are two kinds of node hooks: 1) hooks for modules which implement node types: hook_load(), hook_save(), etc and 2) hooks for all modules (those which implement node types and those which don't): hook_nodeapi_load(), hook_nodeapi_save(). In my opinion type #1 hooks have meaningless names, since they don't explicit say they are for extending node functionality. And type #2 hooks are very similar to hook_user_*(), hook_file_*() ones, so why they have 'nodeapi' in their names, not just 'node'? Basically what the patch does is changing type #1 hooks so they can be implemented in the following two ways: Node type specific: E.g. poll_node_form_poll() Node type agnostic: E.g. poll_node_form() This way modules which implement node types can have either a) one hook implementation for *each* node type they implement (the first case above), or one single hook for *all* node types they implement. The patch also rename type #2 hooks changing 'nodeapi' to 'node', to make them inline with other APIs. So e.g. hook_nodeapi_load() becomes hook_node_load(). What do you guys/gals think? Please comment on the issue: http://drupal.org/node/322485 Thanks, Henrique

1 0