Module development and code questions

Hello everyone,

I recently insrtalled image.module and image-import into Drupal 4.6. I can upload with the image.module, but I cannot bulk upload. The reports are good, e.g.:

image import 2005-06-06 13:07 Successfully imported 17 file(s) out of 17, with 0 captioned fro john plum details
image import 2005-06-06 13:07 Imported "files/images/temp/yum yum.jpg" as node 262 john plum

It's not clear from the help file whether the image.module for download in the 4.6 modules repository is needed or not for the image-import module. Is the walkah module any different from the core module? It seems not, from my efforts trying to confgure it in modules' admin settings.

Isn't this the same image.module in the core? If not, then why does it share the same module settings space? It states in the install text that updating is not necessary if installing imagle-import for the first time.

Hello,

I didn't see this anywhere in the forums, so I thought I'd post it although I have a hard time imagining it hasn't been requested before.

I'm sure quite a few Drupal users develop sites based on taxonomy (section, category), and based on that often there is the need for a separate content type and/or "node limite per page" for one of those taxonomies. The Taxonomy Context module makes a good "frame of reference" tool for tracking where the user is, but as far as I can tell a new DB query would be required to limit the number of nodes per page for the given taxonomy. If that's the case then I believe that query would need to be done in the context of a page node, unless code in the page.tpl.php file would override the default query for a given taxonomy. Is that wrong? I suppose I could be missing something as I am new to Drupal.

In each taxonomy the Administrator has the option to limit the types of content that appear inside it. An added "node limit" for that type relevant to the taxonomy would be, in my opinion, a great feature.

I have had many instances where this would be helpful, one of which is for displaying images per page. I have had little luck with the album/folksonomy/image combination of modules (can't delete an album?) and based on the warnings I've seen in reference to the Gallery module I'm hesitant to dig in. Obviously, I could just hack this in, but a feature such as the one described above could prevent some real messy code and hierarchy. if anyone has an idea of how a module might be extended to accomplish this, please let me know. I've also checked out the Section module, but I am hesitant to break into that as well.

I'm trying to analyze Drupal's code a little bit. Question for developers: how does Drupal render links of node titles on the default node page (that's the page you get when you enter URL ending with "?q=node")?

For example when I create a "page" node with title "TitleXXX", and then go to http://www.example.com/?q=node, my new "page" node appears there at the top, with a fat title/link TitleXXX, plus teaser, plus links "add new comment" and "read more".

So far I can trace the following sequence of calls for "?q=node" (in order to find out how are those links being built dynamically by Drupal):

• ?q=node activates node_page_default() in node.module
• node_page_default() loops over a pager query, and in every iteration, node_view() gets called (with teaser=true)
• hook_view() gets called - but no page_view() exists for page.module, so no HTML gets generated
• node_invoke_nodeapi() gets called - but no page_nodeapi() exists for page.module, so no HTML gets generated
• links below the node ("read more", "add new comment") are being built - but just those links
• finally, theme('node', $node, $teaser=TRUE, $page=FALSE) is
  being applied - this function resides in includes/theme.inc however title link doesn't get generated there either!

What am I missing here? Can anybody shed some light as of where that link code:

I am developing a new module, along with a new node type. When creating a new node, I would like two of the values to be driven from comboboxes...easy right? Trick is, I want one combo box to drive the content of the next combobox. I have all of the values, and the relationships in database tables.

Any ideas or suggestions on the best way to do this in a Drupal form when a node is created?

Thanks!

hello folks, i'd like to find out about creating containers for groups by category with the Organic Groups module and am wondering if anybody has done this...

for example, if you've got tons of users, and then (hypothetically) hundreds of groups, would it be possible to generate 'categories' for the groups to be assigned to - with the ability to assign the same group to more than one category just like other nodes in drupal? for example: imagine a bunch of groups that are fan clubs (just an example, NOT what i'm doing):

current group listings include: