March 2007 - Development - lists.drupal.org

Re: [development] Accessing CCK field data (single, multiple, or shared) from another module
by Karen Stevenson 04 Jun '07

04 Jun '07

To find the right table for a field for a SQL query, use the API, like this: $db_info = content_database_info($field); $table = $db_info['table']; That will always return the right table for the requested field. $field needs to be the complete field array, not just the field name, so if you only have the field name, you would do: $field = content_fields(my_field_name); $db_info = content_database_info($field); $table = $db_info['table']; content_database_info($field) also contains info about the columns declared by the field so you know what field names to use in a SQL query. It returns an array that looks like: Array ( [table] => content_type_story [columns] => Array ( [value] => Array ( [type] => varchar [length] => 50 [not null] => 1 [default] => '' [sortable] => 1 [column] => field_phone_value ) [value2] => Array ( [type] => int [length] => 10 [unsigned] => 1 [not null] => 1 [default] => 0 [column] => field_phone_type ) ) ) ----- Original Message ---- From: Rob Barreca <rob(a)electronicinsight.com> To: development(a)drupal.org Sent: Thursday, March 22, 2007 7:55:31 PM Subject: Re: [development] Accessing CCK field data (single, multiple, or shared) from another module > > Is there a function for getting the data that you can just give a node > type and a field name and it handles the rest? This is something I've just run into as well. I have a hardcoded to query the DB for the multiple field table, but have a TODO in there to find the right API call. Rob Roy Barreca Founder and COO Electronic Insight Corporation http://www.electronicinsight.com rob(a)electronicinsight.com Benjamin Melançon wrote: > Gracious developers, CCK people especially... > > I wrote an access control module that works with the node relativity > module to cascade permissions to all nodes lower in a hierarchy. I > hard-coded a query for a userreference field on a custom content type > as one way to give a user access to a node (and its descendants). > > In generalizing this, the current stumbling block is the way CCK > stores single instances in the content data table and shared instances > of a field in a separate table. > > Is there a function for getting the data that you can just give a node > type and a field name and it handles the rest? > > Or is there a place to check what the case is for a particular field? > (Even a "column_exists()" function would do it for me, but haven't > found one in PHP...) > > It's being developed in Drupal 5 and fixing this (as well as saving > explicitly permitted users when creating a new node) is all that's > needed for posting the project for general use. > > Many thanks, > > ben > > Agaric Design Collective > Open Source Web Development > http://AgaricDesign.com/ > > People Who Give a Damn > building the infrastructure of a network for everyone > http://pwgd.org/

5 4

PHP version stats
by Karoly Negyesi 26 Apr '07

26 Apr '07

Hi, You can find monthly graphs on nexen, the latest is http://www.nexen.net/chiffres_cles/phpversion/16636-php_statistics_for_febr… Regards NK

15 21

Re: [development] Overlap / Sharing work
by Ken Rickard 03 Apr '07

03 Apr '07

Rob- <ego trip> As for tracking friends' content, the MySite module has methods for this, and an API for adding new functionality. http://drupal.org/project/mysite And I'm looking for co-developers.... </ego trip> - Ken Rickard agentrickard

2 1

Theme registry - templates
by Dries Buytaert 02 Apr '07

02 Apr '07

Hello world, at hackfest, Earl wrote a patch to make it easier to theme Drupal: http://drupal.org/node/130987 I'd like to see this patch committed so we can start taking advantages of it. Could we all take a close look at it? Thanks, -- Dries Buytaert :: http://www.buytaert.net/

6 6

Overlap / Sharing work
by Rob Barreca 02 Apr '07

02 Apr '07

Here are some current things I am working on for a project. Wanted to post here to see if anyone is working on something similar and was interested in working together: * Amazon Wishlist integration * Friends' activity block like Facebook: I'm still thinking about this. We can easily get node and comment Views with Buddylist like "My Friends' Recent Nodes", but we want an aggregated watchdog-like list that has other stuff too "Your friend Joe made friends with some user Rachel", "Some user Steve posted a comment on some node of yours", "Your friend Joe posted a comment on some other node", Voting, etc. I want to build this as flexible as possible so it can be contributed back. A new module that maybe uses Actions to perform a logging action on certain user operations. Not sure if that makes sense. But it's definitely like a watchdog log per user. * Pulling facebook profile info in from the Facebook API * Probably work on the Community Tags module for 5.x that was a clean up of my huge Tagadelic patch a while back so users can tag other users' nodes * Doing some invite stuff, so extending or cleaning up invite.module may be in order * Maybe some ACL-Buddylist integration to allow friends to have extra privileges (low priority) * Want to do some FOAF stuff like LinkedIn to see how far removed someone is from you (low priority) -- Rob Roy Barreca Founder and COO Electronic Insight Corporation http://www.electronicinsight.com rob(a)electronicinsight.com

