contrib

(or how to reduce a module's functionality)

During it's lifetime a contributed module's functionality expands, which often leads to a module packed with features. This growth of features is common for all software, but for Open Source the rate of expansion seems even higher. Feature rich software may be beneficial to the user but it comes at a price. Usability often suffers.

After walkah's presentation on Drupal 6 Themeing, I ported and contributed a theme to drupal.org. Some really great information that inspired me to contribute a new theme. I did a relatively detailed write up in the showcase forums.

http://drupal.org/node/212952

Thanks James, for the great presentation and answering the question we all had.

Hi guys,

I recently updated the worldpay.module for 4.7 and included an automated "callback" after the order is processed...i.e. the worldpay server tells the drupal site that the transaction was either APPROVED or CANCELLED (Denied happens at the worldpay end and the order is cancelled).

So a Drupal site admin who is setting up their worldpay enabled shop, enters in the worldpay_callback the worldpay server sends the "y" or "c" flags to. The problem is securing that transfer of information or in other words, validating the source.