Under active development

Step 1.) Create Module file like: yourmodule.info

name = "yourmodule module"
description = "Send Emails for multiple friends module"
core = 7.x
files[] = yourmodule.module

Step 2) Create module file like: yourmodule.module

<?php
function yourmodule_menu() {
$items = array();
$items['sendemail'] = array(
'description' =>'Provide invite form',
'page callback' =>'drupal_get_form',
'page arguments' =>array('yourmodule_form'),
'access callback' => TRUE

);
return $items;
}

function yourmodule_form($form,&$form_submit) {
$form['title'] = array(
//'#title' => 'email',
'#type' => 'textfield',
//'#name' =>'text1',
'#attributes' =>array('placeholder' => t('Enter Your E-mail address')),
);
$form['title1'] = array(
//'#title' => 'email1',
'#type' => 'textfield',
// '#name' =>'text2',
'#attributes' =>array('placeholder' => t('Enter Your E-mail address')),
);
$form['title2'] = array(
'#type' => 'textfield',
// '#name' =>'text3',
'#attributes' =>array('placeholder' => t('Enter Your E-mail address')),
);
$form['title3'] = array(
'#type' => 'textfield',
//'#name' =>'text4',
'#attributes' =>array('placeholder' => t('Enter Your E-mail address')),
);
$form['submit'] = array(
'#type' => 'submit',
'#value' =>'send invites',

);
return $form;

This will make your website pass gas when you scroll.
Just for novelty.

Imports properties from the Vebra Live estate agent software and converts them to nodes

What it does

Propels Drupal 6 sites into the Future by suppressing PHP strict warnings created when running a Drupal 6 site on PHP 5.4.

If you've transferred a Drupal 6 site to a server running PHP 5.4 chances are pretty good that you'll see tons of PHP warnings flooding your watchdog logs and displaying on-screen messages about PHP strict warnings in contributed code. Some of these will eventually be fixed by maintainers but some inevitably will not. Sure you can fix your own code but what about all the others? What to do? You have a few options:

1.) Maybe you've switched your Drupal error reporting to be "log only". That's fine but expect your watchdog table to balloon in size very quickly and you're probably noticing a significant performance lag.

2.) Maybe you tried to turn off strict warnings via settings.php, php.ini or .htaccess. None of those will work because Drupal's drupal_error_handler function will override those settings unless you set the value to 0 (no error reporting at all) which is not a good thing either.

3.) You could hack core, kill a kitten and move on. It would work, but what about the kitten?!

Description

Based on Biblio Scholar, this module adds Dublin Core metatags to biblio nodes.

this is a module for payment with paywords system of banorte mexico.
if you want more security o another thing you can edit the module and send me your changes.