5 5

One other teensy FAPI question
by Syscrusher 01 Apr '07

01 Apr '07

Using the 'date' field type, how does one cause the field to allow a "not specified" date? Is this not supported? I want to use dates in a search form as an optional parameter, not a required one. Right now I am detecting a "null" date by looking for 1900-01-01, but in this particular application (a genealogy research module), that happens to be a perfectly legitimate value. Probably nobody else has needed this yet, and it isn't supported, but I thought it didn't hurt to ask. At worst case, I may have to just reserve that value. I don't want to burden the user with a checkbox for each of the *four* available date search parameters. Scott -- ------------------------------------------------------------------------------- Syscrusher (Scott Courtney) Drupal page: http://drupal.org/user/9184 syscrusher at 4th dot com Home page: http://4th.com/

2 2

node visualization tools
by Peter S. Requadt 31 Mar '07

31 Mar '07

Hi, I'm planning on developing some modules, most likely to be based in AJAX, for graphically visualizing node organization on a drupal site using tree structures and venn diagrams. Does anyone know of any existing projects that are similar to this? Peter

1 0

bet you didn't know you could query d.o's CVS like this...
by Derek Wright 31 Mar '07

31 Mar '07

i just stumbled into a whole new world of power for viewing CVS activity on drupal.org: http://drupal.org/node/132694 who knew? ;) now someone just needs to make a good UI for harnessing this power... any volunteers? thanks, -derek (dww)

2 1

Retrieving form values during intial form rendering
by Syscrusher 31 Mar '07

31 Mar '07

I'm really stumped with what I thought would be a simple thing, and I'm finally asking for some help. This is in Drupal 5. I have a form that is *not* node-related, that needs to be able to do the equivalent of a preview, in that it needs to be rendered with its default values being the fields from its previous submission. Sounds simple, right? Here's what's happening, though: My form gets built fine during HTTP GET, with #default_value being set appropriately. The user submits the form, and $_POST gets the right data. That data is passed to hook_form_validate() and then to hook_form_submit(). So far, so good. But when I get to hook_form(), the $_POST is no longer set, because of the drupal_goto() that results from hook_form_submit(). So I wondered, "Where does my data get stored?" Apparently, I wondered this like everyone else, because the Forms API handbook page says: "The practical upshot to this is that many developers immediately find themselves asking the question of "where does my data get stored?". The answer is simply that it doesn't. You put your $form data together, perhaps loading your object from the database and filling in #default_values, the form builder then checks this against what was posted." Loading from the database isn't an option, because these happen to be search parameters that aren't stored in the database. Most of the extant Drupal code I looked at for an example doesn't apply to my situation, because they all use $node->foo to store their data. My module is managing an app-specific table that isn't connected with nodes in any way, and the particular form in question is a query rather than data entry, so I don't have a table where I can put the data. Now, I think I can probably solve this using $_SESSION, but that seems so... inelegant. I've got to believe someone has solved this before, and that there is a "Drupally-correct" standard way to do what I need to do, which is simply to have a form that defaults to its previous values each time it's rendered after a POST operation (but not a GET). Can anyone tell me what I'm overlooking, or point me toward one of your own modules that does this that would serve as an example? Many thanks. Scott -- ------------------------------------------------------------------------------ Scott Courtney | "I don't mind Microsoft making money. I mind them scott(a)4th.com | having a bad operating system." -- Linus Torvalds http://4th.com/ | ("The Rebel Code," NY Times, 21 February 1999) | PGP Public Key at http://4th.com/keys/scott.pubkey

2 2

Re: [development] Retrieving form values during intial form rendering
by Peter Wolanin 31 Mar '07

31 Mar '07

I'll agree with Mark here- I've used this trick a few times. Take a look at how node previews are generated. -Peter ---------- From: "Mark Fredrickson" <mark.m.fredrickson(a)gmail.com> To: development(a)drupal.org Date: Fri, 30 Mar 2007 17:19:57 -0500 Subject: Re: [development] Retrieving form values during intial form rendering I think you want to research '#button' and '#after_build'. '#button' will send you form values without a full submission. '#after_build' will allow you to do something with the built values (node.module uses #after_build to prepend the rendered preview version) You may have to supply a '#name' element for your button so that it doesn't get stuck in 'op'. I'm a little rusty on that point. Cheers, -Mark

1 0