SPIP-Contrib

The BREVES loop (news items)

2020-06-07T16:59:00Z

The BREVES loop, as its French name indicates, returns a list of news items.

The selection criteria

We will use one of the following criteria to indicate how we will select the elements:

- {tout}, i.e. “all”, will select all the news items available on the site.

- {id_breve} returns the news item identified by id_breve. Since the identifier of each news item is unique, this criterion will return one or zero records.

- {id_rubrique} returns all the news items available in the current section (rubrique), where “current” refers to the contextual environment of any surrounding loops.

- {id_mot} returns all the news items linked to the current keyword (inside a MOTS loop, for instance).

- {titre_mot=xxxx}, or {type_mot=yyyy} returns the news items linked to the keyword named “xxxx” or the keyword group named “yyyy”. Warning, you cannot use the criteria {titre_mot=xxxx} or{type_mot=yyyy} several times in the same loop.

- {id_groupe=zzzz} returns the news items linked to a given keyword group; it is the same technique {type_mot}, but since we're working with an identifier (a group number ), the syntax will be “cleaner”.

- {lang} selects the news items in the language requested in the page's address.

- {recherche} i.e. search, returns the news items matching the words entered in the search interface (search engine incorporated into SPIP).

Tags for this loop

- Tags retrieved from the database

The following tags represent the items retrieved from the database (as opposed to those that are “calculated” and are explained later). You can also use them as sorting criterion (usually: {par titre}, i.e. by title).

- #ID_BREVE returns the unique identifier of the news item.

- #TITRE returns the title of the news item.

- #DATE returns the publishing date of the news item.

- #TEXTE returns the text of the news item.

- #NOM_SITE returns the name of the site given as the reference for the news.

- #URL_SITE returns the URL of the site given as the reference for the news item.

- #ID_RUBRIQUE returns the unique identifier of the section (rubrique) in which this news item is located.

- #LANG returns the language of the news item. By default, this is the language of the sector in which the news item has been published.

- Tags calculated by SPIP

The following elements are calculated by SPIP. (They cannot be used as sorting criterion.)

- #NOTES returns the footnotes (calculated from the analysis of the text).

- #INTRODUCTION the first 600 characters of the text, where the typographical embellishments (bold, italic, ...) are removed.

- #URL_BREVE is the complete URL of the news item's page.

- #FORMULAIRE_FORUM creates and displays the forum interface of the news item.

- #PARAMETRES_FORUM creates the list of variables used by the form interface to post on the forum of the news item. For instance:

[Reply to this news item]

It is possible to pass this tag a parameter specifying the return address to link to after having posted the new message to the forums. For example: Reply to this news item will return the visitor to the same current page once the message has been validated.

- The logo

- #LOGO_BREVE displays the logo of the news item and the hovering logo if it is applicable.

The logo is inserted thus:

- #LOGO_BREVE_RUBRIQUE displays the logo of the news item, if it exists; if there is no logo, SPIP displays the logo of the section (rubrique).

CRITICAL security update : SPIP 3.2.4 & SPIP 3.1.10 released

L'équipe de SPIP-Contrib, Loiseau2nuit — 2019-04-08T15:05:00Z

A critical security flaw in SPIP was recently brought to our attention letting any identified visitors execute random code.

It affects versions SPIP 3.1 prior to 3.1.10 and versions SPIP 3.2 priori to 3.2.4 and every websites running those versions.
Versions 3.0 and prior are not affected by this issue

It's highly recommanded to perform an update as soon as possible.

SPIP team would like to thank Guillaume Fahrner who identified the flaw and alerted us.
If you can't perform the update right now, the safety_screen version 1.3.11 blocks any attempt to exploit that flaw.
https://www.spip.net/en_article4201.html

Updating the safety_screen is a patch and does not come as a replacement for any needed SPIP upgrade. You should perform it as soon as possible.

Complete announcement & details
https://blog.spip.net/834

Download SPIP
https://www.spip.net/en_download

Image Split

goony — 2019-03-01T07:00:00Z

This plugin lets you stack two images with a before/after effect. It uses the TwentyTwenty and Cropper JavaScript libraries.

1. Using the “split” model

The stack process is taken care of by the Jquery plugin TwentyTwenty. It is easy to use. All you have to do is using the model/template, transmitting the two images' id_document as parameters:

Here is the result for two images showing two different variants of a motorcycle model:

2. TwentyTwenty settings

The default parameters can be found in the plugin's configuration page:

If you want to know more about those options, I suggest you take a look at the official plugin documentation.

It is also possible to overwrite each option every time we use the “split” model, such as:

Here is the result:

Supported options:

Option	Values	Explanations
default_offset_pct	Float (0->1)	Slider position
orientation	vertical/horizontal	Slider orientation
no_overlay	true/false	Hide/shows labels
before_label	String	First image label's text
after_label	String	Second image label's text
move_slider_on_hover	true/false	Move the slider when hovering the images with the mouse
move_with_handle_only	true/false	Only move slider when clicking on it
click_to_move	true/false	Clicking on the images move the slider to that position

3. Using the “Cropper” tool

In order to optimize stacking process, it is important to use two images with the same proportions and, with a perfectly aligned content. To help with this, the plugin provides with a tool that crops and centers images you wish to stack. You will find a link to this tool near the button “add a document”:

This button will show a small form where you will be asked to provide the two images' id_document you wish to use.

Clicking “Adjust!”, you will be redirected to the “cropper” page. Follow the instructions on the top of the page. Once your two images are well stacked, you can click “Crop it”, which will redirect you to the article's editing page. You will find two new documents in the portfolio which are your two stacked images with proper dimensions and well centered (the original images are still there too):

Those two new documents are ready, to provide the model with.

Fixing release for branch 3.2 : SPIP 3.2.3

L'équipe de SPIP-Contrib — 2019-01-21T19:45:32Z

In last week end euphoria, the SPIP version 3.2.2, that was released on January 18^th, actually embedded the wrong version of the 'medias' plugin-dist (Many thanks to Christophe Imberti for his report).

We release today, January 21^st, a new fixing version SPIP 3.2.3 which brings every updates and good plugins-dist at the right place.

You should upgrade your website even if you already upgraded to SPIP 3.2.2

SPIP versions 3.0 & 3.1 are not concerned.

Download SPIP :
https://www.spip.net/en_download

Complete announcement & details:
https://blog.spip.net/831

Security & maintenance updates : new versions SPIP 3.2.2, 3.1.9 and 3.0.28

L'équipe de SPIP-Contrib — 2019-01-19T12:30:00Z

To start this new year 2019, we release maintenance versions of SPIP which also fix some security flaws.

The Safety Screen does NOT cover those flaws, so it is strongly recommended that you upgrade your websites.

Those new versions bring fixes to the bugs that were identified those last months :

6 issues for version 3.1
34 issues for version 3.2

Among others :

patched several XSS flaws and, a critical one letting writing authors accessing local documents. We warmly thank Guillaume Fahrner for his reports.
now supporting TLSv1.2 connections.
improved PHP 7.2 compatibility
optimized javascript compressor, which now respects already minified external librairies & bug fix on CSSTidy
repaired 'restore a version' function
updated SafeHTML librairie to support HTML5
updated getID librairie to version 1.9.16
added a _COUPER_SUITE constant to define proper caesura characters
re-designed log-in screens
images filters: JPGs are now progressive by default
new translations for Dutch & Japanese languages
...

Download SPIP

Full announcement & details

TimeCircles plugin for SPIP 3.1+

Loiseau2nuit — 2018-12-04T13:30:00Z

Adds simple & fully customizable jquery timers & countdowns to your SPIP website

Any Big Time deadline or Grand Opening coming soon ?
Tease your website audience about it with simple and fully custom designed jQuery timers & countdowns.

This plugin is a simple, yet efficient package version for SPIP, of Wim Barelds' TimeCircles jQuery plugin in last known version to date (v1.5.3)

How to install ?

Are you new here ? Discover SPIP !

You may install TimeCircles like any other plugin.

TimeCircles depends on nothing but jQuery 1.9.1+ on your website, thus making it “naturally” compatible starting SPIP 3.1.

Even if it's by far not a mandatory dependency for TimeCircles, this plugin has been thought and developed with plugin Agenda in mind, as I was working on a festival website (soon to be released). Promoters wanted to display a “Final countdown” on their home page, until the festival's grand opening (which date/time was recorded as a SPIP event, for lives running order publishing purposes).

How to use it

TimeCircles comes with 3 different timers & countdowns short-models that you can use either with, or without plugin 'Agenda' to generate & display kind of things like that on your website :

Whatever the content you're editing, just add one of the following short to generate the adjusted timer effect.

NOTE: TimeCircles does NOT store any data anywhere (maybe soon if the need is real).

DateCountDown

If you're using the plugin Agenda (not mandatory), this will work perfectly fine and sitewide, with any SPIP event. Example with event id n° 3 (here: New Year's Eve 2019)

DateCountDown

Also works fine with any date/time combination, manually set to the model, like :

Both examples at work here, on my testing website's homepage, within the 'website description' field's display :

Attention : date/time values should always be set with php-like values :
Y-m-d h:i:s (or H for hours 0-24) e.g.: 2019-01-01 00:00:00

In a SPIP event context (with plugin Agenda)

Placed anywhere in your event's description should do the trick too, based on the event's start date/time.

You also may apply TimeCircles to each and every single event created with 'Agenda' by simply adding the #MODELE{datecountdown} tag to your events templates/loops in /squelettes

CountDownTimer

Let's start a 15' min. timer here with (values here are expressed in seconds: 900 => 15 minutes)

CountDownTimer

PageOpenTimer

Or, how long have you been reading that page ?

PageOpenTimer

Modification and styles

TimeCircles is also shipped with a css/timecircles.css stylesheet and a JS file, to call the lib's functions: js/timecircles.js. Those 2 files are already included to your website's section with SPIP's tags #INSERT_HEAD & #INSERT_HEAD_CSS.

You can even get you some free own custom JS calls, ready to get copy/pasted into your /squelettes/js/timecircles.js by generating them on the author's website.

Note to templates developers: Since version 1.5.3.22 and following that method, timers are now made responsive by default, thanks to javascript function rebuild(), invoqued on the timer's container each time the browser's window is resized.

To keep it that way, this snippet should be kept in your own /squelettes/js/timecircles.js :

$(window).on('resize', function(){ $('.DateCountdown').TimeCircles().rebuild(); $('.CountDownTimer').TimeCircles().rebuild(); $('.PageOpenTimer').TimeCircles().rebuild(); });

Plugin is free for any use & open to common dev

It's source code is of course fully open and available, for download & mutual development, on SPIP-Zone's plugins repository (here).

Feel free to git clone / svn co the latest build and let's dance !

TO DO

Get this plugin to work in maintenance mode, on “under construction” pages (with plugin En travaux 2.0).
Make a generic config panel, following the JS generator from the author's website :

Config panel
Deal with insertion through plugin 'inserer_modele'
Finding a way to store duration's data for short models like &/or

“That's All, Folks !”

I/E config PLUS

Loiseau2nuit, Mist. GraphX, RealET — 2018-10-09T07:00:00Z

This plugin enhances I/E config with additional exports options for settings and objects.

Are you new here ? Discover SPIP !

Export/Import metas for new plugins:

Plugin SEO
GIS 4 (maps & cartography)
Modèles Facebook (Facebook widgets)
Autorité (Users' authority)
Paniers et commandes (E commerce Baskets & Orders)
Bank (online payment)

Export/import editorial objects

Export & import editorial selections (not the content !). Can be useful to easily import a template structure
Export & import single pages with plugin Pages uniques
Export & import advanced forms made with plugin Formidable
Export & import Keywords groups & Keywords (recently added, works but still a bit buggy & to be improved)

YAML V2 plugin for SPIP 3.*

Eric Lupinacci, Loiseau2nuit — 2018-06-04T13:36:00Z

Since it's first release, the plugin YAML did have a really few updates. Such stability is a proof of robustness, although a little cleaning and some evolution to the branch v2 will bring more flexibility and make the maintenance easier.

Versions and compliance

This second branch of the plugin is dedicated to SPIP 3.
Compliance with SPIP 2.* has been abandoned (suppressing the plugin.xml file) and, as a consequence, PHP 4 is not supported anymore either.
SPIP minimum compliance has been set to version 3.0.0, although you'll need to have a PHP version 5.3.3 or higher, to ensure the plugin can work properly.

By default, with no settings modification, plugin is to use the same library version the branch v1 already uses, except this one has been refreshed, as mentioned in a forthcoming section of this post.

Even if the API functions' prototype has changed (see next section), the code to call these functions v1 is still valid and will return the same results. Although you should progressively migrate toward v2-like calls (see dedicated section).

Plugin's API

Plugin YAML's API (inc/yaml.php file) contains 3 main functions which are already available in v1 and, a deprecated function which is kept for compliance purposes, with branch v1.

Those 3 main functions are :

yaml_encode($structure, $options = array()), which encodes a PHP data structure to a YAML string;
yaml_decode($input, $options = array()), which decodes a YAML string to a PHP data structure, often as an array;
yaml_decode_file($file, $options = array()), which decodes a YAML file to a PHP data structure. This function calls yaml_decode() after it extracted the file's content.

Compared to the API v1, functions' prototype has been modified, by adding in a systematic manner the optional $options argument, which aggregates all possible options in an array.
How to fully take advantage of it, is detailed in the section which describes the plugin's advanced usages.

Those functions remains independent from the used YAML library. According the context — _LIB_YAML constant and $options argument's 'library' index — each function named $fonction sets the library $library that will be used and, calls it's «homonym» function $library_$fonction().

Function yaml_charger_inclusions() stands deprecated in this new branch. Even if it remains possible to use it, to recursively integer decoded YAML, out of initial YAML file's known includes, you should only use yaml_decode_file() function, providing the options with includes' loading.

Additionally, the decoder_yaml() filter that encapsulates yaml_decode_file() and yaml_to_array() for iterators, has been kept. If decoder_yaml() filter fully takes advantage of optional $options argument, this is not the case with yaml_to_array() which, structurally, can only read the YAML string as an argument.

YAML libraries

The plugin still offers branch v1's library: Spyc and Symfony/yaml v1 but, also lets you use latest Symfony v4's version of the YAML component, with extension PECL, which encapsulates the C libYAML library.

Versions of Spyc and Symfony/yaml v1 has been updated and, improvements brought by SPIP to Symfony/yaml v1 have been reported.

Each library require a minimal PHP version and implement a proper sub-set of YAML 1.0, 1.1 or 1.2 specifications. Following table sums those constraints up and provides with the actual version — which is likely to evolve — of each library included in the YAML plugin (initial version 2.0.0).

Library	Alias*	Version	PHP mini	YAML	Comments
Spyc	spyc	0.6.2	5.3.1	1.0	GitHub repository
Symfony/yaml v1	sfyaml	1.0.6	5.2.4	1.2	GitHub repository, archivé
Symfony/yaml v4	symfony	4.2	7.1.3	1.2	GitHub repository
libYAML	libyaml	1.3.1	5.3.3	1.1	PECL page and libYAML GitHub repository
libYAML	libyaml	2.0.2	7.0.0	1.1	PECL page and libYAML GitHub repository

(*) : The alias is used to pick out the library for the API : $options['library']'s value or, _LIB_YAML constant.

On performance's side, shall we point out:

C libYAML library is by far the best for performance, with benchmarks 6 to 15 times faster than others libraries.
Symfony/yaml v1 and Spyc libraries have quite similar performances, almost correct:
Symfony/yaml v4 is nearly 2 times slower than v1.

Besides, the YAML specifications sub-set, offered by each library, varies a lot. For SPIP's needs, mostly linked to some configuration parameters, every library are equivalent, whatever which YAML specifications version is supported. To get an insight on the different implementations, a serie of test files (demo/$library.yaml) is furnished with the plugin. Those files come from the native Spyc library's test file. For the other libraries, it was adapted, commenting out unsupported cases.

Shall we also point out that two important YAML features are not implemented in the plugin, because they are not available with all libraries:

the YAML document's 3 starting dashes “---” and 3 final dots “...”
and as a consequence, the capability to encapsulate multi YAML documents into a single YAML file: a YAML file must then contain only one single YAML document.

By default, to ensure compliance with branch v1, YAML plugin uses the Symfony/yaml v1 library (alias sfyaml), which still remains a good choice.

Plugin's maintenance

Besides the bug fixed, the plugin's maintenance matches it's libraries one.

The default library, Symfony/yaml v1 isn't maintained anymore. It won't evolve but still works with current YAML specifications and usages. It's made of 4 files, located in the sfyaml/ plugin's directory.

libYAML library is distributed as a PECL extension, so you can install it on Apache server. Nothing to do plugin's side. You should prefer that one if you can install it.

The two others libraries, Spyc and Symfony/yaml v4, are both incorporated in the plugin with Composer. We'll find them into the vendor/ directory. It's possible to upgrade them or, go back to any prior version, using the composer.json file located in the plugin's root directory and, activating the composer update command.

API: advanced usages

Understanding the various options

Basic usage of the API's functions has not been modified. Although, adding an $options argument as second parameter for each API's function makes the plugin more flexible and more accurate to work with. The available options are summarized, function by function, in the following table. An “x” indicates if the option is available for any given library.

Option	Explanation	sfyaml	symfony	spyc	libyaml
Any function
library	Specifies the lib. to be used, irrespective of the _LIB_YAML constant	x	x	x	x
yaml_decode() and yaml_decode_file()
include	Treat YAML files includes (true) or not (false, by default)	x	x	x	x
show_error	Display errors (true) or not (false, by default)	x	x
flags	Combine bitwise PARSE_* flags supported by the library, 0 by default		x
yaml_encode()
indent	Number of spaces for each indentation level, 2 by default	x	x	x	x
inline	Level from which YAML presentation becomes inline, 3 by default	x	x
flags	Combine bitwise DUMP_* flags supported by the library, 0 by default		x

Decode includes

Since YAML plugin v1, it's possible to make includes in a YAML file, like this:

- 'inclure:relative_path/my_file.yaml'

This feature prevents you from duplicating lists of identical blocks in several YAML files, what the specification basically does not allow, This includes processing being quite heavy (recursively browsing the decoded data structure), it's not applied by default while decoding the YAML but, explicitly requested.

With Bonux v1, that feature is performed by calling the yaml_charger_inclusions() API function, on the result of a decoded YAML file or string:

$configuration = yaml_charger_inclusions(yaml_decode_file($fichier));

With new version 2, we should now perform that processing another way, without calling the yaml_charger_inclusions() function — which then, stands deprecated — but by using a decode option, as shown below:

$configuration = yaml_decode_file($fichier, array('inclure' => true));

Force a library while calling

If the library used by default (_LIB_YAML constant) is not suitable for any specific call, it's possible to force for that call, another library:

$configuration = yaml_decode_file($fichier, array('library' => 'libyaml'));

Displaying errors

By default, in SPIP Bonux v2, YAML decoding errors are not displayed anymore. To force their display, you'll have to use 'show_error' option, as following :

$configuration = yaml_decode_file($fichier, array('show_error' => true));

What's next ?

Eventually coming up with a more evolved determination logic to choose the library by default ?
Deprecating certain libraries to keep only libYAML, if it's installed or, one of those installed by Composer ?

3,2,1... Ignition ! Maintenance upgrades for SPIP 3.2.1, SPIP 3.1.8 & SPIP 3.0.27 are out !

L'équipe de SPIP-Contrib, Loiseau2nuit — 2018-03-16T14:37:00Z

Few months after SPIP 3.2 was released, time has come to provide you with some maintenance & security updates for SPIP versions 3.0, 3.1 & 3.2.
It's highly recommanded that you upgrade your installations if you're running one of them, because they come with security fixes & improvements.

Bug fixes

Those new versions come with latest months' bug fixes:

2 tickets for version 3.0
12 tickets for version 3.1
19 tickets for version 3.2

Among many bug fixed, let's highlight :

security flaw fixed on valider_xml function (thanks to Sammy Forgit's reporting)
bug fixed on publication dates
bug fixed on plugins' database installation, specifically when the table prefix begins with a number.
some UI fixes for the Admin Area (now displays total files' weight with the number of documents, in the 'mediatheque' tabs, etc...)
bug fixed on referrer calculation in the Admin Area's statistics module
improved bots detection, in order to exclude them from statistics module datas.
bug fixed on opcode
SNI bug fixed, when using SPIP behind a Proxy server
.../...

security screen

For webmasters who CAN'T upgrade their SPIPs to the latest revision, it's important, at least, to install/upgrarde their config/ecran_securite.php to latest version 1.3.6, in order to correct the security flaw.
See https://www.spip.net/en_article4201.html?var_lang=en for more info.

spip_loader

spip_loader also has its bunch of modifications, in order to simplify the upgrade process for SPIP.

Commplete announcement & details here :

https://blog.spip.net/812

And of course, all info for upgrading SPIP are available on the official documentation : https://www.spip.net/en_article2154.html

Originally posted in French by L'équipe de SPIP-Contrib
Translated to English by Loiseau2nuit

Bingo for Friday the 13^th, SPIP 3.2 is available!

Jacques — 2017-10-14T07:04:41Z

Following the Toulouse meeting in May, SPIP 3.2 was in the starting blocks.Many websites use it daily on-line, now it's time to offer it to you!

SPIP 3.2 is an improved version of SPIP 3.1, which includes:
- * an update of the embedded JavaScript libraries
- * better ergonomics of the private area
- * security patches on XSS attacks
- * many improvements.

As good news never arrive alone, for this major version release, SPIP is adorned with a new logo and the site SPIP.net adopts a new design.

Many thanks to all who participated.

As usual, do not hesitate to make feedbacks or propose improvements :)

PS For those who remain with SPIP 3.1 and who do not wish to upgrade to SPIP 3.2, we also propose a new SPIP 3.1.7

— The team

Complete news and details
https://blog.spip.net/807

Redesigning SPIP graphical identity

Jordan Zuchiatti, nicod_, YannX — 2017-07-10T12:35:00Z

At Toulouse SPIP Party 2017, a new contributor came to show his work on a complete rebranding for the SPIP logo.
Beyond the logo redesign, it is a brand new graphic identity for SPIP that Jordan offers us.

Here is a transcript of his speech:

« SPIP's graphic identity is felt as aging. Its logo suffers some weaknesses and, websites in its “galaxy” [1] could totally use a re-branding & design refreshing.

As a regular SPIP user — which I use to work with on 31mille web agency's projects, as an artistic director — here is my contribution to re-think and modernize SPIP's branding.

Redesigning graphic identity should first ensure all SPIP users about the project and, the dynamism the Community has been carrying around on for 16 years. Default achievement being at least, showcasing a modern front-office to new comers.

With this upgrade, like we do for a software, improving graphic identity brings to any structured environment more flexibility, making it perfectly scalable to new medias and devices.

Working concept relies on a synthesis between SPIP's power animal, the flying squirrel, and the letter « S ».

For typography purposes, we draw a character that keeps the dynamism brought by a sans-serif, emphasized by italic font and, by adding discrete serifs to it. Part of actual logo's typography is kept in the «p» curve.

A detachment in second “p”'s eye, reminds of the power animal, symbolizing the squirrel's hear. Then appears the “squirrel-shaped word”, with its head, body, and a feathery tail.

A logo's strength stands in its rhythm. Feathery tail's lower curve is repeated across the two letters “p”. This redundancy brings the needed dynamism and, empowers the global consistency, meaning to identify and memorize the feathery tail symbol..

The feathery tail may totally be used alone and then become SPIP's graphic identifier.

Modernizing a graphic identity also involves a color refresh. Purple, historical 'legacy' color, now tends to a more actual, brighter & electric hue, so that you clearly can't miss, but recognize SPIP's Identity.

Using both colors remains however possible, depending on the uses, website's topics and/or devices ...

Once the symbol is set, any pictural tweaking can be used for larger displays. Like this one, from a graphic code in reference to Mozilla Firefox:

Using the feathery tail as a graphic symbol being set, identifying SPIP is made possible as soon as one sees the particular curve of the tail.
Shaped by a rounded background, symbol keeps being perfectly usable in small sized displays, like a favicon.

And now this is a design refresh proposal for SPIP's galaxy websites:

This is the graphic identity I imagined for SPIP's community, to be its first spokes person and amplifier.

Jordan Zucchiatti »

The initial point being agreed on among the Community, this new logo and proposal for a new graphic identity were warmly welcomed by the party attendees.

Sources for the logo and variations (favicon, relief, site title and purple declination) are available on Spip-Zone SVN repository [2], in SVG and PNG formats :
https://zone.spip.org/trac/spip-zone/browser/_graphismes_/logos/spip/spip_2017

Update on 07/31/2017 :

Jordan's mock up has been packaged into a new scalable & skin-able template-plugin Galactic.
A first version was made for the developper's documentation website redesign : https://programmer.spip.net/

Templates and their first skin are free to download on Spip-Zone SVN repository:
https://zone.spip.org/trac/spip-zone/changeset/105541

Update on December 11^th 2018 :

By the time that post was translated & published in english, the 'Galactic' templates are already nicely at work on following SPIP Galaxy's websites :

official SPIP website
official SPIP community forums
SPIP plugins & templates' developers guide
SPIP Contrib (This exact one ! Yeah!)

[1] Galaxy made of every official website dedicated to SPIP, like this particular one.

[2] SPIP 's community contributions repository

CRITICAL security update: SPIP 3.1.6 and SPIP 3.2 Beta 3

L'équipe de SPIP-Contrib — 2017-06-15T07:57:02Z

A CRITICAL flaw was discovered recently in SPIP, allowing the execution of arbitrary code.

It affects SPIP 3.1.x and 3.2 versions (alpha & beta), and impacts all websites using these versions.
SPIP 3.0.x and earlier versions are not affected by this issue.

It is imperative to update your SPIP website as soon as possible.

In the meantime, the security screen version 1.3.2 will block possible exploitations of the vulnerability. Updating the security screen remains a transitional measure that should not prevent you from updating SPIP as soon as possible.

The team thanks Emeric Boit and ANSSI for identifying and reporting the issue.

— The team

The following updates are available:

Version 3.1.6
https://files.spip.net/spip/archives/SPIP-v3.1.6.zip

Version 3.2 Beta 3
For people who want to test the future version of SPIP , we're taking the opportunity to release SPIP 3.2 Beta 3.
https://files.spip.net/spip/archives/SPIP-vtrois.2.0-beta-3.zip

Warning: this is a beta version, it can still contain bugs.
Do not update to this version on a production website without knowing what you're doing.

The security screen

People unable to update should install version 1.3.2 of the security screen.
https://www.spip.net/fr_article4200.html

Update using spip_loader

You can also upgrade by downloading the latest version of spip_loader (version 2.5.9) which will install SPIP 3.1 by default.
https://www.spip.net/spip-dev/INSTALL/spip_loader.php

Summary of SPIP versions

Branch	Version	Status
SPIP 3.1	SPIP 3.1.6	Stable
SPIP 3.0	SPIP 3.0.26	Maintained
SPIP 2.1	SPIP 2.1.30	Maintained (security updates only)

SPIP 2.0 and earlier versions are no longer supported. It is strongly recommended that you upgrade to a higher version to avoid security issues.

How to be kept informed about these announcements?

It's simple, sign up on the mailing list http://listes.rezo.net/mailman/listinfo/spip-en .

And follow us on social networks:

Seenthis: https://seenthis.net/people/spip
Twitter: https://twitter.com/spip
Facebook: https://www.facebook.com/spip.net
Mamot: https://mamot.fr/@spip

A question, in need of help?

In case of problems or difficulties, go to https://forum.spip.net
We remind you that to report a flaw, just send an email to spip-team@rezo.net

Go diagrams with maxiGos.

Robert Sebille — 2017-05-20T13:25:45Z

Maxigos is a plugin for SPIP which allows the use of the main features of maxiGos, “a set of tools to insert games, problems and go diagrams saved in sgf format in a web page.”

The plugin works on basis of a model. The sgf code can be written as a parameter of the model or contained in an sgf (Smart Game Format) file.

The plugin was tested under SPIP 3.1, but there is no reason it should not work under SPIP 3.0, or 2.1 and 2.0. You have to test. Feedbacks from users are welcome.

Installation.

As any spip plugin

Authorization of SGF documents

SPIP has “forgotten”;) to allow .sgf extension files and compresses them as zip files. They have to be authorized directly in the database, by adding a row in the “spip_type_documents” table. The plugin performs this operation on activation.

Third party.

The plugin embeds its own version of maxiGos, v6.64 (standalone players only + editor + language files), licensed BSD.

Rules for sgf format.

If you want to write sgf directly into the content, refer to the spécifications. But, most of the time, you will probably prefer to use sgf files.

Model parameters

formatting
- langue=[langue] where [langue] can take the values : fr (for French, default), en (for English), ja (for Japanese), zh (for Chinese), zh-tw (for Chinese-taiwan)
- style=[style] where [style] can take the values: classic (default), neo (for neo-classic), tatami, minimal (for minimalist), cameleon, [which are multitype values] or fm, kifu, tiger [which are monotype values]
- type=[type] where [type] can take the values: basic (default), comment, diagram, game, problem, tree [which are multistyle values], edit, lesson [which are monostyle values]

For the meaning of the style and type parameters, refer to the examples on this page http://jeudego.org/maxiGos/_maxigos/_doc/_en/download.php from the maxiGos website under the heading “Download stand-alone players only” and view the examples.

Multitypes or monotypes, and multistyles or monostyles

Multitypes style values and multistyles type values can be associated, for example: | style=neo | type=comment or | style=cameleon | type=problem
On the other hand,
- The monotype style values (fm, kifu, tiger) have their own type (and therefore the | type=[something] parameter will not do anything with these styles.
- And the monostyle types (edit, lesson) have their own style (and therefore the | style=[something] parameter will not work with these types.

SGF content
If the two following parameters (id_doc and contenu) are present, only the id_doc parameter will be taken into account.
- id=XX or - the content is in a file of id=XX, with extension .sgf, downloaded via SPIP. Regardless of whether the file is linked to the object (such as the article) where the model call is inserted
- contenu=a_sgf_content_directly_written - the SGF content is written directly or copied/pasted into the SPIP object. Beware, sgf content manually written in an article, does not support the “|” (pipe). This applies only to the contenu parameter.

Customization parameters, by types and styles

All types
- init=[init] where [init] can take the values: first (default, =go to the start of the SGF) or last (=go to the end of the main variant of the SGF file) - maxiGos parameter: initMethod
- ombre=X where X can take the values: 0 (default, =does not display a shadow on stone bottom right) or 1 (=displays a shadow on stone bottom right). - maxiGos parameter: stoneShadowOn

Types basic, comment, game, tree, edit, lesson and styles fm, tiger
- demo=X where X can take the values: 0 (=the visitor can place stones on the goban and thus create variants) or 1 (=the visitor can not place a stone on the goban or create variants). Practical for demonstrations. - Parameter maxiGos: (opposite to) canPlaceVariation

Types comment, diagram, problem, tree, lesson, styles fm, tiger, kifu and all tatami style types
- indices=X where X can take the values: 0 (=The indices are not displayed arround the goban), 1 (=The indices are displayed arround the goban) or undefined (=the SGF decides via the FG property). - Parameter maxiGos: indicesOn
- numeros=X where X can take the values: 0 (=the stones on the goban are not numbered), 1 (=the stones on the goban are numbered) or undefined (=the SGF decides via the PM property). - MaxiGos parameter: numberingOn

Types tree, edit, and tiger style
- commentaire_arbre=X where X can take the values: 0 or 1 (= If X is 1, replaces in the tree commented move numbers by a “?”). - maxiGos parameter: markCommentOnTree

Type problem only.
- recommencer_tout=X where X can take the values: 0 or 1 (=If recommencer_tout is 1, displays a retry button). - maxiGos parameter: canRetry
- reprendre_coup=X where X can take the values: 0 or 1 (= If reprendre_coup is 1, displays an undo button). - MaxiGos parameter: canUndo
- montrer_suite=X where X can take the values: 0 or 1 (= If montrer_suite is 1, displays a continuation button. A click on this button shows moves of the first branch of the sgf tree from the current position). - MaxiGos parameter: canContinuation

Examples of use.

In an article, since the use in a template appears here irrelevant.

will present an example of a problem (taking a stone), in classic style, basic type.

will display a tatami-style player, with a tree type, in Chinese language, from the game or the problem contained in a .sgf file of id=XX.

Temporary demonstration

- In the articles of this section
- On European Go Congress 2019 website

Secure your SPIP website with https://

erational, Loiseau2nuit — 2017-02-23T11:00:00Z

How to easily migrate your SPIP website from http:// to https://

https:// protocol is largely spreading:

most big websites are early adopters
it's recommanded for better data transactions' privacy
web browsers now flag http:// websites as “Not Secure”
it's part of quite every search engine guidelines for SEO
...

Hopefully, in most case it's really simple to get SPIP ready for https://. This post shows you how to do it.

Step 1 - Get a SSL certificate for HTTPS

On shared hostings, the option has to be available and should be activated on domain level or, desired sub-domain.

On dedicated servers, Let's encrypt is the solution that let's you generate your own certificates.

Install Let's Encrypt ssl certificate on debian/ubuntu

Step 2 - Modify website's canonical URL

In the admin area:

Go to menu configuration > Site identity > Website URL
Change the adresse from http://www.your-domain.tld to https://www.your-domain.tld (add www. or not, depending on your .htaccess branding/redir. policy)
Save the changes then, go empty your cache via menu Maintenance > Empty the cache

If your templates use the #CHEMIN tag, as normally requested, the update to do should be minimal, addresses already being path relative (normally).

Don't forget to check on those points:

External ressources (fonts, styles, libs, js, ...) should all be called and accessible with https://. => Eg. each & every http://cdn.something.tld/some.js becomes https://cdn.something.tld/some.js
Sounds obvious but browse your website to check on your browser is not detecting any glitch.

For example with Firefox:

	It Works ! `https://` version is up & running
	`https://` is up but some ressources are still called with `http://`

Google Chrome's consol also provides with mixed http / https content errors

Step 4 - Set up `.htaccess` file to force HTTPS

Once HTTPS is set up, we force redirect all HTTP requests toward their equivalent HTTPS URLs, by adding the foillowing custom setting to the .htaccess file:

RewriteCond %{HTTPS} !=on RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Known issue

If your server is mis-configured and/or doesn't provide any $_SERVER['HTTPS'] variable, then you may experience some troubles with mixed content issues.

To bypass that, add the following lines to your config/mes_options.php :

$_SERVER['HTTPS'] = 'on'; $_SERVER['SERVER_PORT'] = '443';

BootStrap v2 for SPIP

rjadot — 2015-10-09T06:30:00Z

Documentation origin http://spipr.nursit.com/bootstrap

Presentation

BootStrap is a framework which facilitates and accelerates the front-end development. It includes

A very complete CSS base (in LESS format) configured from variables files;
a set of conventions of HTML structure and classes naming;
simple Javascripts libraries for the most common functions.

BootStrap has a detailed documentation which facilitates its handling.

BootStrap for SPIP

A plugin BootStrap for SPIP facilitates the integration of BootStrap v2. The plugin includes all the CSS of BootStrap (v2.3.2) and adds to them a layer of adaptation to SPIP.

Adaptation to the SPIP markup

The plugin integrates the CSS of BootStrap without modification, but adds to it an adaptation layer to the HTML generated by SPIP. So, the SPIP forms which use a HTML markup different from the one proposed by BootStrap benefit all the same from the styles of BootStrap. If you add your own forms, you can use as well the markup of BootStrap or the one of the SPIP, according to your habits.

Tables generated by SPIP from the editorial contents also inherit the styles of BootStrap.

Furthermore, the plugin adapts the the pagination markup of SPIP so that it benefits from styles of BootStrap.

Typography

The typography natively proposed by SPIP in its default template is better than that the BootStrap one. It's also more accessible as it's implemented in em and not px.
The BootStrap for SPIP plugin thus takes back typography of SPIP for these reasons.

grid

The plugin BootStrap for SPIP also the integrates #grid display tool. It allows the webmasters to display the currently used grid. It's configured to settle by default on the 3 BootStrap grids (according to the screen width) and you can use it thus directly.

LESS

To allow to work directly in style sheets in LESS format without passing by a stage of manual compilation, the plugin BootStrap requires the plugin LessCSS for SPIP' which automatically compiles LESS sheets in CSS on the fly.

BootStrap in SPIPr

All the BootStrap styles are included in the pages of the SPIPr template, it is thus possible to use the whole markup proposed in the BootStrap documentation and to benefit from its styles and scaffolding.
In the case of forms, it is possible also to use the tagging convention proposed in SPIP, which is entirely managed by the adaptation of BootStrap to SPIP.

On the other hand, most of the Javascripts of BootStrap are not integrated by default and you will thus have to add them in your templates to use the corresponding features of BootStrap.

Demo page

The plugin BootStrap for SPIP integrates several demo pages demo/ directory.

The main demo page is visible at the spip.php?page=demo/bootstrap [1]. This page displays all the elements of interface managed by BootStrap, as well as a typographic charter which allows to verify the display of all the usual typographic enrichments.

BootStrap demo page

Organization of files

The plugin BootStrap for SPIP is organized in two under files(cases) bootstrap / and bootstrap2spip/:

bootstrap/ et bootstrap2spip/ :

bootstrap/
- bootstrap/
  - css/
    - BootStrap LESS files
  - img/
    - BootStrap glyphicons images
  - js/
    - BootStrap javascripts files
- bootstrap2spip/ Overloads the Bootstrap files
  - css/
    - boot-theme.less empty file available for customization
    - bootswatch.less empty file available for customization
    - spip.css Some styles for the code generated by SPIP
    - spip.list.less styles of the lists module
    - spip.comment.less styles of comments
  - formulaires/
    - charter.html SPIP demo form
    - recherche.html SPIP search form adapted to BootStrap
  - js/
    - hashgrid.js #grid
    - html5.js HTML5 support for old browsers
  - modeles/
    - SPIP pagination templates adapted to BootStrap

LESS sheets overloads

The bootstrap2spip/ directory contains LESS style sheets which overload those of BootStrap. Let us see a concrete example with the sheet alerts.less:

/* importer la feuille d'origine de BootStrap */ @import "bootstrap/css/alerts.less"; /* Ajout des classes info, success, warning, error utilisées dans SPIP */ .info {.alert; .alert-info;} .success {.alert; .alert-success;} .warning {.alert;} .error {.alert;.alert-error}

Here we see that the overloads for SPIP completely uses the native BootStrap file by simply adding to it some definitions which inherit from BootStrap. It is the case of most of the overloading files in bootstrap2spip/ with the exception of the typography completely taken back by SPIP.

Using the overloads

During the compilation of the LESS files, the plugin LessCSS interprets each @import directive by searching the file in the SPIP path, including plugins and squelettes/ direcory.

So, if you write @import "css/alerts.less", SPIP is going to look for the file css/alerts.less in squelettes/ then in all the directories declared by the plugins.
In the BootStrap plugin, the search will be made at first in the bootstrap2spip/ diretory to see if a specific overload for SPIP exists, then in bootstrap/ to take the native BootStrap files otherwise.

You can thus customize finely the overloads of BootStrap in the following way:

For example:

You can cancel the adaptation to SPIP for the file css / alerts.css by putting the contents following in skeletons / css / alerts.css:
```
/* importer la feuille d'origine de BootStrap */ @import "bootstrap/css/alerts.less";
```
vous pouvez compléter l'adaptation à SPIP avec vos propres compléments. Pour le fichier css/alerts.css, en mettant le contenu suivant dans squelettes/css/alerts.css :
```
/* importer la feuille adaptée à SPIP */ @import "bootstrap2spip/css/alerts.less"; /* mes ajouts */ ...
```

In a general way, you should avoid overloading BootStrap LESS files to benefit from updates of these files during the update of the plugin.

For your site customization, it's better to use 2 files css/boot-theme.less and css/bootswatch.less which were added and are empty by default. They allow to add customizations of BootStrap CSS, which will be compiled with the set of BootStrap files (which allows to use all the BootStrap mixins).

Images in LESS sheets

A point to which it is necessary to pay attention with LESS is about the relative ways towards the decoration images: the functioning is different from what we can be used in CSS sheets.

In a CSS sheet, if you use the code url(../img/deco.png) the relative way /img/deco.png is interpreted with regard to the location of the CSS file.

In a LESS sheet, with the same code, the relative way is interpreted with regard to the location of the main compiled LESS file. It makes an important difference when the directive @import is used.
Indeed, in this case it is always the location of the main file, the one who makes @import, which is taken in reference, and not the location of included files, even if it is the which references the image.

In the case of BootStrap, it means that it is the location of the file bootstrap.less that is taken into account. So, to use an image in a customized BootStrap LESS file, it is advisable to give a relative way with regard to the file bootstrap.less.

The solution consists then in copying the file bootstrap.less in your squelettes/, folder next to your customized file, without forgetting to also copy there the img/ folder with glyphicons. It is rather impractical, and in a general way it is avoidable by adding the images of decoration in a LESS file which is not included by bootstrap.less but directly by the SPIPr template.

Resources

An indicative and not exhaustive list of tools usable as a supplement to BootStrap to generate themes, build mockup [2]

http://bootswatch.com/
https://wrapbootstrap.com/themes
http://jetstrap.com/ un outil de Mockup en ligne pour BootStrap
http://stylebootstrap.info/
http://www.boottheme.com/
http://bootswatchr.com/
http://www.lavishbootstrap.com/

[1] You must have the webmaster statute to see this page

[2] take care about the BootStrap version which are supported by these tools: if it is an older version that the one used by SPIPr, some variables may be lacking in the generated sheets

Animated dropdown menu

Louis Possoz — 2015-09-12T13:29:59Z

Dynamic multilevel menubar - easy (?) adaptation of colors and sizes - Also suitable for small screens (mobile).

Very simple display of a multilevel animated dropdown menu!

The plugin is suitable for small screens (mobile)!
The color themes and dimensions are modifiable, as explained in the last section below.

Introduction

Flexibility and simplicity are the main keywords for this menu displayer. See an example on our Repair Café website.
It uses (all?) the potential of the various browsers: colour gradients, shadow for boxes and texts, as well as rounded corners, not to mention the dynamic menu boxes!

For smaller screens, the plugin reacts differently and displays a vertical drop down menu. The menu can also be discrete, disappearing at printing!

This animated dropdown menu is essentially based on a simple (!) style sheet (menu_anime.css). It does all the work!
This plugin is an ideal complement to the menus plugin but it is convenient for all menus containing a selector class="menu_anime".

The plugin is also designed to simplify the adjustment of colours and dimensions to each particular site. A method for doing it is described in detail at the end of this article.

The original idea of this menu is linked to the work of Catalin Rosu. This plugin has originally been derived from his elegant and talented handling of style sheets.

Installation

Choose a manual or automatic method provided by SPIP. The plugin has no dependencies.

Use

The simplest and most general use of this plugin is through the plugin menus. After enabling this plugin (if not already), simply create a menu (or edit an existing menu) ensuring to assign the CSS class menu_anime as can be seen on the following screen-shot.

Here, the identifier “barrenav” causes the menu to display as the main navigation bar. No other intervention is necessary!

More generally, the plugin will display an entire list of links (of one or several levels) of which the first level contains the selector .menu_anime (ie

.menu container

Of course and as usual, the menu_anime.css stylesheet can be modified (by placing the modified copy in the squelettes/css/ directory). You certainly will be impatient to change the menu colours. However, direct intervention on the style sheet itself is particularly complex and daunting. That is why an alternative method has been developed (see below).

Changing colours and sizes

The plugin contains a file menu_anime.less allowing easy (?) adaptation to the specific characteristics of each website.
Although the process may seem a little daunting, it is infinitely easier than direct edition of the menu_anime.css style sheet.

Step by step procedure:

Open the file menu_anime.less for editing. This file is contained in the package.
In this file, change the colour and/or size values as desired. They are at the beginning of the file.
Compile the resulting file using a compiler Less compiler, eg online compiler.
Create a menu_anime.css empty file and copy-paste the result of the compilation in it.
Place the new file in the squelettes/css/ directory or replace the one located in the directory plugins/auto/menu_anime/css/.
Carefully store your version of the file menu_anime.less so you can recover your settings for later updates.

Example: changing the base colour of the menu

Select a new colour using an online color utility.
Open the file menu_anime.less in a text editor.
Replace the colour value (#b0422c) in the line @theme-basic: #b0422c; / * ... * / with the one that was chosen.
Compile the content of this new file through an online compiler.
Create a new empty file menu_anime.css and place the entire result of the compilation (copy and paste).
Set the resulting file menu_anime.css in the squelettes/css/ your favourite SPIP. By the way, add your modified menu_anime.less file in the same directory (so you will not lose it).

Simple, isn't it?

Another solution would perhaps be to use the LESS CSS plugin. But I'm not sure it would give any advantage. Changing colours of a website menu is a very infrequent operation once it has been installed. To be discussed...

Favicon

erational, Loiseau2nuit, tetue — 2015-06-04T11:12:00Z

This plugin automatically creates 'favicons' and 'touch icons' to fit various browsers & devices compliance.

Upload the website's logo in the admin area, through main menu Configuration > Site identity. To get the best styling possible, your website's logo should be square shaped and, at least 150px wide. If not via FTP as an favicon.png file in your /squelettes template's directory

The plugin then automatically includes all calls to favicons variations and proprietary-declined types such as apple-touch-icon or msapplication-TileImage (in the website's section, thanks to the #INSERT_HEAD tag).

This is a sample of code, generated by the plugin:

Want more ? Read this quite complete synthesis on favicons.

Yippee, SPIP 2.1.27 and SPIP 3.0.19 are now available !

L'équipe de SPIP-Contrib — 2015-05-16T16:25:25Z

SPIP 3.0.19 and 2.1.27 are minor releases for maintenance waiting for SPIP 3.1 release.

These versions fix many bugs and provide handy improvements.

SPIP 3.0.19
Enhancements and fixes:

Database backups.
image_recadre filter can now crop an image to respect a proportion.
Research of short and accented words.
Display of search engines thumbnails in the statistics page.
robots.txt file updated to make SPIP websites more “Google mobile friendly”. Stylesheets compression option must be enabled.
Anonymous sessions bug fixed.
Switch from ssl:// to tls:// for https requests on servers with a recent OpenSSL lib.

Detailed changelog :
- https://core.spip.net/projects/spip/repository/revisions/22089/entry/tags/spip-3.0.19/CHANGELOG.txt
- http://www.spip.net/fr_article5737.html

As a matter of fact, SPIP 3.0.18 lived only a few hours.

SPIP 2.1.27
Enhancements and fixes:

Limit goneaway queries in MySQL.
Sending emails bug fixed.
robots.txt updated to make SPIP more “Google mobile friendly”.

Detailed changelog :
- https://core.spip.net/projects/spip/repository/revisions/22103/entry/tags/spip-2.1.27/CHANGELOG.txt
- http://www.spip.net/fr_article5738.html

How to update?

Various resources are made available by the community to provide help:

List spip-user: http://listes.rezo.net/mailman/listinfo/spip
Forum: http://forum.spip.net
IRC: http://irc.spip.net

1. Using spip_loader.php (latest version 2.5.5)

If you have already installed spip_loader, go to http: //yoursitedomain/spip_loader.php to install the latest version of SPIP.

Pay attention to not switch inadvertently from SPIP 2 to SPIP 3. To avoid this, please read carefully the instructions at http://www.spip.net/fr_download#spip_loader.

Everything about spip_loader at http://www.spip.net/fr_article5705.html

2. Copying files

dowload SPIP 3.0 at http://files.spip.org/spip/stable/spip-3.0.zip
download SPIP 2.1 at http://files.spip.org/spip/stable/spip-2.1.zip

3. Using SVN:
Check out branch 3.0 at svn up svn://trac.rezo.net/spip/branches/spip-3.0

How to be posted about updates?

The simplest way is to register on the mailing http://listes.rezo.net/mailman/listinfo/spip-ann list.

Social networks are also an option:

Twitter: http://twitter.com/spip
Facebook: http://www.facebook.com/spip.net
Seenthis: http://seenthis.net/people/spip

Reminder: the best way to report security issues or concerns is to send an email to spip-team@rezo.net.

Bonux for SPIP 3.*

JLuc, Loiseau2nuit — 2015-01-28T12:17:00Z

A great number of the features brought by the first version of SPIP Bonux have since then been fully incorporated into SPIP3. Some still haven't yet, and those are brought by this new plugin's version Bonux for SPIP3.

This post lists all tags, criterias & functions, that are defined by SPIP Bonux, for we can keep them in mind, but the documentation of those elements won't appear on (see also other documentation posts to SPIP Bonux or even the source code).

Note: to avoid conflicts, some of these functionalities are defined by Bonux only if they have NOT been already defined elsewhere.

Tags, criteria & loops

Tags

#SET_PUSH stacks an element in an array, instantiated with #SET{my_array,#ARRAY}
#SET_MERGE
#COMPTEUR (Counter)
#SOMME (Sum)
#COMPTE (Account)
#MOYENNE (Average)
#MINIMUM
#MAXIMUM
#STATS

The tags #COMPTEUR, #COMPTE, #SOMME, #MOYENNE, #MINIMUM, #MAXIMUM and #STATS require using a criterion that specifies the field, which the Tag is calculated on.

Those criterions does not calculate any joint or relational database, contrary to the {compteur table} criterion which does.

Examples of usage :

- #SET_PUSH : #SET_PUSH{my_array,my_value}

Statistics criteria

{compteur}
{compteur_left}
{somme}
{compte}
{moyenne}
{minimum}
{maximum}
{stats}

Examples of usage :

- Let's say an extra field 'distance' was added to the ARTICLES objects (posts). The following loop will then calculate the sum (#SOMME) of the distances set in every article posted into section id n°1 (id_rubrique=1)

 #SOMME{distance}

- In the plugin 'abonnement' for example, the 'abonnements_stats ' file gives several examples of those criteria.

For example:

 #COMPTE{montant} [(#SOMME{montant}|number_format{2, ',', ' '}|replace{' ',' '})]

Other criterion

{fusion_supprimer} : this criterion deletes from the SQL query the GROUP BY condition which is already implied, a this compilation step. That might be useful to get rid of a potential interfering GROUP BY, eventually added by default by SPIP's compiler while joining tables. It then becomes possible to add a criterion for the desired merge (see issue #3209).

In the following loop, we have to add {fusion_supprimer} in order to get the merge on dates, because the compiler automatically adds a GOUP BY id_article to join the ARTICLES table (posts) to the MOTS table (keywords) :

 [(#DATE|annee)]

PHP functions

Bonux also defines a whole set of functions, that can be used as filters or by other plugins.

/** Get fields date_$suffixe and heure_$suffixe in the environment, check for their relevancy and re-format them */ function verifier_corriger_date_saisie($suffixe,$horaire,&$erreurs); /** Returns the charset of a line, to be imported */ function importer_csv_importcharset($texte); /** Removes accents from keys, to avoid problems ... */ function importer_csv_nettoie_key($key); /** Reads a CSV file & returns an array if $head is true, the first line is used as a header to generate an array*/ function inc_importer_csv_dist($file, $head = false, $delim = ",", $enclos = '"', $len = 10000) ; /** Exports a field to a CSV export */ function exporter_csv_champ($champ) ; /** Exports a full line, CSV formated, with specified delimiter */ function exporter_csv_ligne($ligne, $delim = ',', $importer_charset = null) ; /** export as CSV. $resource is an array or any open readable SQL resource */ function inc_exporter_csv_dist($titre, $resource, $delim=',', $entetes = null,$envoyer = true); /** generates an IMG tag from a file name */ function tag_img($img,$alt="",$class=""); /** generates a temporary key with 12h validation for the current URL */ function previsu_cle_temporaire($date=null); /** checks if a 12h temporary key is valid */ function previsu_verifier_cle_temporaire($cle); function _T_ou_typo($valeur, $mode_typo='toujours') ; function spip_array_insert($arr1, $cle, $arr2, $avant=false); function array_replace_recursive($array, $array1); function recurse($array, $array1); /** Truncates a string to the desired length, without harming HTML markup and, with options : end text if cut, cut to exact length or, respecting words... */ function text_truncate($text, $length = 100, $options = array()) /** return an array, containing every value in any column of any bi-dimensional table (possibly along values of another column, as an index) */ function array_column($input = null, $columnKey = null, $indexKey = null);

filtre text_truncate
function text_truncate($text, $length = 100, $options = array());

The options array can contain several couples of key/value:
- 'ending' => string added at the end of the text, if it has to be cut. Basically, it'll be '...' or 'read more'.
- 'exact' => a boolean defining if it's to be cut at the exact provided length, even if it's in the middle of a word or, just before that last word.
- 'html' => a boolean defining if text contains any HTML tags that are not to be cut incorrectly.

array_column function

Loads the PHP 5.5 function array_column for older versions.

Renamed

- |aoustrong filter is gone : it became |lien_ou_expose and was incorporated to SPIP.

Refer to the documentation of the commit.

Albums 3 (en)

tcharlss — 2014-08-08T09:00:00Z

The plugin «Albums» evolves with a version 3 made for SPIP 3.

Before upgrading from previous versions, read the notes regarding the retro-compatibility.

This quick presentation video is in french, but it might be helpfull nonetheless.

https://medias.spip.net/IMG/mp4/montage-encoded.mp4

Albums purpose

In the first version, the plugin's purpose was to insert galleries of images inside the text of articles.

Since the version 2, albums are editorial objects, and so the plugin's scope is broader : its purpose is now to manage groups of documents.

⇒ Groups of documents

An album is a container for a serie of documents.
Despite its name, it may contain any types of documents, not just images.
One document may belong to several different albums : all kind of combinations are possible.

Albums are groups of documents

⇒ Albums, documents and objects

In SPIP 3, documents associated with an object are dispatched into 3 sections : «illustrations», «portfolio» and «documents».
In this documentation, we will refer to these documents as «individual» documents, as opposed to documents grouped into albums.

Individual documents and albums are independents and do not interfere with each other : you can continue to manage individual documents the same way as before.
Except now, you have the choice when adding documents to an object : they can be added individually, or grouped into albums.

Albums et documents liés

Documents individuels et regroupés aux seins d'albums

Installation & configuration

You can install the plugin the standard way.
2 tables will be added : spip_albums and spip_albums_liens.

Additional plugins are neccesary in order to enable the customization of tags. These are optional dependencies, install them if you whish to benefit from this functionnality.

Once the installation is done, visit the plugin's configuration page. It is divided in 2 tabs.

⇒ «options» tab
First, choose which objects may receive albums.
There are 2 more options : you can enable the suggestion of a default title when adding an album to an object, and enable moving documents between album with drag and drop.

⇒ «tools» tab
A form will convert articles into albums.
Use it in case you were using articles as pseudo-albums : real ones will be created identically.

Utilisation

Albums may be independents or associated with editorial objects.

⇒ Independent albums can be created from the toolbar or from the «Albums» page.

⇒ The management of albums associated with objects is quite similar to that of individual documents : albums can be managed from the object's page or when the object is being edited.

Managing albums from an object's page

On the page of an object, albums are located after the documents. You can add new albums or existing ones, edit their text and manage their documents.

Albums et documents liés

1) documents «individuels» 2) documents regroupés au sein d'albums

⇒ Adding albums

The «Add an album» button displays a form which has two methods :

Create and «fill» a new album. The title and the description are both optionals : if the title is leaved empty, it will be populated afterward with «New album No X».

Choose existing albums : you can browse a list, or enter directly the album's numbers.

Ajouter un album à un objet éditorial

1) Créer et remplir un nouvel album 2) Choisir un ou plusieurs albums existants

⇒ Editing an album

Albums can be quickly edited «on site». For the full-blown edition (managing authors, keywords...), go to the album's page.

Editing text : an icon will appear when hovering the header, clicking it will display the form to edit the text and the description.

Adding documents : a link located in the footer will display the form to add documents.

Managing documents : the buttons will appear when hovering each document.

It is also possible, under some conditions, to move documents between albums with drag and drop.

Édition rapide d'un album

1) Editer titre et descriptif 2) Ajouter des documents 3) Modifier les documents

⇒ Removing albums

To remove an album, hover the footer to reveal the corresponding button.
When there are several albums, a button located at the end of the list can remove all of them at once.

Managing albums when editing an object

When editing an object, the albums can be managed in the same place as documents, in the left column.
When the object can receive both individual documents and albums, a menu allows you to switch between them.

Albums et documents lors de l'édition d'un objet

1) Gestion des documents 2) Gestion des albums

