The p01-contact default form

p01-contact is a php script who let you simply create advanced contact forms.

p01-contact is natively a plugin for GetSimple cms.

An example of email received. deprecated image

There is hundred of sites using this script, here are some examples :

• chini.de - German industrial flooring.
• ilc-group.ru - Russian transport.
• imbalance.net - English heavy metal portal.
• jp-transport.pl - Poland transport.
• werefrogs.com - U.K. rock band.
• studiofilm.pl - Poland film studio.
• ayutek.ru - Russian cleaning services.
• slubnestyle.kknet.pl - Poland decoration.
• mfarband.ru - Russian band.
• lameo.fr - French composite wood company.
• creer1site.fr - French web-designers.
• kittyears.net - Italian webdesigner.
• wiekehoeke.com - Nederland photographer.
• rubannoir.net - Italian dance school.
• chinaspare.ru - Russian cars accessories and spare parts.
• energy-syn.nba.ro - Romanian energy.
• pinturas-romar.com - Spanish painting.

1. Download the last stable release or the development release.
2. For GetSimple, unzip it in plugins/ directory.

Include the script :

include 'path/to/p01-contact/p01-contact.php';

Create a P01contact instance :

$p01contact = new P01contact();

Define default email address with :

$p01contact->default_email = 'address@domain.ext';

Add form(s) by parsing a string containing tags according to the syntax described below :

echo $p01contact->parse($string);

For example, to display a default contact form :

$p01contact = new P01contact();
$p01contact->default_email = 'address@domain.ext';
echo $p01contact->parse('(% contact %)');

Simply write in a page a tag according to the syntax described below, and a form will appear!

Reminds you to fill the Meta Description, accessible in page options →
If you don't, GetSimple will show the tag in the source code of the output page.

You can use it everywhere you want by manipulating the variable $p01contact, already initialized.

To parse a string and replace tags by forms, use :

$p01contact->parse($string);

For example, to display a default contact form in your sidebar :

<?php
get_component('sidebar');
echo $p01contact->parse('(% contact %)');
?>

The syntax used is really simple, but powerfull.

The minimum tag is :

(% contact %)

It create a default form (see Default params in settings) destinated to the default email address (see Default email in settings).

In the following, to define some parameters we will follow the word “contact” with a colon :

(% contact : parameters %)

You can define any recipients you want by adding valid addresses separated by commas, like :

(% contact : address@domain.ext %)

(% contact : address@domain.ext, another@domain.ext %)

(% contact : address@domain.ext, another@domain.ext... %)

You can construct your own form by specifying the fields like you specify the recipients :

(% contact : field, field, field... %)

By replacing field by valid fields types and/or fields options.

There is two sorts of fields types : the specials and the generals.

The specials types are fields doing specific actions :

Those ones are used in mail :

• name : a text field used as source name in email. If it's not used, the sender name will be “Anonymous”.
• email : a text field with email form verification, used as source address in email. If it's not used, the sender email will be “anonymous”.
• subject : a text field used as subject in email. If it's not used, the subject will be ”(No subject)”.

Those ones have a verification of their format :

• phone : a text field with phone number format verification.
• website : a text field with web address format verification.
• message : a textarea with minimum text length verification.

Those ones protect your forms :

• captcha : a reloadable capcha image with text field entry verification.
• fieldcaptcha : a simple and integrated capcha system. Add a field with mention do not fill this field. If the field is filled, it's a robot. :p
• password : Check if input value is equal to required value.

And there is this one too :

• askcopy : a checkbox allowing the user to receive a copy of the email.

These fields are not doing anything special, but they are displayed in mail content.

• text : a text field, for short information.
• textarea : a textarea field, for longer information.
• checkbox : one or more check boxes and labels. Several may be checked.
• select : a drop down list with defined values.
• radio : one or more radio buttons and labels. Only one may be checked.

If you enter an unknown field type, no field will be displayed but its name will be displayed and mentioned in <div> class :

(% contact : something %)

<div class="field something">
    <div class="label">
        <label>The title</label>
    </div>
</div>

Use that to create separations texts, titles, answer/response…

(% contact : answer "This is an answer", response "This is the response" %)

