June 2006 - Development - lists.drupal.org

DrupalCON Europe
by Dries Buytaert 20 Jul '06

20 Jul '06

Hello, as you might have read, we started planning this year's DrupalCON Europe. We're currently looking for a venue, and would like to know what the 'ideal setup' looks like in terms of meeting rooms and presentation rooms. Please share you ideas at http:// groups.drupal.org/node/363#comment-1371. Your input is required to move forward. -- Dries Buytaert :: http://www.buytaert.net/

2 1

fixing nodeapi : programmatically submitting forms.
by Adrian Rossouw 14 Jul '06

14 Jul '06

Hey everyone. I don't have a lot of time for core development right now (I will likely only have time again in august, by the looks of things), but we have a problem in core at the moment. I am talking of course of the fact that FAPI only partially replaced node api, leaving neither of them the right solution for programmatically creating nodes and the like. The solution I have in mind for this , is the following : 1 ) introduce a hook_forms. which registers each of the forms on the site. 2 ) register all the forms, and their inputs and create callbacks for them 3 ) put the form creation code into it's own function, with the registered callback 4) alter fapi to not use _POST at all. Instead use a parameter that is passed to it, which merely defaults to _POST. Instead of PUSHING the form array through the form generation process, we now have the ability to PULL the form array and process it. So whenever you want to display a form, instead of having function mymodule_page_callback() { $form['title'] = array( /* generate your form array here */ ); return drupal_get_form('form_id', $form, 'alternate'); } You have : function mymodule_forms() { $form['mymodule/form_id'] = array( 'callback' => 'mymodule_form_id', 'access' => user_access('can do form_id'), 'title' => 'form title' ); } function mymodule_form_id($input) { $form['title'] = array( /* generate your form array here */ ); return $form; } function mymodule_page_callback() { // get your form input ready return drupal_get_form('mymodule/form_id', array('input' => 'object')); } -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com

6 12

Extend database abstraction layer, to include table creation.
by Adrian Rossouw 09 Jul '06

09 Jul '06

http://drupal.org/node/63049 Now that we have .install files for modules, I believe it is time we extended our database abstraction layer. I recommend we create the following extra functions : 1. db_create_table($tablename, $columns); // columns is an associative array with the 'name' => 'type' 3. db_drop_table($tablename); 3. db_create_index($tablename, $columns); // columns is an array of column names, or just a single column. 4. db_drop_index($tablename, $columns); 5. db_add_column($tablename, $column, $type); // PGSQL already has a similar function, but it isn't in both systems. 6. db_drop_column($tablename, $column); The installer that is coming in, will be converting the database.*sql files into a system.install file, and with these functions, we can collapse ALL THREE SCHEMA FILES, into a single, much simpler file. This will also _drastically_ simplify updates, and it will give us consistent usage of types across the database. Certain things will still need to happen only on postgres (like create function calls for instance), but this DRASTICALLY decreases the amount of work we have to do to support multiple db types. At the moment, there are no create table statements that can be changed in core itself (until we have a system.install) , however, contrib modules can already be ported to use these functions, which would mean that we have (preliminary) postgres support across the board on all contrib modules. These functions should possibly keep track of what tables / columns / indexes have already been created, that would allow us to check (in a cross db way) what tables are available, and maintaining this information could possibly be useful in the future, such as not creating tables which have already been created. Additionally, each of these functions can be used to trigger a process for entering additional database credentials, in the case that the specific database user is not allowed to create tables and the like. This also helps make the patch for the installer a lot simpler, so if you want to help out with the installer, this would be a good thing to get involved with =) -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com

31 110

Test automation
by Rok Žlender 08 Jul '06

08 Jul '06

Hello I am working on unit test automation for this year Summer of Code. After discussing possible solutions with some people on IRC I feel that this mailing list is the right place to get some response on the subject. Here is the general idea how unit test automation will look like in the end. Testing server - server which prepares the environment for tests and runs them Project server - server with project module installed and where all the issues and patches are gathered 1. Testing server queries project server for all untested patches. This will require a xml-rpc handler in project module which would generate a list of untested patches or patches marked "patch (needs automated test)" and return it as a response. 2. Testing server tests every patch on the list. Testing is done in a virtual server. 3. When a patch is tested testing server notifies project server with result. Again this would require another xml-rpc handler inside project module that would save the result into DB. Because there would be too much information to display as a follow up all the detailed information about a certain test should be saved on testing server. This is an example how testing result could be displayed in follow up: Automated test result for file: [file_name] PASS| FAIL. [link_to_detailed_information]. Testing server could also gather some statistics regarding the tests for example number of passes/fails etc. Please feel free to comment and give ideas. Cheers Rok Žlender

8 12

hook_block can set properties (weight, enabled, etc.) for blocks
by Nedjo Rogers 06 Jul '06

06 Jul '06

A quick FYI for module authors. As of 4.7, we can set all block properties except theme in hook_block (instead of, previously, just 'content' and 'subject'). This is a change that was part of the block region patch. So, for example, you can give your blocks an explicit weight, enable them, limit them to given pages, etc. Example: $block = array('weight' => -6, 'enabled' => 1, 'region' => 'content', 'subject' => t('Example')); $block['content'] = t('This is an example'); These settings will be registered when the block is first loaded at admin/block, and from there can be changed manually via block administration. Note that if you set a region that isn't available in a given theme, the block will be registered instead to that theme's default region (the first item in the _regions array).

3 4

Re: [Drupal bug] Access Control Rules Error - Bump up access.aid and boxes.bid
by sime 29 Jun '06

29 Jun '06

agentrickard wrote: > And sime, trust me, I spent an hour looking at this problem a few weeks > ago when we mysteriously couldn't add blocks anyomre. I trust you. I was just making a joke. ( A pretty good binary joke I might add, but I suppose they're nought for every one. )

