- Development - lists.drupal.org

[drupal-devel] Spread Fire Fox theme in CVS
by K B 22 Feb '05

22 Feb '05

A working version of the Spread Fire Fox theme by Chris Messina has been committed to the repository. I ported the theme from CivicSpace (4.4?) to 4.5. and CVS. Please check the announcement here http://drupal.org/node/17717

1 0

[drupal-devel] Marketplace forum?
by K B 22 Feb '05

22 Feb '05

Regarding this post: http://drupal.org/node/17697 Is it time to setup a "marketplace" forum for these kinds of requests?

4 3

[drupal-devel] [bug] Remove some cruft
by killes 21 Feb '05

21 Feb '05

Project: Drupal Version: cvs Component: base 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/remove-cruft.patch (2.98 KB) This patch remove some cruft from core: - three lines of dead code from node module - taxonomy_node_has_term() function. Was used nowhere. - definitions of page table. killes(a)www.drop.org -- View: http://drupal.org/node/17687 Edit: http://drupal.org/project/comments/add/17687

1 0

[drupal-devel] [task] Support for Taxonomy Images in theme settings.
by grohk 21 Feb '05

21 Feb '05

-Project: Taxonomy image +Project: Drupal -Version: cvs +Version: cvs -Component: Code +Component: system.module -Category: support requests +Category: tasks Priority: normal Assigned to: Anonymous Reported by: Anonymous Updated by: grohk -Status: active +Status: patch Attachment: http://drupal.org/files/issues/system_module_taxonomy_images.patch (507 bytes) Trying to keep this idea alive by resectioning to the correct place (I think) and freshening the patch against the latest CVS system.module. Please forgive me it this is inappropriate, but I think this patch is important for many users. grohk Previous comments: ------------------------------------------------------------------------ December 7, 2004 - 11:11 : Anonymous Attachment: http://drupal.org/files/issues/system_taxonomy_images.patch (727 bytes) This patch adds a checkbox on admin/themes/settings to toggle display of taxonomy images, only if this module is installed and activated. I've also sent a patch to phptemplate theme engine that it uses this checkbox to fill a new variable usable for templates. ------------------------------------------------------------------------ December 7, 2004 - 11:19 : Anonymous PHPtemplate patch that uses this new checkbox: http://drupal.org/node/14028 ------------------------------------------------------------------------ December 7, 2004 - 11:23 : Anonymous Patch for box_grey theme: http://drupal.org/node/14029 ------------------------------------------------------------------------ December 14, 2004 - 21:45 : jxs2151 I am unable to get this working after applying all three patches. When patching the phptemplate engine I get this error: patching file phptemplate.engine Hunk #1 succeeded at 73 (offset 1 line). Hunk #2 FAILED at 239. Hunk #3 succeeded at 237 (offset -23 lines). 1 out of 3 hunks FAILED -- saving rejects to file phptemplate.engine.rej The checkbox for allowing Taxonomy images in posts appears, I created the category, uploaded the image. I can view the image by direct reference in a url, it just does not show up on the page. ------------------------------------------------------------------------ December 16, 2004 - 19:50 : carlosparamio Attachment: http://drupal.org/files/issues/phptemplate_taxonomy_images_0.patch (1.31 KB) It seems that phptemplate.engine file has changed a little. Here is a new patch. When this patch was applied, then you can use the array $taxonomy_images[] in your node.tpl.php theme template to access to the image files for correspondant terms. For example, $taxonomy_images[0] to access to the image file for the first term. This is what box_grey patch does. ------------------------------------------------------------------------ December 16, 2004 - 19:52 : carlosparamio Attachment: http://drupal.org/files/issues/phptemplate_taxonomy_images_4.5.0.patch (1.13 KB) And here is a patch for Drupal 4.5.0 release also. -- View: http://drupal.org/node/14027 Edit: http://drupal.org/project/comments/add/14027

1 0

[drupal-devel] Glossary paged
by Maykel Moya 21 Feb '05

21 Feb '05

I'd like to make glossary not one page, but many pages, one for letter. Could you point me please to some documentation I should previously read to achieve my goal? Regards, mike

4 3

[drupal-devel] [task] Extend db_query()
by chx 21 Feb '05

21 Feb '05