⇒ Adding, removing and editing albums

The management is the same as when you're on the object's page : same form to add albums, same way to edit them and manage their documents.

⇒ Inserting inside texts

Albums inserted inside texts with the tag will be automatically associated with the object.

A form will help you to customize the tag of each album, providing both YAML and Saisies plugins are installed.
Important : for this functionality to be available, additional plugins must be installed. Consult the section regarding dependencies.

Personnaliser la balise d'un album

En mode édition, un formulaire permet de personnaliser la balise de chaque album en vue de l'insérer dans le texte.

Les modèles

Models have slightly changed since versions 1 et 2. Read the notes about retro-compatibility.

2 models are available : the basic one is a thumbnail view, and there is a variation as a list view.
By default, both of them are minimalist : the title and description are not displayed unless you use the proper parameters.

The stylesheet loaded on the public site is also reduced to a minimum.

These models will not fulfill all the use-cases, as the albums may contain all kind of documents and thus may be used for all kind of purposes : audio and video playlists, diaporamas...
Do not hesitate to create your own variations of the model.

⇒ Model «thumbnails»

Modèle album par défaut : vue en vignettes

This model is intended for series of images. It is based on Tiny Typo.
Images may be resized and cropped in order to obtain an even display, by default they are resized with a 100px height.

The basic HTML structure is as follow (with #HTML5 activated) :

⇒ Model «list»

Modèle album, variante sous forme de liste

This variation displays documents as a simple list.

The basic HTML structure is as follow :

...

⇒ Models parameters

Common parameters
Parameter	Description
`titre`	«oui» to display the title Any string in order to use it as a custom title
`balise_titre`	In order to wrap the title in a tag. → strong, h4, etc.
`descriptif`	«oui» in order to display the description
`par`	Documents ordering, default : «titre» → date, titre, media, fichier, extension, taille
`media`	In order to restrain documents to one type → image, file, audio, video

«thumbnails» specific parameters
Parameter	Description
`largeur`	Max width
`hauteur`	Max height, default: 100 (pixels)
`recadrer`	«oui» in order to crop images
`label`	«oui» in order to display each document's title

«list» specific parameters
Parameter	Description
`metas`	«oui» in order to display additional information, or a list of elements comma-separated : → extension, taille, dimensions

⇒ Adding models

When you create a new HTML template as a variation of the model, a YAML file must be created as well, in order for the model to be detected by the form.

This method is inspired by the plugin Insérer Modèles : each YAML file describes the model and its parameters.
The syntax remains the same, though there are 2 more elements :

alias : name of the variation
description : description of the variation

4 parameters are mandatory : modele, id_modele, id_album et variante.
As the first 3 are identical for all variations, they are found in the file inc-yaml/album-compat.yaml which you can include.

An additional config option allows you to use a default value stored in the table spip_meta.
In a way, config:'truc' is the equivalent of 'defaut'=>lire_config('truc') with php.

Confusing? Take a look at the example.

Example : let's imagine a plugin with a «diaporama» model. It would have, among others, a speed parameter whose default value would be stored in the plugin's meta. The HTML template would be named album_diaporama.html and the YAML file would be named album_diaporama.yaml.
The later would be like that :

nom: 'an album (diaporama)'
logo: 'prive/themes/spip/images/album-24.png'
icone_barre: 'album-diaporama.png'
alias: 'Diaporama'
parametres: - 'inclure:inc-yaml/album-compat.yaml' - saisie: 'hidden' options: nom: 'variante' defaut: 'diaporama' - saisie: 'selection_album' options: nom: speed' config: 'plugin/speed' - the remaining inputs...

Use the «list» variation as a reference.

Albums page

Albumothèque

The filters located in the side column allow you to select albums according to their documents or their associations with objects : articles, authors, keywords...

Some inputs with an autocomplete function will help you find specific objects.
For instance, in order to display the albums associated with a given article, click on the icon on the right side, then enter the first letters of the article's title or its number : the corresponding articles will appear, and clicking on one entry will update the albums list.
The autocomplete function only retrieves objects associated with albums.

Albumothèque : filtres

Des champs avec autocomplétion permettent de trouver les objets liés aux albums.

Moving documents between albums with drag and drop

If the option is activated, and provided you are authorized, it is possible to move documents between albums with drag and drop.
Be aware that this is experimental-ish !

When you start draging a document, the albums which may receive it are highlighted with a dotted border. Once a document has been released in a different album, a form will appear at the bottom of the list in order to save the modifications. You may however proceed with more modifications before saving them.

Note that it is possible to include individual documents in the manipulations.

Déplacer des documents entre albums par cliquer-glisser

1) Effectuer un ou plusieurs déplacements 2) Valider avec le formulaire qui apparaît en bas

