July 2005 - Development - lists.drupal.org

[drupal-devel] [feature] Multiple select functionality in profile module
by mathias 28 Aug '05

28 Aug '05

Issue status update for http://drupal.org/node/19356 Project: Drupal Version: cvs Component: profile.module Category: feature requests Priority: normal Assigned to: mathias Reported by: mathias Updated by: mathias Status: patch Attachment: http://drupal.org/files/issues/profile-multiple-select.patch (7.48 KB) This patch adds a 'multiple select' checkbox to the 'list selection' field type interface, allowing users to select multiple items from a single list. It looks the same as the 'multiple select' checkbox used during vocabulary creation. Field values are stored separately in the profile_values table and thus don't need to be serialized, keeping search functionality in tact. Note: this patch is not intended for 4.6. mathias

3 5

[drupal-devel] [task] Fix error reporting for failed mails to users
by nedjo 24 Aug '05

24 Aug '05

Issue status update for http://drupal.org/node/20139 Project: Drupal Version: cvs Component: user.module Category: tasks Priority: normal Assigned to: Anonymous Reported by: nedjo Updated by: nedjo Status: patch Attachment: http://drupal.org/files/issues/user-mail-error-messages.patch (7.2 KB) The user module has error handling for failed emails sent on password changing, but not yet in other cases, so that users may register and get a message that email has been sent when in fact it has not, an issue reported, e.g., here [1]. This patch adds tests for mails sent on user registration, generating appropriate user feedback (e.g., "Unable to send mail", etc.) and logs errors to the watchdog. [1] http://drupal.org/node/20026 nedjo

3 6

[drupal-devel] [feature] OPML export by category
by Prometheus6 22 Aug '05

22 Aug '05

Issue status update for http://drupal.org/node/22637 Project: Drupal Version: 4.6.0 Component: aggregator.module Category: feature requests Priority: normal Assigned to: Prometheus6 Reported by: Prometheus6 Updated by: Prometheus6 Status: patch Attachment: http://drupal.org/files/issues/AGGREGATOR_OPML.txt (1.5 KB) Added an optional parameter to aggregator_page_opml() to specify which category, if any, to create the OPML file for. Modified aggregator_menu() to crerate callbacks for the files. Prometheus6

3 8

[drupal-devel] [feature] Taxonomy rewrite
by chx 21 Aug '05

21 Aug '05

Project: Drupal Version: cvs Component: taxonomy.module Category: feature requests Priority: normal Assigned to: chx Reported by: chx Updated by: chx Status: patch Attachment: http://drupal.org/files/issues/taxonomy_db_rewrite.patch (6.71 KB) I'd like to present a use for db_rewrite_sql: taxonomy rewrites. If this goes through, it will be possible to create an access mechanism, languages and whatever for taxonomy. This is a very small change, I think, much smaller than the node_rewrite_sql megpatch was 'cos at the moment nothing changes. There are no DISTINCTs deleted. But this opens a door for future things. Also, this only affects taxonomy.module, 'cos no other module deals with term_data and vocabulary tables (well, forum.module does, but those queries does not need a rewrite). chx -- View: http://drupal.org/node/16452 Edit: http://drupal.org/project/comments/add/16452

8 21

[drupal-devel] [bug] No more floating node admin groups
by Bèr Kessels 21 Aug '05

21 Aug '05

Issue status update for http://drupal.org/node/26311 Post a follow up: http://drupal.org/project/comments/add/26311 Project: Drupal Version: 4.6.0 Component: base system Category: bug reports Priority: normal Assigned to: Anonymous Reported by: Bèr Kessels Updated by: Bèr Kessels Status: patch Attachment: http://drupal.org/files/issues/non_floating_node_admin.patch (835 bytes) For me -konqueror user- the floats on the "admin groups" of the node edit forms was always annoying. The textfields were inaccessible. But witth the collapsible parts they becme even moer annyoing: They now jump around on teh page when collapsed or folded out. This patch simply removes all the floats frolm these groups. I beleive theis looks and feels much better. It appears more stable on your page. It feels more like one expects: only a single row of collapses, instead of some odd row with columns. And last but not least: that part was amoungst the hardests to theme. I think this is a good moment to get rid of them. Oh, and it removes quite some code/cruft from drupal.css :) Bèr Kessels

5 14

[drupal-devel] [feature] support for path alias chains in drupal_get_path_alias.
by aws 21 Aug '05

21 Aug '05

Issue status update for http://drupal.org/node/21239 Project: Drupal Version: 4.6.0 Component: base system Category: feature requests Priority: normal Assigned to: Anonymous Reported by: aws Updated by: aws Status: patch Attachment: http://drupal.org/files/issues/includes_bootstrap.inc_0.patch (739 bytes) This is a small patch for function drupal_get_path_alias in bootstrap.inc. This allows a path to have a non-cyclic chain of aliases, and enables the path alias finder to walk up the chain to the top level alias. For example: taxonomy_menu/4/1/50 | topics/whats_new/events taxonomy/term/50 | taxonomy_menu/4/1/50 Now I can have all references to taxonomy/term/50 automatically point to the top-level alias, topics/whats_new/events. I am also posting a patch against Pathauto module which creates these multi-links automatically for categories when taxonomy_menu is present. (I will add followup with a link to that patch). Note that the inverse case (alias => path) is *not* necessary (in fact it would break the intention of this patch... --- There are several other ways to accomplish this; all of which are more involved. YMMV. I won't be insulted if this patch is rejected. :) An alternative solution would be to allow the destination column to accept non-unique entries. This would also require some sort of weighting otherwise the final resolution would be indefinate. A second alternative would be to have drupal generate taxonomy links in a more general manner, so that the taxonomy_menu module could change all the taxonomy links via the proper hooks. A *third* alternative would be to fix the menu system so that it does not require nested paths in the hiearchy, this way taxonomy_menu would not need to create its own paths. aws

3 4

[drupal-devel] [bug] Change default for files directory
by killes 20 Aug '05

20 Aug '05

Issue status update for http://drupal.org/node/23467 Project: Drupal Version: cvs Component: file system Category: bug reports Priority: normal Assigned to: killes(a)www.drop.org Reported by: killes(a)www.drop.org Updated by: killes(a)www.drop.org Status: patch Attachment: http://drupal.org/files/issues/file-default.patch (4.98 KB) Currently the defautl for the file storage directory is /files. This is a problrem if you should later decide to setup more than one site from the same source code. The attached page changes the default to be /sites/default/files (defautl is replaced by the site url if the default directory is renamed). killes(a)www.drop.org

6 9

[drupal-devel] [bug] Don't hard code forms into comment.module
by Robin Monks 17 Aug '05

17 Aug '05

Issue status update for http://drupal.org/node/23620 Project: Drupal Version: cvs Component: comment.module Category: bug reports Priority: normal Assigned to: Robin Monks Reported by: Robin Monks Updated by: Robin Monks Status: patch Attachment: http://drupal.org/files/issues/Comment.Control.hardcode.patch (4.02 KB) This patch removes all those nasty hard coded forms from comment.module's user Comment Control. Robin Robin Monks

5 15

[drupal-devel] [bug] Allow both postgres and mysql database connections from within the same site.
by adrian 17 Aug '05

17 Aug '05

Issue status update for http://drupal.org/node/19522 Project: Drupal Version: cvs Component: database system Category: bug reports Priority: normal Assigned to: adrian Reported by: adrian Updated by: adrian Status: patch Attachment: http://drupal.org/files/issues/multi-dbtype.diff (14.57 KB) When I originally coded the multiple database support I noted the caveat that only one database type was useable at a time due to the conflicting function names, so including both database.pgsql.inc and database.mysql.inc would cause a crash. This was also brought up again when someone reopened the multi-db functionality issue, and I am attaching the patch here. I would love for this patch to get into 4.6 if possible. I don't believe it's very invasive, and it fixes a long standing bug in the db api. I have been using some form of this patch on Bryght for the last 3-4 months, and have not found any ill effects related to it. I also clarified the db_set_active() comments a bit after I saw this issue (http://drupal.org/node/13115) adrian

3 4

[drupal-devel] [feature] Do not install a PHP code format by default
by chx 17 Aug '05

17 Aug '05

Issue status update for http://drupal.org/node/27330 Post a follow up: http://drupal.org/project/comments/add/27330 Project: Drupal Version: cvs Component: database system Category: feature requests Priority: normal Assigned to: chx Reported by: chx Updated by: chx Status: patch Attachment: http://drupal.org/files/issues/dbinit.patch (2.04 KB) Those users that are advanced enough that they need PHP pages, will be able to create a custom input format. chx

12 17