Module development and code questions

Just flagging the first commit of a new worldpay.module for accepting credit card and debit card payments using worldpay. It might be useful to UK and Irish Drupallers (Worldpay is part of the Bank of Scotland Group).

As a mini disclaimer: I don't work for the Bank of Scotland Group or Worldpay. A client requested the module and with the help of rkendall, who created the initial version, the result is the worldpay.module.

I'm working on a new module, basicgallery.module, which just copies/moves the image.module's gallery functionality into a separate module and extends it just a little. It intends to be a _basic_ gallery module. See http://drupal.org/node/4321.

Hi everybody.

I'm working on a module which adds a new node type.
This new node type has a "closing_date" field which is in unix date format.

I need to show informations about the remaining time before the closing date calcolated from current time.

Drupal support the configuration of timezones.

What do I need to do to correctly use dates with timezones??

example:
closing date is 12/12/2006 15:00 GMT
I've set GMT as my timezone on my drupal account page
In my timezone is 12/12/2006 13:00
the module show "2 hours remaining"

Hi

I was using event module version 1.122.2.23 2005/10/04 and it had event's Start and End date and time filleds to fill. But now when i upgarded it to v 1.183 2005/12/13 , there is no start and end date filled.

can some body correct it. I need it very much

regards,
--rafi

Hi everybody!

I need to set the title of a node from other fields provided
by a custom module created by me.

The custom module has two fields called number and name.

How do I set the node title to be 'number . name' ?

thank you.

Fabio

I really hate the way that book.module generates the "printer-friendly" link without checking whether or not the current page is actually of the "book page" type. Instead it seems that the only check is:

if ($type == 'node' && isset($node->parent)) {

which is certainly not an ideal way of doing things... if a module also defines a "parent" attribute to the node, then it will get the printer friendly links no matter what. I have to hack the book.module every time I upgrade.