Module development and code questions

Hi,

I am creating a set of modules around some core framework

module
module -> optionalmodule1
module -> optionalmodule2
module -> optionalmodule3

How can I generate data in the optional modules for example $form['modulename'] and use that data in the core module?

I don't want the "core" module to have to know about the optional ones.

Example.

optionalmodule1_function returns $data[1]
optionalmodule2_function returns $data[2]
optionalmodule3_function returns $data[3]

HI,

I am currently working on 4.7.x with the PROTX payment module and I am trying to add some new features, such as re-displaying the credit card input form if the transaction fails. I have created a URL, protx/failed, which executes (I have set my VSPDirect simulator to REJECTED for now) as expected but when I try again it tells me that the transaction ID cannot be used.

Thus my question, after much code trawling...

I'd like to create a vendor directory listing, which module(s) would I use to create this?

Hi all,

I'd like to use my drupal installation includes to do a simple database query from php (I don't want to record host/user/password information twice).

What files should I include in order to be able to use db_query ?? :

I thought this should work but it doesn't :

include_once '../blog/includes/bootstrap.inc';
include_once '../blog/includes/common.inc';
include_once '../blog/includes/database.inc';
$result = db_query("select * from ...");

Any ideas ??

Thanks

hi search-experts,

i am trying to setup an advanced search for a little niche-jobsite like monster.com etc. like http://www.job.de/job_suche/refine.phtml or http://drupal.org/search/issues

job-listings will be categorized with the taxonomy-module and i have installed trip_search.

user should select different search-kategories in different multiselect-boxes (from taxon-modul).

e.g.

For Drupal 4.7 I have used official weblinks module: http://drupal.org/project/weblinks

But I was not satisfied with it, since:

* it is too heavy for new node type module
* it use own non-standard category system
* too much unnecessary menus and administrations possibilities (it shall be moved to separate module, if someone need it)
* module do not count clicks