Boucles & critères

⇒ Critère {orphelins}

The criteria {orphelins} will select albums not associated with any other object.

⇒ Joins

Albums have automatic joins with all objects.

Provided that id_xxx is present in the environnement, you may select albums associated with the object without using an explicit join :

Beware though, {id_auteur} behaves differently :

select the author's albums (on spip_auteurs_liens).
selects albums associated with the author (on spip_albums_liens).

⇒ Select albums according to their documents

When using a join with the table spip_documents, it is use some criterias of documents :

For instance :

{documents.media IN image,audio} : albums containing images or audio files.
{documents.id_document=x} : albums containing the document no x.
{documents.titre LIKE %something%} : albums containing documents whose title or filename corresponds to the term «something».
{documents.extension == mp3|ogg|oga} : albums containing mp3 or ogg audio files.
{documents.taille > 1000000} : albums containing documents whose weight exceeds 1Mo [1].

Autorisations

Here are how some particular authorizations are defined (administrators can do everything).

Modify an album : one must be the album's auhtor and be authorized to modify all the objects associated with the album.
Add an album to an object : the object must be activated in the options, and one must be authorized to modify the object.
Move documents between albums : the option must be activated, and in the context of an object, one must be authorized to modify all the associated albums.
Delete an album : the album must be empty, not used, and not published.