/* apply to every fields */
.p01-contact .field{margin:5px;}
/* those are known fields */
.p01-contact .text{margin:5px;}
.p01-contact .captcha{margin:10px;}
/* those are user-defined fields (labels only) */
.p01-contact .answer{color:red;}
.p01-contact .response{color:blue;}

• An exclamation point after the field type define it as required, like :

  message!

  A required field left empty will display a “This field is required” error.

• A text between quotes define field title, like :

  message "Tell me something :"

• A text after an equality symbol define field pre-filled value, like :

  message = value

  Except for password field, where that define required value :

  password = required value

  For multiple values fields, separate values by vertical bars :

  checkbox = "value1" selected | "value2" selected | "value3"
  select = "value1" | "value2" selected | "value3"
  radio = "value1" | "value2" | "value3" selected

  Note the use of selected keyword to define selected value(s).

• A text after an arrow symbol define field locked value, like :

  message => value

  Works with multiple values fields :

  select => "value1" | "value2" selected | "value3"

fieldType! "title" => value

Default :

(% contact %)

Default with defined recipients :

(% contact : recipient@domain.ext, other@domain.ext %)

Advanced form construction :

A minimal one :

(% contact : email!, message! %)

A big one :

(% contact : address@domain.ext, another@domain.ext,
             subject => About this script,
             email!,
             textarea "How old is born Napoléon?",
             phone,
             radio "Do you like this script?" = "Yes" selected | "No", 
             website,
             select = "One" selected | "Two" | "Three" | "Four" | "Five" ,
             message = Say something!,
             password = tomato,  
             captcha, 
             askcopy %)

You can display a functionnal configuration panel with :

echo $p01contact->panel();

In GetSimple, simply access to it from the admin panel, in the Plugins tab :

When disabled, the forms are displayed and all the process are executed (fields verifications, etc…) but finally, instead of sending the mail a message “Plugin disabled” is displayed.

Define email used for default froms. Default email can also being set with :

$p01contact->default_email = 'email@domain.ext';

This is indicated in italic below. (for GetSimple, this is set to admin email)

Settings default address prevails to that defined in code.

To send a mail, a form need at least one valid recipient defined in tag, or a valid default email defined in code or a valid default email defined in settings.

Default language is by default to English, and can be set with :

$p01contact->default_lang = 'fr';

For GetSimple, default is the language defined in GetSimple.

You can also define to use a particular language, by selecting one in the list of existing translations. Those beginning with ”~” are not fully translated.

Minimum number of characters to write in message fields to be valid.

This setting does not affect the textarea fields.

This setting let you defining the form structure used when no structure has been set in tag, in other words default tags.

Use the form construction syntax described above.

Blacklist : indicating values that must not be present in the field to send email.
Whitelist : indicating possibles values required for the field to send email.

All values must be separated by commas.

The debug mode disable mail sending and display p01-contact object data structure. If a form is posted, it display data sent and the email that would have been sent.

The last stable version is translated in :

• Dutch 45%
• English
• French
• German
• Italian 45%
• Russian 45%
• Spanish 45%
• Swedish 45%

The development release is already translated in :

• Bulgarian
• Dutch
• English
• Finnish
• French
• German
• Hebrew
• Italian
• Lithuanian
• Polish
• Portuguese
• Russian
• Spanish

Some translations are not complete, and will not be included in the next stable release :

• Swedish 45%

Thanks to Martin Köhler, Carlos Navarro, Kristian Salonen, Nicola Sarti, Vaidotas Kazla, Thomas Stolwijk, Evandro Xavier Azevedo, Eugene Vetrov, Göran Söderberg, barlew, Iggy Pritzker, Panayot Kuyvliev and Daniel A. Rodriguez.

1. Go to :

   p01-contact/lang

   (Use development release : there is probably some translation changes since the stable one.)

2. Duplicate an existing file fully translated (in the language that you understand more easily) and rename it with the new language code, according to ISO 639-1. Example : for japanese, rename it to jp.php.
3. Open the new file with a text editor and translate the sentences after the arrows :

   'sentfrom' => 'Translate me here',

4. Change the file header to indicate the language used and your name. Example, for japanese :

   /**
    * Japanese language file
    * @author Your Name
    * @package p01-contact
    */

5. Please send me your translation, so I integrated it into the next version!

2010-11-06
Download 0.9.1.zip.