Project: Drupal Version: cvs Component: database system Category: tasks Priority: normal Assigned to: killes(a)www.drop.org Reported by: killes(a)www.drop.org Updated by: chx Status: patch Do I need to say +1? chx Previous comments: ------------------------------------------------------------------------ February 21, 2005 - 13:48 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/db-query.patch (2.16 KB) We should make our database abstraction layer more robust and ensure that module authors can use it without string manipulations inside the query. Several queries use implode() to get their arguments into the query. This is undesirable as we rely on the module author to check the keys and values of such arrays for exploitation attempts. I have created the attached patch which shouldbe able to allow us to not use implode anymore. A minor problem is that all inserted values will be treated as strings. This might be a problem with PostgreSQL at least. However, the same strategy is already used in Drupal core without any complaints I know of. Summary: This patch will alow us to simplify some code in node.module, user.module, taxonomy.module and probably others. ------------------------------------------------------------------------ February 21, 2005 - 18:03 : killes(a)www.drop.org It's a patch. ------------------------------------------------------------------------ February 21, 2005 - 18:19 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/db-query_0.patch (2.07 KB) Squeezed out two lines of code after consultation with Karoly. Adds only 10 loc (plus some docs). -- View: http://drupal.org/node/17656 Edit: http://drupal.org/project/comments/add/17656

1 0

[drupal-devel] [task] Extend db_query()
by killes 21 Feb '05

21 Feb '05

Project: Drupal Version: cvs Component: database system Category: tasks 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/db-query_0.patch (2.07 KB) Squeezed out two lines of code after consultation with Karoly. Adds only 10 loc (plus some docs). killes(a)www.drop.org Previous comments: ------------------------------------------------------------------------ February 21, 2005 - 13:48 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/db-query.patch (2.16 KB) We should make our database abstraction layer more robust and ensure that module authors can use it without string manipulations inside the query. Several queries use implode() to get their arguments into the query. This is undesirable as we rely on the module author to check the keys and values of such arrays for exploitation attempts. I have created the attached patch which shouldbe able to allow us to not use implode anymore. A minor problem is that all inserted values will be treated as strings. This might be a problem with PostgreSQL at least. However, the same strategy is already used in Drupal core without any complaints I know of. Summary: This patch will alow us to simplify some code in node.module, user.module, taxonomy.module and probably others. ------------------------------------------------------------------------ February 21, 2005 - 18:03 : killes(a)www.drop.org It's a patch. -- View: http://drupal.org/node/17656 Edit: http://drupal.org/project/comments/add/17656

1 0

[drupal-devel] [task] Extend db_query()
by killes 21 Feb '05

21 Feb '05

Project: Drupal Version: cvs Component: database system Category: tasks Priority: normal Assigned to: killes(a)www.drop.org Reported by: killes(a)www.drop.org Updated by: killes(a)www.drop.org -Status: active +Status: patch It's a patch. killes(a)www.drop.org Previous comments: ------------------------------------------------------------------------ February 21, 2005 - 13:48 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/db-query.patch (2.16 KB) We should make our database abstraction layer more robust and ensure that module authors can use it without string manipulations inside the query. Several queries use implode() to get their arguments into the query. This is undesirable as we rely on the module author to check the keys and values of such arrays for exploitation attempts. I have created the attached patch which shouldbe able to allow us to not use implode anymore. A minor problem is that all inserted values will be treated as strings. This might be a problem with PostgreSQL at least. However, the same strategy is already used in Drupal core without any complaints I know of. Summary: This patch will alow us to simplify some code in node.module, user.module, taxonomy.module and probably others. -- View: http://drupal.org/node/17656 Edit: http://drupal.org/project/comments/add/17656

1 0

[drupal-devel] node_access_where_sql()
by Chris Cook 21 Feb '05

21 Feb '05

I'm debugging an issue in the project module on Drupal cvs. Most node queries use the node_access_where_sql() function like so. "SELECT foo FROM bar WHERE " . node_access_where_sql() . " AND criteria = true" However, the first test in the function returns nothing which will obviously result in an invalid query. Shouldn't the function return a value of "0" or something so that queries will always be valid? http://drupaldocs.org/api/head/function/node_access_where_sql

5 6

[drupal-devel] CVS log messages
by Tim Altman 21 Feb '05

21 Feb '05

Greetings, Did the CVS log message mails get turned off? I haven't seen one on the list since February 7th and I didn't see a post about any changes. I checked out the CVS RSS feed, but it doesn't show the changed files, so it's a bit difficult to tell what the log messages are referring to. -- Tim Altman

1 0