- Development - lists.drupal.org

Re: [development] update module
by FGM 12 Jul '07

12 Jul '07

What would be even better would be a way to specify from which server the module comes, using d.o. only as the default: it would allow easier maintenance of custom modules. ---- Original Message ---- From: development(a)robuustdesign.nl To: development(a)drupal.org Subject: Re: [development] update module Date: Wed, 11 Jul 2007 19:32:24 +0200 >While we are at this, is it possible to exclude an module/theme from > >the update_status list? >Say you have a site specific theme, which you do not want to list on > >the update staus list.. Is that possible at all? > >At the moment, my custom themes for drupal 6 are all in the state of > >'No available releases found'. > > > >Stefan

3 4

Templatizing Drupal's Themes: Documentation Proposal
by Earl Miles 12 Jul '07

12 Jul '07

In an effort to convert as much of Drupal's theme_* functions to tpl.php files as possible, I went through and did the forum module's theme functions (I picked those because I knew they'd be more difficult than some other modules). One thing I encountered is that this new system has no documentation standard for tpl.php files. I propose the following items: We should create a themes.php in contributions/docs/developer that contains definitions for theme_* functions that are being converted (or are new and will never have had a theme_* function before). Everything in this file should be @ingroup themeable. It would contain the full documentation for the theme function, including the @params. All .tpl.php files should contain a Doxy syntax @file directive that summarizes the template and lists variables that are commonly available. This list does not need to be exhaustive but it should include the most important variables, at a minimum. It should contain an @see to the template_preprocess function, if it exists, and a @see to the theme_HOOK function in the contrib docs. The template_preprocess_HOOK function should contain a @see to the theme_ function and a list of the arguments (mostly for reference while looking at the function; since the argument to that function will always just be &$variables, it's nice to get a look at what data is coming in). Both of the above should also contain an @see to the .tpl.php file -- however, in api.module, currently @see doesn't work on files. I think api.module could probably be modified to rectify this for us, or another method of referencing the file could work. Here are some examples. Note that I did these before I thought about a theme.php so these aren't updated for that yet, but I intend to. forum_list.tpl.php: <?php // $Id$ /** * @file forum_list.tpl.php * Default theme implementation to display a list of forums. * * Available variables: * - $forums: An array of forums to display. * * Each $forum in $forums contains: * - $forum->is_container: Is TRUE if the forum can contain other forums. Is * FALSE if the forum can contain only topics. * - $forum->depth: How deep the forum is in the current hierarchy. * - $forum->name: The name of the forum. * - $forum->link: The URL to link to this forum. * - $forum->description: The description of this forum. * - $forum->new_topics: True if the forum contains unread posts. * - $forum->new_url: A URL to the forum's unread posts. * - $forum->new_text: Text for the above URL which tells how many new posts. * - $forum->old_topics: A count of posts that have already been read. * - $forum->num_posts: The total number of posts in the forum. * - $forum->last_reply: Text representing the last time a forum was posted or * commented in. * * @see template_preprocess_forum_list() */ ?> Example in api.module: http://drupal.logrus.com/api/file/drupal/modules/forum/forum_list.tpl.php/h… /** * Process variables for forum_display.tpl.php * * The $variables array contains the following arguments: * - $forums * - $topics * - $parents * - $tid * - $sortby * - $forum_per_page * * @see forum_display.tpl.php */ function template_preprocess_forum_display(&$variables) { Example in api.module: http://drupal.logrus.com/api/function/template_preprocess_forum_list/head

1 0

update module
by Dries Buytaert 12 Jul '07

12 Jul '07

Hello world, I just reviewed the update.module once more and finally committed to to CVS HEAD. Kudos to dww and Earl for their hard work. This is an important module in terms of usability, but also for the security of everything Drupal. When security releases are made available, we'll be in a much better shape. If you were to ask me, this means that Drupal is the first Open Source CMS that takes security to the next level and that is not something to take lightly. (This probably warrants a post on the drupal.org front page post but I'll leave that up to dww and/or Earl to write -- if they want.) Great job, -- Dries Buytaert :: http://www.buytaert.net/

