- Development - lists.drupal.org

bzr mirror
by Karoly Negyesi 08 Jul '06

08 Jul '06

Hi, Thanks to Matt Rae from OSUOSL, we now have a bzr mirror at http://bzr.drupal.org/ As this contains a ton of revisions, a bzr get would last for very long (approx ten minutes). So use this tarball (packaged nightly): http://ftp.osuosl.org/pub/drupal/files/bzr/drupal-bzr.tar.gz Untar the tarball and then either in that directory or a copy of that (bzr get locally is just a directory copy): bzr pull --remember http://bzr.drupal.org Onwards a simple bzr pull will get you the latest. No need to redownload the tarball again. Regards NK

7 8

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

Absence /4.7.3
by Gerhard Killesreiter 08 Jul '06

08 Jul '06

Hi there, I will be away till Tuesday. After I return I'd like to release Drupal 4.7.3. I'd appreciate if all of you could look at the bug tracker and try to come up with patches and review existing patches. Cheers, Gerhard

1 0

Extending Modules
by Benjamin Maurice 08 Jul '06

08 Jul '06

I very much expected to find "best practices" for extending modules, but I haven't. Does anyone have any pointers to resources or advice? It's great that Drupal itself is modular, but if I want to add a little something to a module that already does 90% of what I want, it seems there ought to be a standard way to do this without forking it. Wrapping a module I can imagine how to do, and overriding or adding functions as needed, but it seems there could be a way to do this without having to define every function and pass it through. At least I hope to find recommendations on how to do this. Thanks for any help, Ben Melançon of Agaric Design http://agaricdesign.com/

5 4

Integrating Drupal with PHPSurveyor
by Leo Burd 07 Jul '06

07 Jul '06

Hello there, I wonder if anyone has already implemented a module to integrate Drupal with PHPSurveyor, the open-source survey creation tool (http://www.phpsurveyor.org/) In my opinion, it would be great to have a module that presented Drupal users with a link to specified PHPSurveyor surveys, generated periodic reminders for users that haven't responded a given survey, etc. Ideally, I believe survey.module should incorporate the functionality offered by PHPSurveyor. Until then, this module should provide a good alternative solution. Anyone interested? Best, Leo

3 2

re: imagefield / imagecache
by Darrel O'Pry 07 Jul '06

07 Jul '06

'imagefield'[1] is its own project. If you've been experimenting with cck and imagefield, please post issues to the 'imagefield' project. I'm going to keep it on its own until JonBob comes back and includes it in the mainline cck. imagefield requires the cvs HEAD version of cck. 'imagecache'[2] is a dynamic image resizer and caching tool. I use it with imagefield for thumbnail generation so I don't have to track data about derivative media in the database. I generate and trash as needed. It requires .htaccess and clean urls to function properly. The current cvs version is free of the DOS exploit in the prior version and allows multiple actions to be performed to create a derivative image. Only scale and resize are implemented. I'd appreciate feedback/patches/bugs if you play. *note: recent security fixes seems to have broken the preview feature in 'imagefield' when using clean urls. To enable previews, in the .htaccess in your files directory, comment out RewriteEngine Off, and add +FollowSymlinks to the Options line. ciao. .darrel. Footnotes: [1] imagefield: http://drupal.org/project/imagefield [2] imagecache: http://drupal.org/project/imagecache

2 2

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

question on page layout
by Josh Milane 05 Jul '06

05 Jul '06

I know this is a very basic question and this may not be the appropriate forum, but: Often when I browse Drupal sites (or really any CMS site), the page is just a bit too wide for my browser and I have to scroll left and right a tad. It actually looks as though it is going to fit but it then widens and does not. Also, many times there is a very long blank space extending downward, such that it makes the page appear empty to the casual viewer. You have to scroll down to find content, apart from menus that may be on the left or right. Are these things preventable? Or, are they to be expected when dealing with CMS tools? I appreciate your time. Josh

1 0

Accessbility - quick read about WCAG2
by sime 05 Jul '06

05 Jul '06

To: those interested in drupal accessibility. Re: version 2 of the Web Content Accessibility Guidelines (in development). Here is an easy-read insight. In the form of an interview with a WCAG contributor. http://webstandardsgroup.org/features/gian-sampson-wild.cfm

4 3

Utility module to configure blocks for all themes at once
by Nedjo Rogers 05 Jul '06

05 Jul '06

Some users have complained that block configuration is 'broken' for multi-themes in 4.7, because block status, weight, and throttle settings need to be made separately for each enabled theme. This simple module provides a fix, allowing the configuration of blocks for all themes at once. http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/nedjo/modules/bl… Enable this module and admin/block will provide global block settings, while block configuration for other enabled themes will allow only "Placement" (selection of region).

2 1