Retro-compatibility

Models

The version 1 syntax, disabled in version 2, is supported anew : and

The structure of the basic model has changed, in order to respect the standards for the tags

and

Visually, a few changes occured :
- titles are hidden by default.
- the title and the description of the basic model are now located on the bottom.

Parameters :
- thumbnails & list : titraille has been remove
- thumbnails & list : balise_titraille is deprecated in favor of balise_titre
- liste : infos is deprecated in favor of metas

Divers

The {contenu} criteria of the version 2 has been removed.
See the section about joins.

[1] 1000000 octets = 975ko, but let's not chipote

The version 2 of the plugin has served as a transition, so to speak, between the version 1 and this version, which is the «correct» version for SPIP 3.
It will only receive bug corrections.

SPIP-Contrib

The BREVES loop (news items)

Table of contents

The selection criteria

Tags for this loop

CRITICAL security update : SPIP 3.2.4 & SPIP 3.1.10 released

Image Split

Table of contents

1. Using the “split” model

2. TwentyTwenty settings

3. Using the “Cropper” tool

Fixing release for branch 3.2 : SPIP 3.2.3

Security & maintenance updates : new versions SPIP 3.2.2, 3.1.9 and 3.0.28

TimeCircles plugin for SPIP 3.1+

Table of contents

