Module development and code questions

Hello All,

Currently I am in the works of creating an extensive video library of athletic drills in Drupal 4.7.3.

To do this I am using:
video.module
views.module
taxonomy_menu.module

I am experimenting with several different modules in order to create a somewhat alternative advanced search exclusively for the video libaray. Here is what I am trying to achieve:

• Seperate dropdown lists for each vocabulary
• Choose EITHER a search phrase, or use the drop down lists (taxonomy vocab > terms). Where if you specify a search phrase, search ignores any values in the drop down lists.
• Offer each term in a vocabulary drop down as well as an "all terms" option which will search all vocab terms.
• First the search looks for the term in the exercise title in the library
• Second the search looks for the words or term in any of the 3 search criteria we have for the exercise library, that is muscle group, training modality and exercise equipment

To help illustrate what I am talking about here is an image

I have been experimenting with:
refine_by_taxo
taxonomy_browser
taxonomy_ezfilter

and I was not able to get any of those to perform exactly like what I am looking for.

If anyone has any ideas as to how to do this please let me know. I'd be open to using existing modules or a paid development of a module (if paid please email me quotes via my personal contact form)

We are building an ecommerce site using Drupal 4.7, and need to add custom fields during the checkout process. We require that the 'buyer' add special info to be integrated into the product.

Does anybody know how we can accomplish this?

We are building an ecommerce site using Drupal 4.7, and need to add custom fields during the checkout process. We require that the 'buyer' add special info, four seperate fields, so that info can be integrated into the product.

Does anybody know how we can accomplish this?

I've developed a new module for Drupal for content localization : localizer.

This module offers the following features :
- translates the user's menus
- provides a language switch block
- translates the node's content

This module has been inspired from internationalization module (i18n).
It uses very large portions of code fron i18n module.
Differently from i18n module, localizer doesn't change the url path adding the locale prefix and in this
manner it prevents some problems that this tecnique can generate (for example non activation of the
current link in the menu or in the primay or secondary links groups).
Localizer doesn't need that every node has an url alias.
If you want, it is sufficient that you assign an url alias only to one of the nodes of the translation.
Then the module will display the correct translated node without changing the displayed url.
Localizer doesn't need any patch to the Drupal core.

Localizer offers a block to language switch, but you can
change the language from every link simply adding the
parameter locale to the url, like : locale=en

Two Drupal function have been reimplemented for internal use only :
localizer_locale and localizer_t (corresponding to functions locale and t).
The two new functions make almost the same work, except that they accept a new
parameter : locale. So it is possible to get a translation for a particolar locale through the localizer_t function.

I'm trying to use metaweblog's api to programmatically post data to blogapi.module. When i try calling the function blogger.getUserInfo('1','username','password') i am getting and XMLRPC fault returned. When i look at the api and then at the code i see some discrepancies . I'm using version 1.82 in drupal 4.7.3. Is this api functional? The blogid hack, does it still apply? are there any examples for developers anywhere? Can i get an example from someone as to what i should be posting?

for example the drupal function:

I've decided to try to upgrade the trip_search module (or at least parts of it) to 4.7, for various reasons (notably the fact that I want much more control over the user interface than I get with the standard search). It's turning out much more difficult than I thought :-(

Notably, I'm currently stuck on using "pager", which trip_search calls without using pager_query. I think I've worked out how to initialise the various variables needed by pager (actually I just copied this from Robert Douglass) and the code to get the paged string seems very simple, it is:

      if ($pager = theme('pager', array(), $max, 0, )) {
        $str .= $pager; // $str contains all the search results on the page, plus the pager links
      }

However, for a reason which is completely mysterious to me, when I get the (correct) list back, with the correct number of page number links at the bottom, the links all point to the same place which is:

http://localhost/drupal-4.7.2/trip_search?page=1&edit[keys]=lorem+ipsum&edit[content_type]=&edit[form_id]=trip_search_form

Why does it look like this and not like this:

http://localhost/drupal-4.7.2/trip_search?page=1&keys=lorem+ipsum

which is what I would expect? And what do I need to do to get this to come out right?

I'm especially confused because this app