5 8

Advice on a menucallback
by Chris McGinlay 12 Jul '07

12 Jul '07

Hi, I'm trying to get a very small module running - I have a menu callback which generates a blank page on activating the callback. I'm basing this heavily on the onthisdate exemplar module on the drupal.org I point my browser at ?q=list_creative/T and receive an empty page. Can anyone advise me on what I'm doing wrong? Apologies if this should have been posted to support instead of development. Cheers Chris There is content in the database matching the T (see below). Here is the (tiny) module: <?php /* $Id$ */ /** * Display help and module information * @param section which section of the site we're displaying help * @return help text for section */ function rockstanza_help($section='') { $output = ''; switch ($section) { case "admin/help#rockstanza": $output = '<p>'. t("Manages blocks for accessing creative and excursion posts on RockStanza website") . '</p>'; break; } return $output; } //function rockstanza_help /** * Valid permissions for this module * @return array An array of valid permissions for the rockstanza module */ function rockstanza_perm() { return array('access rockstanza content'); } //function rockstanza_perm /** * Implementation of hook_menu(). */ function rockstanza_menu() { $items = array(); $items[] = array( 'path' => 'list_creative', 'title' => t('Creative works'), 'callback' => 'rockstanza_list_creative', 'access' => user_access('access rockstanza content'), 'type' => MENU_CALLBACK ); return $items; } /** * Generate HTML for the rockstanza block * @param op the operation from the URL * @param delta offset * @returns block HTML */ function rockstanza_block($op='list', $delta=0) { switch ($op) { case "list": //listing of blocks, eg. on admin/block page $block[0]["info"] = t("RockStanza Creative"); break; case "view": $block['subject'] = t('Creative works'); $block['content'] = ''; $first_letter_list = ""; //this will be a list of the first letter of broch names $result = db_query("SELECT title FROM {node} " . "WHERE {node}.{type} = 'poem' ORDER BY {title} ASC"); $index = array(); do { $t = db_fetch_array($result); $letter=$t['title'][0]; $index[$letter]=$letter; //store unique first letters in list } while ($t); $letterlist = implode ('',$index); //store in variables table foreach ($index as $fl) { $block['content'] .= l($fl,"list_creative/$fl", array('title' => "Creative works beginning $fl", 'target' => '_self'), NULL, NULL, FALSE, FALSE) . ' '; } break; } return $block; } //function rockstanza_block /** Group creative posts (e.g. poems) by the first letter of their title * use via menu callback * @returns content HTML */ function rockstanza_list_creative($firstletter) { $fl = '^'.$firstletter[0]; //get all poems with chosen first letter of title $result = db_query(db_rewrite_sql( "SELECT n.nid, n.title, n.type " . "FROM {node} n " . "WHERE n.type = 'poem' " . "AND n.title REGEXP '%s' " . "ORDER BY n.title ASC", $fl )); //leave only the node titles in the results $content = node_title_list($result); }

3 4

FW: [Drupal bug] fix text:big, add CLOB, update BLOB handling
by Edison Wong 11 Jul '07

11 Jul '07

May someone help me? I need some advice about this patch :) Issue status update for http://drupal.org/node/147947 Post a follow up: http://drupal.org/project/comments/add/147947 Project: Drupal Version: 6.x-dev Component: database system Category: bug reports Priority: critical Assigned to: hswong3i Reported by: hswong3i Updated by: hswong3i Status: patch (code needs review) Attachment: http://drupal.org/files/issues/drupal-6.x-dev-clob-0.4.diff (46.2 KB) this patch standardize drupal BLOB/CLOB handling for cross DB compatibility, e.g. db_update_* for LOBs value update, db_encode_*/db_decode_* for LOBs value encoding/decoding. change incude: * new API: db_update_blob(), db_update_clob(), db_encode_clob(), db_decode_clob() * updated API: _db_query_callback(), db_encode_blob() * module with BLOB change: cache * modules with CLOB change: aggregator, block, comment, contact, node for current stage, it is only a dummy mapping for "clob" type among mysql/pgsql, where mapping it as like as that of "text" type. BTW, it will greatly decrease the difficulty for other DB driver implementation, e.g. oralce, mssql and db2. this patch only change the handling for LOBs type. therefore, unless developer choose to use BLOB/CLOB type, nothing will affect them. on the other hand, if developer choose to use LOBs type, which means that they will have (nearly) unlimited storage size, BTW trade off some query level features, e.g. using GROUP BY, ORDER BY, WHERE, etc. hswong3i

1 0

Question about Drupal performance
by Lennart Borgman (gmail) 11 Jul '07

11 Jul '07

From the admin staff on a web host I am using I got a message saying: "Personally I'll recommend Drupal when pigs can fly, because I believe it is just that ... a pig. Slow even when I tried it on my dedicated server... its very full featured, but it is hardly peppy, at the best of times... and, I'm not aware of many Drupal sites on the platform -- there are definitely better choices performance wise at the current juncture." Can you comment on this, please? I am just going to setup some more Drupal site and got a bit frustrated. - L

15 37

drupal.org is down <eom>
by Jeff Griffiths 11 Jul '07

11 Jul '07

-- "Coffee should be black as Hell, strong as death, and sweet as love." ~ Turkish Proverb

9 14

AJAX Session Problem
by Darren Oh 11 Jul '07

11 Jul '07

http://drupal.org/cvs?commit=72806 Since this commit to the DRUPAL-5 branch, the Chat Room AJAX code is creating a separate session for itself. This is interferes with the code that prevents unknown users from observing the chat. Is this a bug in my code or in core?

1 1

The future of the project module(s)
by Chad Phillips -- Apartment Lines 10 Jul '07

10 Jul '07

After conversations with Derek, Dries, and Killes, I'd like to formally announce my new role as the official co-maintainer of project module, and related modules (cvslog, project_issue, etc.). Derek and I will be working together to provide support and direction for this very important suite -- as co-maintainers, we'll share final say on how things work in the project world, subject to the needs of drupal.org. This is extremely good news, as Derek has labored too long alone with a workload that outdistances what a single great coder can do. ;) I'll be coming on for day-to-day duties starting August 1st, which luckily will be in plenty of time for the 6.x conversion. At that time we'll also begin prioritizing and knocking out items on the currently very large to do list. Finally, listed below is a brief summary of our mutually agreed big- picture priorities for project*: 1) Improve how it supports the d.o's development process (functionality, bug fixes, usability, etc). 2) Continue to make it general enough to be used at other sites. We're finally turning the corner with this (e.g. with http:// jquery.com/plugins now a project*-based site, and certainly others). This step probably includes deploying a drupalorg.module soon, for truly d.o-specific code that should be moved out of project* completely. 3) Make the code easier to maintain and work with, to facilitate others contributing patches, testing, etc. 4) Move towards reusing existing functionality instead of re- implementing everything in project* (e.g. followups as comments, generic subscribe functionality, actions integration, eventually CCK integration, perhaps views + workflow, etc, etc). This should help with #3, as we rip out large portions of ugly code and move towards re-using well-supported existing code from other modules. Chad (aka hunmonk)

3 2

Drupal Profile module contribution
by Didine 10 Jul '07

10 Jul '07

Hello, I'm in the process of developing a Drupal powered recruitment website, i found the profile module very useful, but missing the upload file type. I don't know if this was already added or not but i made a test by adding it :) Please find the modified module in enclosed, feel free to send me your comment on how bad i'm developing :) Greetings from Morocco :) -- Didine

2 1