How to install ?

How to use it

DateCountDown

CountDownTimer

PageOpenTimer

Modification and styles

Plugin is free for any use & open to common dev

TO DO

I/E config PLUS

Table of contents

Export/Import metas for new plugins:

Export/import editorial objects

YAML V2 plugin for SPIP 3.*

Table of contents

Versions and compliance

Plugin's API

YAML libraries

Plugin's maintenance

API: advanced usages

What's next ?

3,2,1... Ignition ! Maintenance upgrades for SPIP 3.2.1, SPIP 3.1.8 & SPIP 3.0.27 are out !

Table of contents

Bug fixes

security screen

spip_loader

Commplete announcement & details here :

Bingo for Friday the 13th, SPIP 3.2 is available!

Redesigning SPIP graphical identity

CRITICAL security update: SPIP 3.1.6 and SPIP 3.2 Beta 3

Table of contents

The following updates are available:

The security screen

Update using spip_loader

Summary of SPIP versions

How to be kept informed about these announcements?

A question, in need of help?

Go diagrams with maxiGos.

Table of contents

Installation.

Authorization of SGF documents

Third party.

Rules for sgf format.

Model parameters

Examples of use.

Temporary demonstration

Secure your SPIP website with https://

Table of contents

Step 1 - Get a SSL certificate for HTTPS

Step 2 - Modify website's canonical URL

Step 4 - Set up .htaccess file to force HTTPS

Known issue

BootStrap v2 for SPIP

Table of contents

Presentation

BootStrap for SPIP

Adaptation to the SPIP markup

Typography

grid

LESS

BootStrap in SPIPr

Demo page

Organization of files

LESS sheets overloads

Using the overloads

Images in LESS sheets

Bingo for Friday the 13^th, SPIP 3.2 is available!

Step 4 - Set up `.htaccess` file to force HTTPS