• Full german translation
• Bugs fix : captcha verification and reload
• Url to captcha defined with GS $SITEURL (should work with url rewriting)
• Captcha required by default (default params with captcha!)
• Languages names instead of ISO codes in configuration panel (new lang/langs.php file, associating iso and name).

2010-11-05
Download 0.9.zip.

• New special field : fieldcaptcha.
• New special field : password.
• New special fields : checkbox, select and radio.
• Security : implementation of sessions tokens.
  • Prevent from history back.
  • Prevent from reload.
  • Prevent from Cross Site Forgery Requests.
• Script fully separated from GS.
  • p01-contact can be used anywhere.
  • p01contact_gs.php do the link with GS.
• Configuration panel sentences and info messages added to language system.
• New setting : default email. Editable by code and settings.
• Editable default lang.
• Blacklist/Whitelist choice prepared.
• General fields have checklists too.
• HTML/CSS structuration.

2010-10-30 to 2010-11-02
Download 0.8.3.zip or 0.8.2.zip or 0.8.1.zip or 0.8.zip.

• Fully object oriented recoded.
  • Unlimited multiple parsing.
  • Unlimited fields manipulation.
• Debug mode.
• Plugin last version check (Extend API).
• Italian, russian, spanish translations.
• Possible translations are listed in admin panel.
• Many bugs fixes and improved functioning.

2010-10-27
Download 0.7.zip.

• Administration panel. Accessible in “Plugins → p01-contact”.
• Fields editable blacklists. Some anonymous-webmails included.
• Message minimum length setting.
• Default form stucture is simply defined by default tag parameters.
• Use/mimics fancy GetSimple info messages.
• Field label bug with multiple forms fixed.
• Captcha reload bug fixed.

2010-10-25
Download 0.6.zip.

• Separated languages files.
• Separated config file.
• Doc-commented code.
• Main function is now simply “p01contact”.
• Links to this page, GS extend and GS forum in plugin description.

• 0.5.zip 2010-10-17
  • Tag-with-no-options allowed : the recipient is the administrator address.
  • Clarifying use and process.
  • New special field : askcopy.
  • New special field : website.
  • Allow adding not-special fields : checkbox, text, textarea.
  • Configurable field name.
  • Configurable field value (pre-fill).
  • Configurable field locked-value (not editable value).
  • Use by default GS installation language.
  • Don't parse plugin tags in code tag.
  • Output in div, not tables.
• 0.4.zip 0.4.1.zip 0.4.2.zip 2010-10-10 to 2010-10-12
  • Encoding fixed : every language is supported.
  • Tags parameters controls recipients and options.
    • Add multiple recipients,
    • Display fields,
    • Hide fields,
    • Make fields required.
  • Page form ID : query associated to specific tag during process.
  • Multiple forms system.
  • Bugs fixes.
• 0.3.zip 2010-10-09
  • Define what fields to show, in what order.
  • Define what fields are required to send email.
  • New CAPTCHA field.
  • Setup system ready for tag parameters.
  • Dynamic error system, content validation and form generation.
  • Bugs fixes
• 0.2.zip 0.2.1.zip 0.2.2.zip 2010-10-08
  • multi-language support
  • w3c validation
  • Bugs fixes
• 0.1.zip 2010-10-08

I list here the new functionalities and changes expected before the 1.0. Fell free to tell me if you have a cool idea, or if you know how to realise one :

• Any forms actions possibles. The actual only integrated action is send_mail (send a mail with form answers to recipients), but anything is now possible (pool, newsletter, comments…).
• Hide every fields by using ? :

  fieldType?

• Multipart/alternative mail content : plain text and html.
• Fix : two unlocalized strings “Save settings” and “Default” in admin settings.
• Checklists can be defined as blacklist or whitelist.

• Remove paragraph wrapped around tag. See
• license.txt and documentation.txt.
• Make a better phone pattern.
• Multiple values allowed for fields treated as text (create selection list).
• Attachment field. Infos here, here or here. For multiples files types accepted (like by black/whitelist), MIME type management needed; or force one, like zip.
• Home-made anti-bot. What is better? An integrated literal captcha system (removing the directory p01contact/captcha) but fairly easy to circumvent, or current advanced captcha image?
• Set the page meta description if it's left empty to prevent GS page source scan. How to modify $metad?

• Mail subject encoding. See
• B/W lists bug. See
• Quote in email pattern (o'reily bug). See