NB: The generated cloud fall under the configuration set for the index tag cloud.

Features

• Allows registered users to send invitation emails for your site by either a list of emails they manually input or from their contacts ( basic http://openinviter.com integration )
• Ability to limit how many emails per time duration a user can send, and duplicate email invitation prevention.
• Links inviter to the invitee
• Basic referral system where users' have their own referral code that they can send to people and get credit for registration e.g yoursite.com/?rfc=816d9a0f96e55b39e420d35cc4224423 or any valid URL for your site with &rfc=816d9a0f96e55b39e420d35cc4224423 appended
• Compatiable with esclkm's SMTP plugin (PHPMailer) for SMTP support. Just install and configure the SMTP plugin if you want SMTP support and you're good to go.

Installation

1. Download, unzip and move 'invite' folder into your module directory
2. Install through the administration panel
3. Ensure the extension configurations are set to your preference
4. Edit invite/tpl/invite.tpl and invite/tpl/invite.contact.tpl to fit your theme
5. (optional) Add any of the tags ( found on GitHub ) to your templates

Credits

OpenInviter (http://openinviter.com)

You can find additional information and documentation at GitHub.

For the link to the user profile, use only the end of your profile link.

Example:

http://www.linkedin.com/in/brockburkholder/

This plugin can then be embedded by using the tag {PHP.linkedin.badge} globally on your website.

Note: Any width less than 300 will automatically be set to 300.

Example of how the badge will look:

Enjoy!

Features

• Add videos from YouTube or Vimeo.
• Shows N last videos on the index page. 
• Shows complete paginated listing on a standalone page.

Installation

1. Download the ZIP and unpack it somewhere.
2. Copy "video" to your Cotonti module folder.
3. Install it in Administration / Extensions.
4. Add {INDEX_VIDEO} to your index.tpl if needed.

Если вы решили продавать на своем сайте ссылки и для этого вам нужно установить php код какой-либо биржи ссылок то в данном уроке я покажу вам, как легко это сделать, что даже не нужно писать или устанавливать какие-либо плагины для этого. В уроке будет рассмотрено подключение трех бирж - sape, trusttrustlink, uniplacer. Сделать, кстати вы можете это как для одной из них, так и одновременно для всех - то есть держать свой сайт как площадку для продажи сразу в нескольких биржах.

Будет рассмотрен способ подключения кода бирж, который предусматривает продажу ссылок с их размещением в каком либо отведенном под такого вида ссылки месте на страницах вашего сайта работающего на CMS\CMF Cotonti, то есть продажа контекстных ссылок (то есть тех которые размещаются непосредственно в тексте страниц) предусматривает другой, более сложный способ установки кода биржи. Потому если вы решили продавать только контекстные ссылки, то к сожалению, вам данный урок, не подойдет - потому советую либо обратится за помощью к специалистам либо попросить помощи на нашем форуме, кстати данный урок был написан по мотивам вот этой темы на форуме потому дабы не множить подобные темы свой вопрос предлагаю задавать именно там.

А если действия описанные здесь вам покажутся слишком сложными то могу предложить воспользоваться поиском в хранилище расширений для Cotonti что бы найти там плагин, который сделает часть работы за вас. Например, там уже есть плагин для sape.

Требования

Для начала вы должны на сайте бирж(и) ссылок выполнить начальные действия, в которые входят:

• скачать архив с php кодом который даст возможность торговать ссылками у себя на сайте, будем считать что вы его уже скачали;
• распаковать(разархивировать) скачанный архив у себя на компьютере;
• загрузить (чаще всего делают это с помощью ftp) распакованную папку в корень своего сайта. Можно, конечно, не в корень, а в другую папку, но этот и другие частные случаи я в этом уроке рассматривать не буду, потому будем полагать что папка с php кодом от бирж(и) ссылок уже загружена в корень сайта;
• выставить на эту папку соответвующие права.

Теперь вам потребуется всего лишь любой текстовый редактор и знание идентификатора вашего сайта в системе биржи ссылок. Обычно он похож на вот такую строчку 2fc411fd6328b7f4f854d5c6589d (имя загруженной на сайт папки с кодом соответвует ему). В примерах ниже этот идентификатор указан как xxxxxxxx или yyyyyyyyy.

Так же в примерах я буду говорить о стандартном шаблоне\скине который идет в коробке с Cotonti который называется nemesis (для Cotonti Siena) или sed-light (для Cotonti Genoa).

Установка

Итак, приступим. В каждой из бирж, вам предлагают, разместить на страницах своего сайта определенный php код. Для каждой из систем он выглядит, примерно, так:

sape

     if (!defined('_SAPE_USER')){
        define('_SAPE_USER', 'xxxxxxxxxxxxxxxxxxxxxxxxxxx');
     }
     require_once(realpath($_SERVER['DOCUMENT_ROOT'].'/'._SAPE_USER.'/sape.php'));
     $sape = new SAPE_client();
     echo $sape->return_links($n);

trusttrustlink

define('TRUSTLINK_USER', 'yyyyyyyyyyyyyyyyyyyyyyyyyyyyyy');
require_once($_SERVER['DOCUMENT_ROOT'].'/'.TRUSTLINK_USER.'/trusttrustlink.php');
$o['charset'] = 'cp1251';//кодировка сайта
$trustlink = new TrustlinkClient($o);
unset($o);
echo $trustlink->build_links();

uniplacer

require_once($_SERVER['DOCUMENT_ROOT'].'/uniplacer_config.php');
require_once($_SERVER['DOCUMENT_ROOT'].'/'._UNIPLACE_USER_.'/uniplacer.php');

$Uniplacer = new Uniplacer(_UNIPLACE_USER_);
$Uniplacer->GetCode();
$links = $Uniplacer->GetLinks();

if($links)
{
      foreach($links as $link)
      {
        echo $link.'<br>';
      }
}

Что ж давайте откроем в текстовом редакторе файл /themes/nemesis/nemesis.php (если у вас Cotonti Genoa то /skins/sed-light/sed-light.php )

nemesis.php

<?php
/* ====================
[BEGIN_COT_THEME]
Name=Nemesis ver. 1.00
Schemes=default:Default
[END_COT_THEME]
==================== */

/**
 * Cotonti Model Theme
 *
 * @package Cotonti
 * @version 0.9.0
 * @author Cotonti Team
 * @copyright (c) Seditio.by 2010
 * @license BSD
 */

defined('COT_CODE') or die('Wrong URL');

//Вставлять код(ы) бирж(и) будем сюда

?>

sed-light.php

<?PHP
/* ====================
[BEGIN_SED]
Name=SED-Light
[END_SED]
==================== */

/**
 * Official skin
 *
 * @package Cotonti
 * @version 0.0.3
 * @author Xiode - XiodeStudios.Com http://www.xiodestudios.com , Cotonti Team
 * @copyright Copyright (c) Cotonti Team 2008-2009
 * @license BSD
 */

defined('SED_CODE') or die('Wrong URL');

// List of supported themes
$skin_themes = array('sed-light' => 'Light');

//Вставлять код(ы) бирж(и) будем сюда

?>

И вставим в него вышеуказанный код системы (или несколько кодов для разных систем) с небольшой поправкой, вот такой:

sape

if (!defined('_SAPE_USER'))
{
     define('_SAPE_USER', 'xxxxxxxxxxxxxxxxxxxxxxxxxxx');
}
require_once(realpath($_SERVER['DOCUMENT_ROOT'].'/'._SAPE_USER.'/sape.php'));
$o['charset'] = 'UTF-8';
$sape = new SAPE_client($o);
$sape_link_out = $sape->return_links();

trusttrustlink

define('TRUSTLINK_USER', 'yyyyyyyyyyyyyyyyyyyyyyyyyyyyyy'); 
require_once($_SERVER['DOCUMENT_ROOT'].'/'.TRUSTLINK_USER.'/trusttrustlink.php'); 
$o['charset'] = 'UTF-8';
$trustlink = new TrustlinkClient($o); 
unset($o); 
$trust_link_out = $trustlink->build_links();

uniplacer

require_once($_SERVER['DOCUMENT_ROOT'].'/uniplacer_config.php');
require_once($_SERVER['DOCUMENT_ROOT'].'/'._UNIPLACE_USER_.'/uniplacer.php'); 

$Uniplacer = new Uniplacer(_UNIPLACE_USER_);
$Uniplacer->GetCode();
$links = $Uniplacer->GetLinks();
  
 if($links)
{
    $uni_link_out = '';
    foreach($links as $link)
    {
      $uni_link_out .= $link.'<br>';
    }
}

Не забыв при этом заменить xxxx... или yyyy... на свой идентификатор. Сохраняем измененный файл nemesis.php (или sed-light.php соответственно) на сервер.

Теперь осталось выбрать место в шаблоне куда вы хотите вывести блок (обычно его размещают в подвале или в близи него потому подразумевая шаблон, речь идет о файле footer.tpl, но выводить можно в абсолютно любой другой шаблон) ссылок и вставить в это место - вот такую строчку:

sape

{PHP.sape_link_out}

trusttrustlink

{PHP.trust_link_out}

uniplacer

{PHP.uni_link_out}

Вот и все. Сохранив шаблон со вставленной строкой на сервере (на всякий случай еще можно в админ панели вашего cotonti сайта очистить Дисковый кэш) ваш сайт готов размещать ссылки от бирж(и).

• Provides a page with a list of questions and or questions and answers
• Users and guests can ask questions if they have the proper rights priviledge
• Manage and submit questions and answers in the admin panel
• Order questions by manually setting positions and, configuration options for default ordering of questions with the same position value
• Categories through structures (optional)​

Requirements

• Cotonti 9.13 or greater​

Installation

1. Copy the plugin to your Cotonti plugins folder
2. Install it in Administration / Extensions​

Categories

The use of categories is optional and can be setup through Administation / Structure / FAQ. All categories will be created with guest as read only and will need to be configured under the structure other wise. You can setup category specific templates through structures configurations as well.

Question submission to the default page ( no category ) will follow rights based on the module wide rights under this modules rights configuration.

Templates

A couple of useful variables for template condition blocks to alter you templates:

{PHP.faq_uses_categories}: a boolean that states whether the FAQ module is using categories
{PHP.faq_has_subcategories}: a boolean that states whether the current FAQ category has subcategories
{PHP.faq_has_questions}: a boolean that states whether the current FAQ category (even on the default page) has questions

You can find further documentation about available tags and blocks under the /docs directory included with this plugin or https://github.com/xerora/cot-faq

• Filters comment, forum and other spam with your choice of services (Akismet, Defensio, Typepad Anti-Spam). Comment and forum spam filtering is disabled by default. ( It is not recommended to use non-custom adapters for filtering if you use plugins that alter the extension you are filtering spam on. This could have unexpected results unless you know the specifics.)
• Provides an administration tool to manage items marked as spam.
• Allows you to filter spam in your extensions.
• ​Add your own section adapters to enable your extensions to use the spam moderation queue when filtering spam.

Installation

1. Decide which spam service you wish to use. Register at the service you choose to use and obtain an API key.​​​​ Akismet (http://akismet.com), Defensio (http://defensio.com), Typepad Anti-Spam (http://antispam.typepad.com)
2. Download, unpack and upload the spam_protection plugin folder to your plugin directory.
3. Install the plugin in the administration panel.
4. Go into the plugin's configurations in the admin panel and select your spam service and enter your API key.
5. Check to see that everything is configured to your preference.
6. The rest is up to your spam service and you can find all spam items caught in Administration -> Other -> Spam Protection​

Adding spam filtering to your extensions

An example of what it would look like to add spam filtering to your extension:

if(cot_plugin_active('spam_protection'))
{
    require_once cot_incfile('spam_protection', 'plug');
    $spam_data = array(
        'content' => $msg['text'],
        'authorname' => $usr['name'],
        'authoremail' => $usr['profile']['user_email'],
        'authorid' => $usr['id'],
        'authorip' => $usr['ip'],
        'date' => $sys['now'],
        'section' => 'guestbook',
        'data' => array(
            'guestbook' => $msg
        ), 
    );
    $spam_check_result = spam_protection_check($spam_data);
    if($spam_check_result['is_spam'])
    {
        // Item was returned as spam
        spam_protection_queue_add($spam_data); // Add to the moderation queue if you want. Not required.
    }
}

See https://github.com/xerora/cot-spam_protection#spam_protection_checkdata for more options to pass.

Go to https://github.com/xerora/cot-spam_protection or spam_protection/docs/README.htm for further documentation.

It's time to update your Cotonti instances to the latest and greatest 0.9.13 after several months since 0.9.12.1. Here is what we've got for you:

• CKEditor 4 is our new WYSIWYG editor by default.
• Page cloning feature.
• Draft pages are now easier to access.
• Cotonti language files are compatible with Transifex translation service. Discussion. Documentation.
• 11 small enhancements.
• 31 bug fixed.

See release notes for more information.

This release is dedicated to Leslie "Kingsley" Gonggryp, a well known member of LDU, Seditio and then Cotonti community who has recently passed away at the age of 35. You can join our condolences if you knew this guy. Let's continue the good work that he would appreciate.

Rest in peace, Kingsley.

• Basic CMF.
• Modules: Forums, Homepage, Installation and Upgrade, Page, Personal File Space, Private Messages, Polls, RSS, Users, View.
• Plugins: AJAX autocomplete, Banlist, BBcode, CKEditor, Cleaner, Comments, Contact, Forum statistics, Genoa compatibility, Hidden groups, Hit statistics, HTML Purifier, Contents Internationalization, IPSearch, markItUp!, MassMoveTopics, MathCaptcha, News, Start Ratings, Recent Items, Referers, Search, Statistics, Tags, Trashcan, URLEditor, User images, User by first letter, Who is online.
• Themes: Nemesis (development), SymiSun-03 (showcase).
• Icon packs: Tango.
• Locales: English, Russian.

Requirements

• PHP 5.2.3 or higher.
• MySQL 5.0.8 or higher.
• PHP extensions: GD, Hash, Mbstring, MySQL (mysqli, mysqlnd are suitable too), PCRE, PDO and PDO_MySQL, Sessions, Zlib.

What's new in Siena 0.9.13

• CKEditor 4 is our new WYSIWYG editor by default.
• Page cloning feature.
• Draft pages are now easier to access.
• Cotonti language files are compatible with Transifex translation service. Discussion. Documentation.
• 11 small enhancements.
• 31 bug fixed.

For more details please see this report.

See the list of new TPL tags here.

Installation

1. Copy datas/config-sample.php to datas/config.php and make it writable with CHMOD 666 or CHMOD 664 (depending on your hosting configuration).
2. Make the following folders and all their subfolders writable too with CHMOD 777 or CHMOD 775:

   	/datas/avatars
   	/datas/cache (and all its subfolders)
   	/datas/defaultav
   	/datas/extflds
   	/datas/photos
   	/datas/thumbs
   	/datas/users
   

3. Open your favorite browser and locate the installation script in it, e.g.: http://example.com/install.php
4. Follow the instruction on the screen up to the end of installation.

Update from 0.9.12.1

See updating instructions here.

For the list of files updated from 0.9.12.1 please see this diff and click "Files Changed".

Upgrade from Genoa

All upgrading procedures are described in this document.

Since v.0.9.13 Cotonti's language files are compatible with Transifex translation service and you can join our international translations teams there:

https://www.transifex.com/projects/p/cotonti/

Please read Transifex Help Pages to get started with the service. In this document we will only cover some topics specific to Cotonti.

Setting up the client tools

You can edit everything online but as Cotonti has plenty of language files, in many cases it would be more comfortable to copy files on your disk and edit them with your favorite editor. For such a case Transifex has a console Client tool.

Python interpreter is requried to use the client tools. If you don't have one, get it from http://python.org/download/. If you are using Windows, setting some shortcuts would be handy too.

Then you can install Transifex 'tx' tool as described in this section.

We also maintain a set of helper tools to manipulate language files easier in this repo: https://github.com/trustmaster/cotlang. They are also written in Python and run in command line.

Getting a working copy

Transifex works much like a git repository, so what you'd probably like to do first is to checkout yourself a working copy.

First, make a new folder, e.g. called 'cot-lang' and enter it in the command line:

cd cot-lang

Then initialize a Transifex repo in it:

tx init

After doing so, import repository configuration using this command:

tx set --auto-remote  https://www.transifex.com/projects/p/cotonti/

To map Transifex translations to Cotonti langfiles correctly, open '.tx/config' file that the previous command created for you and replace all of its contents with the actual Cotonti configuration for Transifex:

https://raw.github.com/trustmaster/cotlang/master/tx.config

Note for advanced users: contents of this file were generated by 'cotlangtx.py' tool given current Cotonti source tree as an argument, e.g.:

python cotlangtx.py ~/htdocs/cotonti

Now you can pull all the existing langfiles to your working copy:

tx pull -a

Done, you now have a source tree with only language files in it.

Making an existing locale compatible with Transifex

If you have an existing locale prior to 0.9.13, you should update it to be compatible with Transifex. There is a tool in cotlang package called 'cotlangfix.py' for it. It automates 95% of the fixes that need to be applied. Invoke it this way:

python cotlangfix.py path/to/source

It will print the results on screen. It will also print some strings that should be fixed manually. Below are some common cases.

Multiline entries

Transifex does not support strings that have line breaks in them. So you will have to merge them into a single line. To include line breaks though, you need to make sure the strings is in double quotes and then you can replace line breaks with \n. Also when changing from single quotes to double quotes, the '$' character needs to be escaped, so it becomes '\$'. For example,

$L['multiline_example'] = 'Here is
some %1$s entry
with multiple lines';

should become

$L['multiline_example'] = "Here is\nsome %1\$s entry\nwith multiple lines";

Arrays of options

You might also come across a few cases when values for some configuration option are localized like this:

$L['cfg_array_params'] = array(
	'Foo',
	'Bar'
);

or like this:

$L['cfg_array2_params'] = array(
	'foo' => 'Foo',
	'bar' => 'Bar'
);

They should become just a simple string too. So arrays are glued with ',' and associative arrays are glued this way: 'key1: value1, key2: value2'. So above examples become

$L['cfg_array_params'] = 'Foo, Bar';

and

$L['cfg_array2_params'] = 'foo: Foo, bar: Bar';

Loading an existing locale to Transifex

Before uploading files for a new locale, make sure this locale is already registered and listed with Cotonti project on Transifex. If it's not, log into Transifex and request adding a new language to Cotonti. We will accept your request and create a new locale shortly.

There's a tool in the cotlang set called 'cotlangcp.py' which simplifies copying language files here and there a lot. It copies just the language files and keeps the directory structure. You can use it to copy all language files from one folder to another:

python cotlangcp.py path/to/source path/to/destination

or you can even tell it to copy only language files for a specific locale, e.g. 'nl':

python cotlangcp.py path/to/source path/to/destination -l nl

So, if you have an existing localization e.g. for the 'nl' locale in path '~/htdocs/cotonti' and you want to copy it to '~/cot-lang' repo, you can do it using cotlangcp.py this way:

python cotlangcp.py ~/htdocs/cotonti ~/cot-lang -l nl

Now that you have copied new translation files, you can add and push them to the Transifex server:

tx push -t -l nl

Replace 'nl' in the above examples with your locale code.

At this point your locale should be already on server and you should see it filled in https://www.transifex.com/projects/p/cotonti/.

Updating locale files

Language files get updated from times to times. There may be new strings to be translated and some strings may be removed if they are not needed anymore. With Transifex you can monitor all these changes online and find strings to be translated. The online editing is pretty self-explaining and it has some advanced tools like Translation Memory and Automatic Translation via Google. But you might also want to keep your local copy of all locales up2date and use your favorite editor to translate files. No problem, let's use command line tools for it.

It is always good to pull fresh files from server before doing any changes:

tx pull

To pull everything, including new files, run this instead:

tx pull -a

Then you can edit files directly in the current source tree. Or you can copy updated files for your locale from other location, e.g.:

python cotlangcp.py ~/htdocs/cotonti ~/cot-lang -l nl

This command copies 'nl' locale files from ~/htdocs/cotonti folder to ~/cot-lang folder, assuming that ~/cot-lang is your Transifex repo copy and ~/htdocs/cotonti is where you keep the latest langfiles for 'nl' locale.

And vice versa, you can copy the latest files from the Transifex repo to your Cotonti site using the same cotlangcp.py tool:

python cotlangcp.py ~/cot-lang ~/htdocs/cotonti -l nl

When you are done with translating a portion of files in the Transifex repo copy, you can push your changes to the server:

tx push -t -l nl

Replace 'nl' with your locale code.

Tips and tricks

Pull before you push

This rule comes from git, but tx is not git so you need to be more careful. Normally you should do it in this order:

tx pull -a # get a fresh copy
cotlangcp.py # modify or copy updated files
tx push -t # push your updated translation

This pack includes formal and informal versions of the Dutch language.
Formal Dutch is used on more professional business type websites.

Installation: Copy & paste all the content from either the 'informal' or  'formal' folder in to your Cotonti root folder.

Nederlands (NL) Taalpakket voor Siena.

Dit pakket is inclusief formele en informele versies van de Nederlandse taal.
Formeel Nederlands wordt gebruikt voor professionele en zakelijke websites.

Installatie: Kopieër & plak de volledige inhoud van de 'informal' of 'formal' folder in je Cotonti root folder.

A responsive theme for Cotonti Siena, built with Twitter Bootstrap.

Installation

1. Place the folder 'blogster' in your Cotonti themes folder.
2. Enable the theme by setting: $cfg['defaulttheme'] = 'blogster'; in datas/config.php.

GitHub

The Blogster theme can be found on GitHub: https://github.com/Twiebie/cot-blogster
Feel free to fork it.

Support is offered on the github page(here). Report issues, feedback, and suggestions on the repository. Or even in the topic for the theme here. Feel free to tell me what you think.

A completely barebones Bootstrap theme for Cotonti Siena for you to build on!

Installation

1. Place the folder 'barebones' in your Cotonti themes folder.
2. Enable the theme by setting: $cfg['defaulttheme'] = 'barebones'; in datas/config.php.

GitHub

The barebones theme can be found on GitHub: https://github.com/Twiebie/cot-barebones
Feel free to fork it.

Note: this guide comes handy for theme developers as well. You can use any of these global variables as global template tags as well. Just remember the CoTemplate syntax. E.g. $usr['profile']['user_avatar'] in a template becomes {PHP.usr.profile.user_avatar}.

Current user's profile

$usr represents the current user and is the most popular global variable among the others.

You can distinct logged in users from guests by checking $usr['id']:

if ($usr['id'] > 0)
{
    // The user is logged in
}
else
{
    // It is a guest
}

Here is the list of standard keys this array has:

• $usr['id'] - unique number of the user in the database;
• $usr['name'] - username (login) of the user;
• $usr['maingrp'] - identifier of the main group the user belongs to, grp_id value of the groups table;
• $usr['ip'] - current user's IP address;
• $usr['lang'] - user's language preference. Another global $lang is a shortcut for this;
• $usr['theme'] - user's theme preference;
• $usr['scheme'] - user's color scheme preference;
• $usr['timezone'] - user's timezone offset in hours;
• $usr['timezonename'] - the name of the user's timezone;
• $usr['lastvisit'] - a timestamp for the last user activity on site;
• $usr['lastlog'] - a timestamp for the last time user logged in;
• $usr['level'] - user's main group's level value;
• $usr['profile'] - an array providing access to all the fields in the users table, explained below.

You can use $usr['profile'] to obtain raw values of user profile fields, including extra fields. It contains them prefixed with 'user_'. For instance, here are the standard ones:

• $usr['profile']['user_birthdate'] - user's birthdate in MySQL date format. You can display it using a combination of cot_date2stamp() and cot_date() functions;
• $usr['profile']['user_country'] - contains 2-char ISO country code of the user, if specified;
• $usr['profile']['user_email'] - user's email address;
• $usr['profile']['user_gender'] - one char for user's gender: 'M' for male, 'F' for female or 'U' for unknown;
• $usr['profile']['user_hideemail'] - true if the user prefers their email to stay private (default) or false if it can be displayed;
• $usr['profile']['user_logcount'] - the number of times a user has logged in;
• $usr['profile']['user_regdate'] - a timestamp for user registration date and time;
• $usr['profile']['user_text'] - user signature text.

So if you added an extrafield to users table that is called "first_name", then it can be accessed as $usr['profile']['user_first_name'] in the $usr global.

Current user's settings

There are a few globals containing current values of per-user display settings for current request:

• $lang - current language code;
• $theme - current theme name;
• $scheme - current color scheme name.

Configuration variables

All configuration variables are accessible via $cfg global. It has several levels of nesting:

• $cfg['option_name'] - one of the core settings;
• $cfg['module_name']['option_name'] - setting for a specific module;
• $cfg['plugin']['plugin_name']['option_name'] - plugin setting.

Extension environment

The $env array contains information about current extension (module or plugin) being executed and status information of the request:

• $env['type'] - 'module' for modules or 'plug' for plugins;
• $env['ext'] - extension code, e.g. 'forums';
• $env['location'] - a string containing textual description of user's location on site, such as 'Home page';
• $env['status'] - HTTP rersponse status, e.g. '200 OK';

System variables

There are temporary system variables that are used in several places and calculating them again and again would be a waste of resources.  Such variables may be contained in the global $sys array. Here are some of its common contents:

• $sys['now'] - an integer timestamp for the current time in UTC, same as calling time() function for UTC (Cotonti dates are stored in UTC and timezones are applied right before displaying them);
• $sys['site_id'] - some string unique for the site and used as its identifier (this data is public);
• $sys['parser'] - the code for the default parser plugin or the parser selected for the current data;
• $sys['xk'] - contains current value of CSRF protection token, used in forms;
• $sys['noindex'] - set this TRUE if current page should not be indexed by search engines;

The following variables are related to runtime detection of current URL and its parts:

• $sys['scheme'] - URL scheme, like 'http' or 'https';
• $sys['secure'] - a flag which is TRUE for HTTPS protocol being used;
• $sys['host'] - full host part of the URL, e.g. 'my.example.com';
• $sys['domain'] - 2nd level domain of the URL, such as 'example.com';
• $sys['port'] - the port if other than 80, containing comma, e.g. ':8080';
• $sys['site_uri'] - relative path of the site root on server with trailing slash. E.g. if you run Cotonti in 'example.com/cotonti/' then this path will be '/cotonti/';
• $sys['abs_url'] - absolute URL to the site root, e.g. 'http://my.example.com/cotonti/'. This is normally same as $cfg['mainurl'] with a forward slash, but on sites using multiple subdomains this would be different from $cfg['mainurl'] if accessing from subdomain;
• $sys['canonical_url'] - is used to get and set the canonical URL for the current page (used in html head);
• $sys['uri_curr'] - contains the current request URI part of the URL, e.g. '/cotonti/foo?bar=baz';

Output variables

These variables are used to make global tags to output them in multiple templates. They are collected in $out array. Here are some standard elements:

• $out['uri'] - the URI part of the current URL valid for HTML, e.g. '/index.php?foo=bar&boo=baz';
• $out['notices_array'] - user personal bar notifications array;
• $out['copyright'] - prints "Powered by Cotonti" link;
• $out['meta_contenttype'] - MIME type of the document, 'text/html' is default;
• $out['logstatus'] - displays user's login status as a string message;
• $out['userlist'] - displays the list of online users;
• $out['subtitle'] - sets the variable part of the head <title> tag. E.g. if you set it to 'Apples', the full title would look somewhat like 'Apples - Fruits - My Cool Garden Site';
• $out['meta_desc'] - sets meta description of the page;
• $out['meta_keywords'] - sets meta keywords of the page;
• $out['meta_lastmod'] - sets last modification date of the page;
• $out['adminpanel'] - displays the link to Administration panel for logged administrators;
• $out['loginout_url'] - a URL to log the current user out;
• $out['loginout'] - HTML link to log the current user out;
• $out['profile'] - HTML link to current user's profile settings;
• $out['guest_username'] - username form input for guests;
• $out['guest_password'] - user password input for guests;
• $out['guest_cookiettl'] - "remember me" checkbox for guests;
• $out['guest_register'] - a link to registration for guests;

Structure tree

The entire tree of site's categories, managed in Administration / Structure, is accessed via $structure global. It has the signature:

$structure['module_name']['category_code']

Where 'module_name' is the module code such as 'page' and 'category_code' is the code of the category such as 'articles'. The returned element is an associative array containing the keys:

• 'path' - the dot separated path of the codes from structure root, such as 'goods.electronics.blenders';
• 'tpath' - a path consisting of category titles instead, e.g. 'Goods - Electronics - Blenders';
• 'rpath' - raw path property of the category, e.g. 'goods.1.3';
• 'id' - integer identifier;
• 'title' - category title;
• 'desc' - category description';
• 'icon' - category icon path, if present;
• 'locked' - whether category accepts adding new items;
• 'count' - number of items contained.

Structure extra fields are also accessible via $structure. For example, if you have added an extrafield with code 'specialty', then it is accessible as

$structure['module_name']['category_code']['specialty']

Database and cache access

There are two other rather important global variables:

• $db - an instance of CotDB class used to query the database, see CotDB class reference and PDO for more information;
• $cache - an instance of Cache class, see Cache API documentation for more information.

Other global lists

There are some other global collections good to be mentioned for extension developers:

/**
 * Contains information about user groups, you'd better find yourself in system/common.php file
 */
$cot_groups = array();

/**
 * Registry for captcha functions
 */
$cot_captcha = array();

/**
 * Registry for hash functions
 */
$cot_hash_funcs = array('md5', 'sha1', 'sha256');

/**
 * Array of custom cot_import() filter callbacks
 */
$cot_import_filters = array();

/**
 * Custom e-mail send callbacks
 */
$cot_mail_senders = array();

/**
 * Custom parser functions registry
 */
$cot_parsers = array();

/**
 * Parameters to be automatically appended to all URLs if present
 */
$cot_url_appendix = array();

Demo: http://gokhan-yildiz.com/cot/index.php?e=leaguetables

HybridAuth is a self-hosted single sign on solution for PHP.

Features

• Quick login via social networks and services.
• Pre-filled fields on registration for new users.
• Linking multiple accounts to your profile: users will be able to login with social accounts after linking them to their profile on site.
• Auto-registration mode for sites which don't need standard registration and want to create accounts automatically from social networks.
• No extra JavaScripts and third-party requests on every page, this plugin has minimal footprint.

See the list of supported auth providers here.

Demo

The plugin is enabled on this site. If you are logged out, you can see social buttons in the "Sign-in" dropdown at the top of the page and on the login page. If you are logged in, you can link social accounts in your profile.

Requirements

• Cotonti >= 0.9.11
• PHP extensions: curl, json

Installation

1. Copy the plugin to your Cotonti plugins folder.
2. Install it in Administration / Extensions.
3. Edit plugins/hybridauth/conf/hybridauth.config.php according to HybridAuth User Guide.
4. Go to Administration / Configuration / HybridAuth and click Update.
5. Add {PHP|hybridauth_login} to your theme's login.tpl and {PHP|hybridauth_accounts} to your theme's users.profile.tpl. By default these widgets use templates called hybridauth.login.tpl and hybridauth.accounts.tpl accordingly, you can override them in your theme if you wish.

Configuration

This single sign-on solution is self-hosted, so you don't depend on any middleware providers but you have to obtain API keys for each service yourself. The basics are covered in HybridAuth User Guide and there are instructions for each provider in particular. For some providers you need to google how to register an app and get API keys yourself.

Every time you update hybridauth.config.php file you need to tell the plugin that there is a new provider available and it should create some database fields for it. To do so you should go to Administration / Configuration / HybridAuth and click Update. Configuration update forces hybridauth plugin to check for new providers and upgrade the database.

If you want to track user's real names in your database, it is recommended to add 2 extra fields to cot_users table in Administration / Other / Extra fields: firstname and lastname. They will be used to store names obtained from social profiles.

Templates

The plugin comes with two drop-in tags which help you to get going quickly: {PHP|hybridauth_login} and {PHP|hybridauth_accounts}. The first one renders large login buttons for your configured providers. The second one is used to link social accounts to user's profile.

You can customize those templates in your theme by copying hybridauth.login.tpl and hybridauth.accounts.tpl from plugin's tpl folder to your theme's plugins folder and editing them. You can also create more templates and pass them to these widgets as parameters, e.g. {PHP|hybridauth_login('hybridauth.my_login')} will use hybridauth.my_login.tpl as its template.

If you want to create direct login links for some providers, you can compose a URL this way: {PHP|cot_url('plug', 'e=hybridauth&a=login&provider=Provider_name')} where Provider_name is the name specified in hybridauth.config.php, such as Google or Facebook.

It is recommended to add a regular login form to your users.register.tpl for the following use-case: if the user has an account on your site and wants to log-in via provider but he has not linked the social account to his site account yet, then he needs to log in with his username and password and link the account in profile first.

{PHP|ilanguage('ru/Русский;en/English','selected_language_class')}

Where selected_language_class is a name of selected language class to mark current language. You can leave it empty to use "current" value (it is default).

Use TPL file ilanguage.tpl to make your one design of language links.

Also see forum topic. 

Users who have already upgraded to 0.9.12, please download the new version and replace updated files.

We are sorry about that. Please help us to improve Cotonti by submitting your bug reports to our issues page.

Changes in Siena 0.9.12:

• Page manipulation API for extension developers.
• SEO: title and meta description for pages now editable out of the box.
• Forums: markers for topics where a user has posted (#978), timeout for post editing (#1025).
• Added support for parsing and translation of name and notes of extensions. See #991.
• Added support for non-alphanumeric characters in passwords.
• CKEditor 3.6.5, markItUp! 1.1.13 and updated Star Ratings plugin
• Extended SQL devmode with backtrace.
• Lots of small enhancements.
• 38 bug fixes including some rather important ones.

Changes in Genoa 0.6.25:

• Fixed changing passwords in profile.
• Added experimental support for IPv6.

• Page manipulation API for extension developers.
• SEO: title and meta description for pages now editable out of the box.
• Forums: markers for topics where a user has posted (#978), timeout for post editing (#1025).
• Added support for parsing and translation of name and notes of extensions. See #991.
• Added support for non-alphanumeric characters in passwords.
• CKEditor 3.6.5, markItUp! 1.1.13 and updated Star Ratings plugin
• Extended SQL devmode with backtrace.
• Lots of small enhancements.
• 42 bug fixes including some rather important ones.

For more details please see this report and this one.

See the list of new TPL tags here.

Update from 0.9.11

See updating instructions here.

For the list of files updated from 0.9.11 please see this diff and click "Files Changed".

Package contents

• Basic CMF
• Standard modules: Admin, Forums, Lists and Pages, PFS, Plug, Private Messages, Polls, RSS, Users
• Standard plugins: Admin QuickView, Chili Highlighter, Cleaner, Comments Edit, Forums Stats, Index Polls, IPSearch, markItUp! editor, MassMoveTopics, News, Password Recovery, Recent Items, Search, Seditio Compatibility, Statistics, Tags, Who's Online
• Localizations: English, Russian

System Requirements

• Webserver (we tested on Apache and Nginx).
• MySQL >= 4.1
• PHP >= 5.1
• PHP extensions: gd, hash, mbstring, mysql, pcre, session

What's new in 0.6.25

• Fixed changing passwords in profile.
• Added experimental support for IPv6.

Installation

Just follow the INSTALL.txt instructions included in the package.

Updating from 0.6.24

1. Replace these files with updated files: see this diff page.

See also:

• Installation Guide
• Other language packs
• Source code

Plugin for Cotonti CMF. It allow to use tpl TAGs and function calls in menuslots.

Description

Cotonti have a predefined custom tags that admin can use in templates. Content of these tags called «menu slots» can be altered via administration web interface. As a default, menu slots allow to use only simple html text. With this extension you can use common TPL tags and function calls like in TPL files.

Features

• Parses text of menu slot as a tpl file
• Allow to use tags and Unified input field for time selections
• Allow to use function calls

Requirements

Works starting from Cotonti Siena v0.9.11.

Version info

Plugin must works out from the box. But as it relies on CoTemplate->compile() function it worsk only from Cotonti v0.9.11. Some of lang file strings or resource strings may be undefined in menuslots if they init after global hook.

How extension works

Runs on global hook. And parses all menu slots with CoTemplate->compile().

Install

• Unpack, copy files to plugins folder of your site.
• Install via Admin → Extensions menu (Administration panel → Extensions)

References

• «Slots and Tags» -- Page on GitHub

You can use it to generate last commented pages/polls/etc. list, most commented pages/polls/etc. list and so on.

As a Pagelist Plugin, Comlist is available via {PHP|comlist} callback from TPL file with the following settings:

$tpl - Template code (TPL file name without ".php" at the end)
$items - Number of items to show. 0 - all items
$order - Sorting order (SQL)
$condition - Custom selection filter (SQL)
$area - Custom comments areas list semicolon separated (both pages and polls by default)
$bwlist_cat - White and black lists of page categories. Mark categories with + or - to include them to the white or black list and separate with semicolon symbol. (+white_cat_1;...;+white_cat_N;-black_cat_1;...;-black_cat_Y;) Order does not matter.
$sub - Include subcategories in to the black and white lists of pages categorys TRUE/FALSE
$pagination - Pagination parameter name for the URL, e.g. 'pcm'. Make sure it does not conflict with other paginations. Leave it empty to turn off pagination

return string Parsed HTML

Examples:

{PHP|comlist('comlist', '10', 'com_maxdate DESC', '', 'page;polls', '', 'true')}

shows 10 last commented pages and polls in all pages categorys without pagination

{PHP|comlist('comlist', '5', 'com_maxdate DESC', '', 'page', '+news;-sport', 'TRUE', 'pcl')}

shows 5 last commented pages in 'news' categorys without pages in 'news/sport' category with pagination

{PHP|comlist('comlist', '5', 'com_count DESC', '', '', '', 'TRUE', 'pcl')}

shows 5 most commented resources (pages,polls, etc.) in all availible areas with pagination

{PHP|comlist('comlist', '5', 'com_count DESC', '', '', '+articles', 'FALSE')}

shows 5 most commented pages of the root articles category without pagination

You can turn on/turn off caching and caching for authorized users in administration panel.

Cache is sensitive to TPL code, location, language and page number.

Features

• Modern upload dialog based on jQuery File Upload.
• Multi-upload support.
• Easy integration via TPL callbacks.
• Built-in gallery based on Lightbox 2.
• File downloads are counted and provided with original file names.
• Configurable on-the-fly thumbnail generation.
• Special BBcodes to paste images into content regardless of parser.

Installation

1. Download the plugin and extract "attach2" folder into your Cotonti plugins folder.
2. Go to Administration / Extensions and install the Attachments plugin.
3. Enter plugin Configuration and set the proper defaults there.
4. Create the "Directory for files" on your host (by default it is "datas/attach") and make it writable for PHP (e.g. CHMOD 775 or CHMOD 777).

Basic usage

This section covers plugin usage basics with Pages module and minimal customizations involved. Similar actions can be applied to other content such as Forums, Comments, etc.

All examples are given for the basic theme, feel free to customize them for your needs.

Adding the attachment dialog

First we need to be able to attach files to pages. You would expect to do it while editing the page itself, but in this plugin it can be done while browsing the page. So let's add an "Attach files" button to the page management menu in "page.tpl":

It can be done by adding following code in your "page.tpl":

<!-- IF {PHP|cot_auth('plug', 'attach2', 'W')} -->
<li>{PAGE_ID|att_widget('page',$this,'attach2.link')}</li>
<!-- ENDIF -->

The link will only be displayed to users who have permission to attach files (controlled by Write access to Attachments plugin).

Using the attachment dialog

If you click the "Attach files" link, it opens attachment dialog:

The dialog is pretty straightforward. It lets you add one or several files at once, upload them, remove existing attachments, replace files and edit descriptions via AJAX. Drag & Drop rows to reorder them. Once you're done with changes, click the "Close" button and it will refresh the page to show you results.

Displaying all files at once

The quickest way to display all files attached to a page is by using att_display() widget in "page.tpl":

<!-- IF {PAGE_ID|att_count('page',$this)} > 0 -->
<div class="block">
	<h3>{PHP.L.att_attachments}</h3>
	{PAGE_ID|att_display('page',$this)}
</div>
<!-- ENDIF -->

It renders to something like this:

Adding a simple gallery

One of the most common tasks you'd like to complete is turning a page into an image gallery. You can add a simple gallery to "page.tpl" by pasting this code:

<!-- IF {PAGE_ID|att_count('page',$this,'images')} > 0 -->
<div class="block">
	<h3>{PHP.L.att_gallery}</h3>
	{PAGE_ID|att_gallery('page',$this)}
</div>
<!-- ENDIF -->

It embeds a Lightbox 2 gallery into a page:

Adding downloadable files block

Another common task is providing multiple files for downloading on a page. Use att_downloads() widget to embed it in "page.tpl":

<!-- IF {PAGE_ID|att_count('page',$this,'files')} > 0 -->
<div class="block">
	<h3>{PHP.L.att_downloads}</h3>
	{PAGE_ID|att_downloads('page',$this)}
</div>
<!-- ENDIF -->

A typical downloads block renders like this:

Advanced usage

Pasting basic widgets into pages is easy. But what if you need something custom or if you are curious about how they work? This section has the answers.

TPL callbacks and parameters

Attachments are not limited to just pages and the standard templates. You can easily attach files to other content and customize templates. Let's have a look at TPL callbacks this plugin provides and parameters they have.

att_widget()

/**
 * Generates a file upload/edit widget.
 * Use it as CoTemplate callback.
 * @param  string  $area    Target module/plugin code.
 * @param  integer $item    Target item id.
 * @param  string  $tpl     Template code
 * @return string           Rendered widget
 */
function att_widget($area, $item, $tpl = 'attach2.widget', $width = '100%', $height = '200')

This callback is used to add the attachments management dialog to the content object. In previous chapter we used it to add a "Attach files" link together with the dialog to pages by editing page.tpl. In fact this callback is more powerful, look at its parameters:

• $area - Defines the type of content the files are attached to. Usually conains module or plugin code, such as 'page', 'forums', 'comments', etc.
• $item - This parameter accepts an integer ID of the item the files are attached to. For example, it can be a page ID, forums post ID or comment ID. CoTemplate pipe operator and "$this" keyword are used to pass the appropriate tag to this parameter.
• $tpl - Contains template code for the widget to be rendered. E.g. if you pass it 'attach2.my_widget', it will try to find the template in "themes/your_theme/plugins/attach2.my_widget.tpl". Default (fallback) templates can be found in "plugins/attach2/tpl", use them as reference. 'attach2.widget' inserts the dialog as an iframe, whereas 'attach2.link' (see previous chapter) adds a link + popup dialog.
• $width - Width of the iframe, optional.
• $height - Height of the iframe, optional. 

For example, here is how you can add "Attach files" link for forum posts in "forums.posts.tpl" inside the FORUMS_POSTS_ROW block:

<!-- IF {FORUMS_POSTS_ROW_USERID} == {PHP.usr.id} -->
{FORUMS_POSTS_ROW_ID|att_widget('forums',$this,'attach2.link')}
<!-- ENDIF -->

att_display()

/**
 * Renders attached items on page
 * @param  string  $area Target module/plugin code
 * @param  integer $item Target item id
 * @param  string  $tpl  Template code
 * @param  string  $type Attachment type filter: 'files', 'images'. By default includes all attachments.
 * @return string        Rendered output
 */
function att_display($area, $item, $tpl = 'attach2.display', $type = 'all')

This callback is used to display files already attached to an item. It can render them all within one stream or include a certain type of files only. The paramters are similar with other callbacks:

• $area - Site area, same as for att_widget().
• $item - Item ID, same as for att_widget().
• $tpl - Template code, similar to att_widget(). The standard one for this widget is called 'attach2.display' and can be found in "plugins/attach2/tpl/attach2.display.tpl".
• $type - Use this parameter to display images only or files only.

Here is how you can display all files attached to a forums post in "forums.posts.tpl" inside the FORUMS_POSTS_ROW block:

{FORUMS_POSTS_ROW_ID|att_display('forums',$this)}

att_count()

/**
 * Returns number of attachments for a specific item.
 * @param  string  $area Target module/plugin code
 * @param  integer $item Target item id
 * @param  string  $type Attachment type filter: 'files', 'images'. By default includes all attachments.
 * @return integer       Number of attachments
 */
function att_count($area, $item, $type = 'all')

This callback returns the number of files attached to an item but it is often used to check whether there are files attached or not. Parameters are common:

• $area - Site area, same as for att_widget().
• $item - Item ID, same as for att_widget().
• $type - Use this parameter to count images only or files only.

Here is how you can use it to display attachments in "forums.posts.tpl" only if there are files attached:

<!-- IF {FORUMS_POSTS_ROW_ID|att_count('forums',$this)} > 0 -->
{FORUMS_POSTS_ROW_ID|att_display('forums',$this)}
<!-- ENDIF -->

att_gallery()

/**
 * Renders images only as a gallery.
 * @param  string  $area Target module/plugin code
 * @param  integer $item Target item id
 * @param  string  $tpl  Template code
 * @return string        Rendered output
 */
function att_gallery($area, $item, $tpl = 'attach2.gallery')

This is a shortcut to att_display() using 'attach2.gallery' as $tpl by default and $type set to 'images'. By default it shows you how to make a simple gallery using Lightbox 2, but you can make your own template and use any gallery script you wish. Parameters:

• $area - Site area, same as for att_widget().
• $item - Item ID, same as for att_widget().
• $tpl - Template code, see att_widget() for description.

E.g. let's imagine we've made our own template located in "themes/your_theme/plugins/attach2.fancy-gallery.tpl". Here's how we attach it to LIST_ROW block in "page.list.tpl":

{LIST_ROW_ID|att_gallery('page',$this,'attach2.fancy-gallery')}

att_downloads()

/**
 * Renders files only as downloads block.
 * @param  string  $area Target module/plugin code
 * @param  integer $item Target item id
 * @param  string  $tpl  Template code
 * @return string        Rendered output
 */
function att_downloads($area, $item, $tpl = 'attach2.downloads')

Similarly to att_gallery(), this is a shortcut to att_display() using 'attach2.downloads' as $tpl by default and $type set to 'files'. It is normally used to provide downloadable files section. Parameters:

• $area - Site area, same as for att_widget().
• $item - Item ID, same as for att_widget().
• $tpl - Template code, see att_widget() for description.

E.g. let's imagine we've made our own template located in "themes/your_theme/plugins/attach2.download-box.tpl". Here's how we attach it to a page in "page.tpl":

{PAGE_ID|att_downloads('page',$this,'attach2.download-box')}

att_thumb()

function att_thumb($id, $width = 0, $height = 0, $frame = '')

This callback is mostly used in attach2 templates themselves. It generates a thumbnail for an image attachment and returns an URL to that thumbnail. The parameters are:

• $id - Attachment ID.
• $width - Max. thumbnail width in pixels.
• $height - Max. thumbnail height in pixels.
• $frame - Framing mode. 'width' fits to the width and saves image ratio, 'height' fits to the height and saves image ratio. 'auto' (default) keeps the original ratio and fits the image into the given rectangle, 'crop' crops the image into the exact width/height given.

Thumbnails are generated on the fly and cached for futher use. Here is an example call from attach2.gallery.tpl:

<img src="http://www.cotonti.com/{ATTACH_ROW_ID|att_thumb($this,200,200,'crop')}" alt="{ATTACH_ROW_FILENAME}" />

att_get()

/**
 * Fetches a single attachment object for a given item.
 * @param  string  $area   Target module/plugin code.
 * @param  integer $item   Target item id.
 * @param  string  $column Empty string to return full row, one of the following to return a single value: 'id', 'user', 'path', 'filename', 'ext', 'img', 'size', 'title', 'count'
 * @param  string  $number Attachment number within item, or one of these values: 'first', 'rand' or 'last'. Defines which image is selected.
 * @return mixed           Scalar column value, entire row as array or NULL if no attachments found.
 */
function att_get($area, $item, $column = '', $mode = 'first')

This function is used to get data for a single attachment per item. Its main purpose is to create page covers in category lists. Parameters are:

• $area - Site area, same as for att_widget().
• $item - Item ID, same as for att_widget().
• $column - Name of the column to be returned by the function. If empty, the function returns an array with a row from the database. If one of the specified values is passed, the scalar column value is returned.
• $number - Affects the ordering. By default the first attachment is returned. You can change it to last with 'last' or to a random one with 'random'. You can also specify exact number of the attachment for the item, e.g. $number == 3 fetches the third image.

Here is an example of how this function can be used to turn a first attachment per page into clickable page cover thumbnails in "page.list.tpl":

<a href="http://www.cotonti.com/{LIST_ROW_ID|att_get('page',$this,'path')}" title="{LIST_ROW_ID|att_get('page',$this,'title')}">
    <img src="http://www.cotonti.com/{LIST_ROW_ID|att_get('page',$this)|att_thumb($this,240,160)}" alt="Foobar" />
</a>

As you see, this function can be used in conjunction with att_thumb() to generate thumbnails on the fly. The minimal Cotonti version for this feature to work is 0.9.12.

BBcodes for embedding into content

Images and thumbnails of the attachments can be pasted directly into content such as page_text, com_text, etc. However, you need to get the Attachment ID somehow first in order to paste it. The syntax of bbcode parameters is similar to URL query string. Available bbcodes are:

• [att_thumb] - inserts only a thumbnail <img/> tag.
• [att_image] - inserts a clickable image conisting of an <img/> thumbnail and a hyperlink to a full image.

Usage example:

[att_thumb?id=15]
[att_image?id=11&width=320&height=240&alt=Picture description&class=foo]

These bbcodes work regardless of the parser being used, including HTML and Markdown. If you want to disable them, just Pause the attach2.parser part of this plugin in Administration / Extensions / Attachments.

Cleanup tool

There's a tool in Administration / Other / Attachments. It is used to purge files attached to items which don't exist anymore. Sometimes items are removed but the code removing linked attachmehts is missing, so this tool may help.

Contact

Please use the Extensions forum to discuss plugin features and GitHub tracker to submit bug reports.

Credits

• Attachments 1.0 sponsored and tested by Skuola.net.
• Attachments 2.0 sponsored and tested by Seditio.by.
• jQuery File Upload by Sebastian Tschan.
• Lightbox 2 by Lokesh Dhakar and Dragonzap.

This module displays in-game achievements of your Cotonti website users utilizing Steam API and SteamCommunity.

Features

• Global game achievement stats for all users of your site.
• Multiple games support.
• Automatic synchronization with Steam.
• Global, weekly, recents stats display.
• Top board among your users.
• Steam achievements box for user profile.

Demo

See the module in action on FM Scout.

Installation

1. Copy steam module into your Cotonti modules folder.
2. Install the module in Administration / Extensions.
3. Proceed to configuration.

Configuration

1. Obtain your own Steam API Key and specify it in the module configuration.
2. Collect Steam appIDs for your games from SteamCommunity, e.g. if the game URL looks likehttp://steamcommunity.com/app/71270 then appID for the game is '71270'.
3. Collect SteamCommunity shortcuts for your games by visiting Global Achievements for those games, e.g. if the achievements URL looks like http://steamcommunity.com/stats/FM2012/achievements/ then SteamCommunityName for the game is 'FM2012'.
4. Go to module configuration in Administration / Extensions / Steam and fill collected information in game configuration. Don't forget to specify default appID.

Every time you change configuration and add/remove games, Steam module synchronizes its database with SteamCommunity and obtains properties and descriptions for those games.

Usage

This module installs a new extrafield for user profiles: SteamID. Add {USERS_PROFILE_STEAMID} it to your 'users.profile.tpl' file.

A user needs to specify his SteamID in profile for the module to start tracking their achievements. SteamID can be either a 64-bit SteamID (a big integer number) or a name part of Steam vanityURL. For example if your SteamCommmunity Profile URL looks likehttp://steamcommunity.com/profiles/12345678901234567/ then your SteamID is '12345678901234567'. If your SteamCommmunity Profile URL looks like http://steamcommunity.com/id/coolguy then your SteamID (vanityURL) is 'coolguy'.

Once a user has specified his SteamID, the module starts synchronizing their achievements every time he comes back to the site from absence.

Add {USERS_DETAILS_STEAMBOX} tag to 'users.details.tpl' file to display user achievements on their public profile page.

The global stats URL is something like http://example.com/steam/ or http://example.com/index.php?e=steam depending on your site's URL settings.

Customization

You can easily customize Steam module templates. In order to do so, copy files from 'modules/steam/tpl' folder to 'themes/your_theme/modules' folder and edit them there.

Credits

• This module uses PHP SteamAPI by Matt Ryder.
• This module was sponsored and tested by FM Scout community.

Plugin for Cotonti CMF. It adds «Share it» widget to pages of cite.

Description

Adds easy to use widget for social networks sharing to pages of your site. You can setup list of allowed services choosing from more than 20 social sites. Basicly all you need to enable it - is to install Extension. It will automatically adds widget to bottom of you pages and news. Also you can finetune placement of widget with manually adding {SOCIAL_SHARE} tag in tpl files.

Features

• Easy «one-click-install» (for basic use you don't need adding TPL tags)
• Highly configurable (widget style and list of services)
• I18n for widget based on users profile
• No external dependencies (working without jQuery use)
• Allowed to insert in any block of site with {PHP.social_share} tag

Requirements

Developed for Cotonti Siena (0.9.x branch). Worked with/or without jQuery enabled.

Demo page

Comming soon…

Version info

Current version 1.3 tested with:

• Cotonti Siena. Versions on 0.9.5 - 0.9.11 (actual).
• Skins: HTML Kickstart, Nemesis
• Admin skins: standard, bootstrap, priori

How extension works

Simply generates widget code based on your Extension settings (widget style and services list). Then auto insert widget code in bottom of pages or place specified with own tag in TPL files.

Install

• Unpack, copy files to root folder of your site.
• Install via Admin → Extensions menu (Administration panel → Extensions)

Comments

After install you must see widget block on bottom of articles and news pages (accordingly you had page and news modules installed). You can choose used services, language and widget style in Extension config menu (Administration panel → Extensions → Social share → Configuration).

If you want to change location of widget switch off «autoinsertion» mode in Extension config menu and manually add tag {SOCIAL_SHARE} in one of the templates:

• index.tpl
• news.tpl
• page.tpl
• page.list.tpl
• forum.posts.tpl

If you suppose to insert widget in other templates — use {PHP.social_share} tag. If you want to change default url, title or description of sharing page — use funciton style tag {PHP|social_share('url','title','tag')}.

References

• -- Source on GitHub

The Pagelist plugin is a universal solution that may be used to build widgets, virtual page lists and navigation. The plugin enables you to complete the following tasks:

• Output news feed without parent folder limitations with customized pagination, sorting and element (page) selection conditions.
• Build widgets of the following types: “Recent Additions”, “Top Pages”, “Random Pages” etc with customizable sorting and element selection conditions.
• Build navigation elements and any types of widgets based on the Page module.
• Add comments tags (optional).

The Pagelist plugin is essentially the pagelist function and is used via callbacks:

function pagelist(
    $tpl = 'pagelist',
    $items = 20,
    $order = 'page_date DESC',
    $condition = '',
    $cat = '',
    $blacklist = '',
    $whitelist = '',
    $sub = true,
    $pagination = 'pld',
    $noself = false
)

The callback parameters are as follows:

1. $tpl – template code (without extension, i.e. pagelist.recentitems)
2. $items – numberof elements to display (optional, i.e. 5)
3. $order – sorting order (optional, i.e. page_date DESC)
4. $condition –query condition (optional, i.e. page_some-extrafield = “1”)
5. $cat- parent folder (optional, i.e. blog)
6. $blacklist – categoryblacklist (optional, separated with semicolon, i.e. system;some-cat)
7. $whitelist – category whitelist (optional, separated with semicolon, i.e., hot;podcasts)
8. $sub – include subcategories (optiomal, i.e. true)
9. $pagination – pagination parameter name (optional, i.e. pld – make sure names do not conflict!)
10. $noself – exclude current page from list (optional, i.e. true)

Examples

The plugin uses the pagelist function to build own template in the specified placeholder. Due to this feature it enables website developer to build such blocks as blog feeds, recent items / top items widgets etc.

Build blog feed – selec t pages from all categories except system and archives, sort by date ASC and build pagination with 8 elements per page:

{PHP|pagelist('pagelist.blog','8','page_date DESC','','','system;archives','','TRUE')}

Build “Top-3” widget – 3 pages with non-zero hits sorted by hits DESC except pages from the system category:

{PHP|pagelist('pagelist.top','3','page_count DESC','page_count != "0"','','system','','')}

Build “About us” widget – 1 page with about alias from the system category:

{PHP|pagelist('pagelist.about','','','page_alias = "about"','system','','','')}

Template Structure

The model template has the following format:

<!-- BEGIN: MAIN -->
    <ul>
<!-- BEGIN: PAGE_ROW -->
        <li><a href="http://www.cotonti.com/{PAGE_ROW_URL}">{PAGE_ROW_TITLE}</a></li>
<!-- END: PAGE_ROW -->
    </ul>
 
<!-- IF {PAGE_TOP_PAGINATION} -->
    <div class="pagination">
        {PAGE_TOP_PAGEPREV} {PAGE_TOP_PAGINATION} {PAGE_TOP_PAGENEXT}
    </div>
<!-- ENDIF -->
 
<!-- END: MAIN -->

The PAGE_ROW_ regular block is used to output elements generated with the cot_generate_pagetags() function prefixed with PAGE_ROW_.

The following additional tags are available:

• {PAGE_ROW_NUM} (element number)
• {PAGE_ROW_ODDEVEN} (odd/even)
• {PAGE_ROW_RAW} (raw data from the db in the {PAGE_ROW_RAW.page_alias} format)

Once Comments plugin linkage is enabled in the config the following tags become available: PAGE_ROW_COMMENTS and PAGE_ROW_COMMENTS_COUNT.

Feel free to discuss the plugin at our forums: Pagelist Plugin

Plugin for Cotonti CMF. Designed for implement images «lazy loading».

Description

Extends pages with «lazy loading» functionality. It speeds up loading of page with a lot of images. With this Extension images on the page are loading only when they appears on screen. So it is not loaded until you scroll page for certain image had visible.

Features

• Delays loading of images outside a viewport
• Pages containing many images loads faster
• Two different library for your choice
• Control what images to make «lazy»
• Works in browsers with JS switched off
• Sample page included

Demo page

Sample page included in Extension pack. Just install and open plugin page (http://www.yoursite.com/lazyload/). View demo page without installation you can here.

Comments

Plugin works out from the box. For better results you may setup height and width attributes for you images. In that case content structure won't be rearranges during «lazy» load.

How extension works

Extension parses page content for img tags checks src attribute and substitute it with dump (transparent) image. When page loads script processes that img tags to check is it visible at this moment or not. As image become visible it loads as standard one.

Install

• Unpack, copy files to root folder of your site.
• Install via Admin → Extensions menu (Administration panel → Extensions)
• Checks setting in config (Administration panel → Extensions → LazyLoad → Configuration).

Comments

To see this Extension in action - open «LazyLoad» plugin page. There you can see sample page with multiple «lazyload» images.

References

• LazyLoad sources -- Actual code on GitHub

Plugin for Cotonti CMF. Designed as helper for Cotonti Extension (plugin) developers.

Description

Extends standard controls types for plugin configuration screen. There are no multiselect type control that can be used in Cotonti plugin configuration parameters. This extension (ExtDev_multiselect) extends standard input fields with additional functionality to select multiple values at once.

With this extension there are three new types of multiselect control.

Features

• Extending plugin configuration UI controls
• Three new types of multiselect control
• May be used as «supplementary» plugin without modification of current plugin code
• May be used as code snippet in your own plugins
• Easy to implement your own controls
• I18n

Demo page

Just install and switch to plugin configuration page.

Comments

Plugin works out from the box. You can see new controls on plugin configuration page.

How extension works

Hooks only on Extension's own configuration page (switch to global mode for tracking all Extensions in system). And preprocess plugin parameters to create multiselect controls on Extension config page.

There are added three new types of controls with multiple selection:

• simplelist - shows as usual text input field that allowed to select items and presents it as comma separated list.
• multiselect - shows as common selectbox element with multiple selection support
• checkboxlist - presented as list of checkboxes.

To enable new stye controls you must add specially named parameter of type text to your plugin setup file - plugname.setup.php (see extdev_multiselect.setup.php for examples).

Rules of naming config variable:

`varname_type`, 
     where `varname` - variable name allowed 
           `type` - type of control: simplelist, multiselect, checkboxlist

So to make a multiselect field you can write this code: VARNAME_multiselect=01:text:item1,item2,item3,item4,item5:item1,item3:«Multiselect» parameter

By default extension tracks controls only on own config (testing) page. If you want to enable multiselect controls in you plugin - enables Global mode.

Install

• Unpack, copy files to root folder of your site.
• Install via Admin → Extensions menu (Administration panel → Extensions)
• If you plan to use it as «supplementary» for your own plugins - select global mode in config (Administration panel → Extensions → ExtDev_multiselect → Configuration) and rename Config parameters in you plugin (see below).

Comments

To use this Extension as helper for your own plug you must add (or rename existing ones) parameters of type text. See rules for naming in How extension works section.

Compatibility

Tested with Cotonti Siena 0.9.5 ­- 0.9.11

References

• Cotonti.com -- Home of Cotonti CMF

Actual code

https://github.com/macik/cot-extdev_multiselect

(see the Demo page)

Plugin for Cotonti CMF. It replaces common date/time selection controls with unified pretty style jQueryUI controls.

Description

Current date/time selection controls are presented as several separated dropdown select box. Separate for year, month, day for date and hour, minutes for time. The plugin hides this controls and bring to user unified one input field for date and one field for time respectively. In addition this fields supplied with easy-to-use dropdown UI controls to selec date/time in one-click.

Features

The following markups are supported. The dependencies listed are required if you wish to run the library.

• Unified input field for date selections
• Unified input field for time selections
• User friendly pop-up UI control attached for fast selection of date time
• I18n for datepicker control (date format, month and day of weeks names)
• Using jQueryUI library
• jQueryUI ThemeRoller ready
• By default working in add/edit page, edit users, user profile.
• Optional mode to track any date/time controls and replace with new one regardless opened page or extension

Comments

Plugin must works out from the box. Tested on Nemesis, HTML Kickstart, SymiSun-03 theme and must work on most common themes or extension that uses standard date/time controls that relies on cot_selectbox_date function and $R['input_date*'] resource strings.

But if your use highly customized theme or your custom resource strings ($R['input_date*']) than extension may work uncorrectly.

How extension works

Old style controls simply hides with inline styles but still work as input fields for transfer parameters to server (while you save the data). New fancy style UI controls use jQuery UI library and dynamically added in pages in specially marked DIV containers.

Simply it maked by changing controls template in resource strings $R['input_date'] and $R['input_date_short'].

The default ui_date/time template for 'short' date is:

<div class="uidt_date">{$day} {$month} {$year}</div>
<div class="uidt_datetarget"></div> 

(See ui_datetime.rc.php for details.)

Most part of magic happened after page loads. JS script searches for elements with uidt_date and uidt_time class then parse it and linked with new controls added in elements with uidt_datetarget and uidt_timetarget class respectively.

By default extension tracks controls only on these pages: add/edit page, edit users, user profile. You can switch on global mode in settings for trace all controls on all pages, but it's not recommened because will load extension files all the time.

Install

• Unpack, copy files to root folder of your site.
• Install via Admin → Extensions menu (Administration panel → Extensions)
• If you already use jQueryUI in your project than setup path for jQueryUI library in ui_datetime settings .

Comments

After install you can see and test extension on Admin → Tools page (Administration panel → Extensions → UI date/time picker → Administration). You can Enable/Disable date and time controls separately via settings.

Compatibility

Tested with Cotonti Siena 0.9.5 ­- 0.9.11

Actual version can be found on GitHub: https://github.com/macik/cot_ui_datetime

Step 1. Prepare Remote Host

Hosting plans and tariffs differ, so here we give you a full freedom to:

• Setup the domain
• Create GIT or SVN repository

Step 2. Prepare Cotonti Package

First download the package at http://cotonti.com/download/ and unpack it into the local folder of choice.

Now we proceed to the primary web engine configuration. Copy the contents of sef-urls.htaccess into the still empty .htaccess and add the www / non-www redirect:

RewriteCond %{HTTP_HOST} ^www.cotonti.by$ [NC]
RewriteRule ^(.*)$ http://cotonti.by/$1 [L,R=301]

So as not to come back to .htaccess we add two more strings:

RewriteRule ^sitemap.xml?$  index.php?r=sitemap [QSA,NC,NE,L]
RewriteRule ^sitemap$  page.php?c=system&al=sitemap [QSA,NC,NE,L]

First one is required for the XML sitemap and the other one lets you create and use a system page with “sitemap” alias for a normal HTML sitemap.

The finalized .htaccess should look like this:

# Rewrite engine options
Options -Indexes
RewriteEngine On
 
# Server-relative path to Cotonti
# Replace it with your path if you run Cotonti in a subfolder
RewriteBase "/"
 
RewriteCond %{HTTP_HOST} ^www.cotonti.by$ [NC]
RewriteRule ^(.*)$ http://cotonti.by/$1 [L,R=301]
 
# Language selector
RewriteRule ^(en|ru|de|nl)/(.*) $2?l=$1 [QSA,NC,NE]
 
# Admin area and message are special scripts
RewriteRule ^admin/([a-z0-9]+) admin.php?m=$1 [QSA,NC,NE,L]
RewriteRule ^(admin|login|message)(/|\?|$) $1.php [QSA,NC,NE,L]
 
# System category has priority over /system folder
RewriteRule ^system/?$  index.php?rwr=system [QSA,NC,NE,L]
 
RewriteRule ^sitemap.xml?$  index.php?r=sitemap [QSA,NC,NE,L]
RewriteRule ^sitemap$  page.php?c=system&al=sitemap [QSA,NC,NE,L]
 
# All the rest goes through standard rewrite gateway
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^([^?]+) index.php?rwr=$1 [QSA,NC,NE,L]

One last thing left in the root folder is modification of robots.txt. We just add the host directive:

User-agent: *
Disallow: /datas
Disallow: /images
Disallow: /js
Disallow: /lang
Disallow: /lib
Disallow: /themes
Disallow: /system
Host: cotonti.by

If you’re planning to use the URL Editor plugin and modify a preset, copy it into datas/urltrans.dat. This would save your settings from accidental overwriting during the website engine upgrade.

This is also a good time to alter URL modification settings. If, in instance, you prefer to have trailing slashes in category URLs, you should change

page	c=*	{cot_url_catpath()}

to

page	c=*	{cot_url_catpath()}/

This way category and page URLs would look different for search engines.

Step 3. Prepare the Theme

Since we’re going to build a new the theme from scratch, we should use Nemesis theme as a model. Once it has been copied into a “themename” folder, rename the following files:

• nemesis.php
• nemesis.en.lang.php
• nemesis.rc.php
• nemesis.ru.lang.php

into

• themename.php
• themename.en.lang.php
• themename.rc.php
• themename.ru.lang.php

In the themename.php change the theme name from Nemesis to whatever name you got for it. I would strongly recommend not skipping theme cloning step so as to save it from accidental overwriting during future upgrades.

Step 4. Upload the Package

This is simple – deploy the package in a preferable way: repository or FTP client.

Step 5. Initial Setup

Any attempt to open Cotonti-powered website with missing config.php starts Cotonti installer. All operations here are pretty much understandable and normally do not cause any problems. All you have to do is provide MySQL server address, database name, user and password.

Next comes extensions selection. The choice here depends on the website type and overall requirements, in each case the list would be different. Couple of things shall be kept in mind:

• Any module and plugin can be paused, uninstalled and reinstalled at any time.
• Third party extensions can be added to the list, installed, uninstalled and removed at any time.
• There exist dependencies according to which some extensions require other extensions to run. Cotonti tracks such dependencies and lets you know if a required module or plugin is missing or not installed.

Last thing to do here is specify Superadmin login and password.

Once the installation routine is finished, there are three more operations to complete:

If GIT repository is used, exclusions specified in .gitignore shall be uploaded manually via FTP (i.e. urltrans.dat).

Caching should be disabled in config.php so that all changes at the development stage could be visualized immediately:

$cfg['cache'] = FALSE;			// Enable data caching
$cfg['cache_drv'] = '';			// Cache driver name to use on your server (if available)
								// Possible values: APC, eAccelerator, Memcache, Xcache
$cfg['xtpl_cache'] = FALSE;		// Enable XTemplate structure disk cache. Should be TRUE on production sites

Delete Install.php until next update.

The Summary

We have prepared Cotonti Siena package for the development stage. The next actions would differ depending on the website type and requirements. I’ll describe those later in the coming tutorials.

Installation

• Download and extract the plugin to your Cotonti plugins folder.
• Install the plugin in the administration panel.
• Enter your BF3Stats server ID in the plugins' configuration.
  Your server ID can be found by searching for your server on BF3Stats.
• To include the plugin on your index you can use the tag: {BF3S_INDEX}

As a PHP coder you might be used to $_GET, $_POST, $_COOKIE and such, but raw user input is not always good for your security and data integrity. That's why in Cotonti we import all data with cot_import() function:

function cot_import($name, $source, $filter, $maxlen = 0, $dieonerror = false, $buffer = false)

Parameters explained:

• $name - the name of the input in the HTML form.
• $source - source type of the data. Possible values are:
  • 'G' or 'GET' - for GET parameters;
  • 'P or 'POST' - for POST data;
  • 'C' or 'COOKIE' - to import data from cookies;
  • 'R' or 'REQUEST' - to import from PHP's $_REQUEST;
  • 'D' or 'DIRECT' - used to filter data passed in the $name argument;
  • 'PUT' - to import data from HTTP PUT request (for REST services);
  • 'DELETE' - to import data from HTTP DELETE request (for REST);
  • 'PATCH' - to import data from HTTP PATCH request (for REST).
• $filter - filter name against which the data is validated. Supported filters:
  • 'ALP' - passes digits, latin alphabet characters, dashes and underscores, useful for identifiers;
  • 'ARR' - imports an unfiltered array, each array item needs further validation after this import;
  • 'BOL' - import for booleans and checkboxes, returns TRUE if the input is checked or positive, FALSE if it is unchecked or zero and NULL if the input was not present in the form which sent the data;
  • 'HTM' - passes any text and trims whitespace from the beginning and ending of it, HTML is passed by this filter;
  • 'INT' - passes integer values only, a PHP (int) is returned or NULL if validation fails;
  • 'NOC' - no check/encoding, passes everything as is;
  • 'NUM' - passes numeric values only, PHP (float) is returned or NULL if validation fails;
  • 'PSW' - special filter for passwords, removes quotes , &, <, > from input and limits its length to 32 characters;
  • 'TXT' - filter accepting plain text except for HTML, in HTML some characters are replaced with HTML entities on import;
• $maxlen - limits max. lenght of the input, 0 means unlimited;
• $dieonerror - stop script execution with a fatal error if validation fails;
• $buffer - enables import buffer feature, used by Forms API.

The returned value is either a value with a filter applied or NULL if validation failed and a user must enter another value instead. Here are some example calls:

$title  = cot_import('title',  'P', 'TXT');
$code   = cot_import('code',   'P', 'ALP');
$count  = cot_import('count',  'P', 'INT');
$text   = cot_import('text',   'P', 'HTM');
$notify = cot_import('notify', 'P', 'BOL');

After you have imported the values, you might want to check them against some value (first of all NULL which is returned if the input was not present or validation failed against the filter) and emit an error message.

In a verbose form you could do it like this:

if (is_null($count))
{
	cot_error('Please enter a correct integer count', 'count');
}

cot_error() is a standard way to inform the system that something went wrong and to emit an error message that can be displayed later on. It has two parameters:

• $message - message text or language string code for the message to be displayed. E.g. if there is a language string $L['my_err_msg'] in connected language files, you can just pass 'my_err_msg' and localized message will be displayed to a user.
• $src - name of the input where wrong data was entered (optional), this is used to display the error message next to the input depending on template configuration.

There is actually a shorter (and recommended) way to combine "if" and "cot_error()" call in case of error:

cot_check(is_null($count), 'Please enter a correct integer count', 'count');

cot_check() function has parameters:

• $condition - a boolean expression which checks for an error, if it evaluates to TRUE, then the error will be triggered;
• $message - error message displayed if $condition is TRUE, same as in cot_error();
• $src - input name (optional) for the source of invalid data, same as in cot_error().

You should check whether any errors have been found in the system before proceeding to action such as saving data in database using cot_error_found() function:

if (!cot_error_found())
{
	// OK, we can save our data here because validation passed
}

This is it, now you know the basics of input validation in Cotonti.

Emitting messages and using other functions

Not all messages are error messages. You might as well inform the user that some operation ended successfully or warn him about something non-critical. Cotonti's messages API covers those cases too.

Here is the list of other Errors and Messages API functions:

• cot_check_messages() - mostly used by messages display function itself;
• cot_clear_messages() - normally used by Cotonti itself too;
• cot_die() - immediately terminates script execution if passed condition is true;
• cot_die_message() - outputs a standard error page and custom message if necessary;
• cot_diefatal() - terminates script execution and prints not-so-fancy error page (normally for developers);
• cot_display_messages() - use this function to display messages in your template (see next chapter);
• cot_get_message() - returns an array of raw message strings, normally used by messages display function;
• cot_implode_messages() - glues all messages into a single string;
• cot_message() - emits a generic non-error message.

Most of these functions are rather advanced and you will never have to use it in your modules or plugins. Let's have a look at the most common ones.

cot_message() function is similar to cot_error() but it is more generic. Here is the list of its parameters:

• $text - message text or language string code;
• $class - type or CSS class of the message, common values are 'error', 'success', warning', 'ok';
• $src - source input name where the message was caused, used to display the message next to it in some configurations.

Use this function to inform the user about operation status when handling forms and returning back to the normal page:

cot_check($some_input != '', 'some_err_msg', 'some_input');
if (!cot_error_found())
{
	// OK
	// Save the data...
	// ...
	// Emit the message
	cot_message('New item added successfully');
	// Return to the interface
	cot_redirect(cot_url('mymod', 'm=edit'));
}

Use cot_die() if something went wrong and you want to prevent further script execution:

if ($something_really_wrong)
{
	// How did the user get here?
	cot_die();
}

If that "something went wrong" is a standard situation that can be represented with a common HTTP error code and message, then use cot_die_message() function providing an error code:

if ($page_not_found)
{
	// Print a standard 404 page with a correct HTTP code
	cot_die_message(404);
}

You can also use cot_die_message() to handle non-standard errors and pass error page title and contents as 3rd and 4th arguments.

Displaying messages

Now you can validate data and emit messages but how do you display them? Normally you need to add just two lines to add errors and messages display to your module or plugin.

The first one is in your template, add a line that includes standard template for messages output:

{FILE "{PHP.cfg.themes_dir}/{PHP.cfg.defaulttheme}/warnings.tpl"}

And the second one should be put in your PHP code somewhere before the MAIN is parsed, e.g.:

cot_display_messages($t);

The above example assumes that:

• $t is the current XTemplate object;
• You have put the line connecting the standard warnings.tpl template in the outer block called MAIN.

This assumption may be incorrect, so here is the explanation of cot_display_messages() parameters:

• $tpl - XTemplate object where messages should be displayed;
• $block - full block name where messages template is included. For example, if you have put it in the RESULTS block contained within MAIN block, then the value of this argument should be 'MAIN.RESULTS'.

All together now

Now that you know the pieces of the puzzle, here is a complete picture of a real application for you:

// Connect language file with messages
require_once cot_langfile('mailout', 'plug');

if ($a == 'send' && $_SERVER['REQUEST_METHOD'] == 'POST')
{
	// Handle form submission
	$subject = cot_import('subject', 'P', 'TXT');
	$limit   = cot_import('limit',   'P', 'INT');
	$content = cot_import('content', 'P', 'HTM');

	// Input validation
	cot_check(empty($subject), 'mailout_err_subject_empty', 'subject');
	cot_check(empty($content), 'mailout_err_content_empty', 'content');
	cot_check($limit <= 0,     'mailout_err_invalid_limit', 'limit');

	if (!cot_error_found())
	{
		// Passed, save changes
		$sql_limit = $limit > 0 ? "LIMIT $limit" : '';
		$res = $db->query("SELECT user_name, user_email FROM $db_users $sql_limit");
		$counter = 0;
		foreach ($res->fetchAll() as $row)
		{
			$to = '"' . addslashes($row['user_name']) . '" <' . $row['user_email'] . '>';
			cot_mail($to, $subject, $content, '', false, null, true);
			$counter++;
		}
		// Emit success message
		cot_message("$counter messages sent.");
	}

	// Redirect back to the original form and show messages there
	cot_redirect(cot_url('admin', 'm=other&p=mailout', '', true));
}

// Display the user interface with the form
$t = new XTemplate(cot_tplfile('mailout.tools', 'plug'));

// Work with the template, assign tags and render blocks

// Don't forget to display the messages if they are present
cot_display_messages($t);

1. Install Fancybox (see how)
2. Install Pagemavatar
3. Configure picture upload:
   

   somecat|datas/photos|s_-200-200-crop|0||

4. Go for BBCodes list and add a new one name inline:
   

   \[inline=(\d+),(\d+),(.+?),(.+?)\]
   <a href="http://www.cotonti.com/datas/photos/page_$1_$2.jpg" class="fancybox" title="$3"><img src="http://www.cotonti.com/datas/photos/s_page_$1_$2.jpg" alt="$3" class="inline col$4" /></a>

5. Add / check styles for .colleft / .colright / .inline classes
6. In the page text insert pictures using following tags:
   

   [inline=23,1,This is alt text for the picture and title for the link,right]

   Parameters: page ID (you can use pictures uploaded for other pages too), picture number, alt text, float direction (left or right)

This is the first version of Turkish (TR) language pack for Cotonti Siena 0.9.11 (Beta)

Please contact me by PM if you have any suggestions or corrections of this translation.

Installation:
1. Unpack cotonti-0.9.11-turkish-language-files_109.zip
2. Upload folders: plugins, modules and lang to your /www folder (or any folder where you've installed Cotonti)
3. Open datas/config.php
4. Find

$cfg['defaultlang'] = 'en';

5.Replace

$cfg['defaultlang'] = 'tr';

Cotonti Siena 0.9.11 sürümü Türkçe dil dosyasını incelemektesiniz.

Herhangi bir problem veya çeviri hatası ile karşılaşırsanız lütfen özel mesaj yolu ile bana ulaşınız.

Kurulum:
1. İndirdiğiniz cotonti-0.9.11-turkish-language-files_109.zip adlı dosyayı sıkıştırılmış klasörden çıkarınız.
2. plugins, system ve lang klasörlerini olduğu gibi public_html veya www dizinine (ya da cotonti hangi dizinde kuruluysa) kopyalayınız.
3. datas/config.php dosyasını açın
4. Bul

$cfg['defaultlang'] = 'en';

5.Değiştir

$cfg['defaultlang'] = 'tr';

UYARI: Bu Türkçe dil dosyası Cotonti Siena 0.9.11 (Beta) sürümüne ait olup 0.6.X ve alt sürümlerini desteklememektedir. Cotonti'nin alt yapısının tamamiyle değişecek olması sebebiyle beta sürümü için dil dosyası hazırlanılmış olup, bir sonraki sürümler için yeni dil dosyaları bu dosyanın geliştirilmesiyle oluşturulacaktır. Eski sürümler için dil dosyasına ihtiyacı olanlar http://www.cotonti.com/locales/turkish-tr-language-pack-for-cotonti-065 sayfasından 0.6.5 için hazırlamış olduğum dil dosyasını indirerek eksiklikleri tamamlayabilir.

Bu sürüm'ün (0.9.11) altındaki herhangi bir Cotonti versiyonu için Türkçe Dil çalışması yapmayacağımı bildirir, bu yönde bir talep yapmamanızı da rica ederim.