1 0

Re: [Drupal bug] Access Control Rules Error
by Ken Rickard 29 Jun '06

29 Jun '06

Actually, it means that you've hit the practical limit of the access table. The column 'aid' is set to a tinyint(), unsigned, which has a maximum value of 128 unique records. The table records 0 - 127, then you start to get errors. I had the same problem with the 'boxes' table. http://drupal.org/node/66961 Administer your SQL tables and set 'aid' to be an INT. - Ken Rickard agentrickard alextrup wrote: > Issue status update for http://drupal.org/node/71389 > Post a follow up: http://drupal.org/project/comments/add/71389 > > Project: Drupal > Version: 4.7.2 > Component: base system > Category: bug reports > Priority: critical > Assigned to: Anonymous > Reported by: alextrup > Updated by: alextrup > Status: active > > I wasn't sure which component to put this under. > > > I have been creating many access control rules, to deny certain > usernames being used. I currently have 125 rules in the list (but I > have aids up to 127 in my database with 1 or 2 aids missing - which > were rules I deleted) > > > I now get the following error every time I try to add any additional > rules > > > user warning: Duplicate entry '127' for key 1 query: INSERT INTO access > (aid, mask, type, status) VALUES ('133', 'examplerule', 'user', 0) in > /home/.jaunt/diversity/woo.sh/includes/database.mysql.inc on line 120. > Is there a known limit on the number of rules that can be applied? > > > Thanks, > > > Alex > > > > > alextrup > > > >

2 1

Re: [Drupal bug] Access Control Rules Error
by sime 29 Jun '06

29 Jun '06

Sounds like... the access table key has been incremented ahead of the value in the sequences table. I don't know all the ways this can happen, so I won't hypothesize. If you look at the structure of access table in phpmyadmin, the current autoincrement is shown next to "Next Autoindex". So make the value in sequences (WHERE name='access_aid') higher than that. HTH .s alextrup wrote: > Issue status update for http://drupal.org/node/71389 > Post a follow up: http://drupal.org/project/comments/add/71389 > > Project: Drupal > Version: 4.7.2 > Component: base system > Category: bug reports > Priority: critical > Assigned to: Anonymous > Reported by: alextrup > Updated by: alextrup > Status: active > > I wasn't sure which component to put this under. > > > I have been creating many access control rules, to deny certain > usernames being used. I currently have 125 rules in the list (but I > have aids up to 127 in my database with 1 or 2 aids missing - which > were rules I deleted) > > > I now get the following error every time I try to add any additional > rules > > > user warning: Duplicate entry '127' for key 1 query: INSERT INTO access > (aid, mask, type, status) VALUES ('133', 'examplerule', 'user', 0) in > /home/.jaunt/diversity/woo.sh/includes/database.mysql.inc on line 120. > Is there a known limit on the number of rules that can be applied? > > > Thanks, > > > Alex > > > > > alextrup > > > >

1 0

How to move taxonomy fields from the categories fieldset?
by Angela Byron 29 Jun '06

29 Jun '06

I found an old thread where this was asked about but it didn't seem to have a resolution: http://lists.drupal.org/archives/development/ 2006-03/msg00511.html Basically, I'd like the ability to take the stuff in the "categories" fieldset (specifically, free-tagging vocabs, but any and all is good), assign it some arbitrarily weight, and place it elsewhere in the form. Anyone have any pearls of wisdom? I hereby volunteer to write up a nice little tutorial about it for the handbook if someone can throw me some sample code. Thanks a lot, -Angie

5 5

Wanting to tag my newly commited module.
by Dirk Botha 28 Jun '06

28 Jun '06

Greetings all, I have just committed my first module, and have arrived at the point where I need to tag it. After 4 hours of searching and reading of forums, cvs man pages, etc. I have come to the conclusion that there is something I do not understand. Simply stated, I have attempted every logical combinations of options for both "cvs tag" and "cvs rtag". My attempts have all failed with: --- start of error --- Invalid tag for /contributions/modules/easylinks. cvs rtag: Pre-tag check failed cvs [rtag aborted]: correct the above errors first! --- end of error --- I have also attempted to use a GUI (Cervisia) in order to achieve this. The result was exactly the same. Is there perhaps something I need to do between committing my module and tagging it, that I am missing? Regards, Athelas

3 3