SPIP 1.9.2b "1.9.2b"

    * a number of new image filters and image filter optimisation;
    * new functionality in the backup/restore tools;
    * a more responsive caching system;
    * the introduction of the jQuery javascript library;
    * the directory structures have been revised;
    * an extensible XHTML validator;
    * a programming interface (API) for managing authorisations and changes;
    * more accurate site visit statistics.

Milestone information

Project:
SPIP
Series:
trunk
Version:
1.9.2b
Code name:
1.9.2b
Released:
2007-07-11  
Registrant:
martin gaitan
Release registered:
2007-07-11
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon spip.tar.gz (md5) Several innovations concerning the application programming interface (API) of SPIP, specifically the number of functions available to programmers (especially for plugins). This new version, therefore, earns much of its credit from the new plugins that will become available (for example, the "crayons" plugin which enables editing articles directly from the public site ; the automatic XHTML validation plugin, etc.) spip 1.92b version 26
last downloaded 6 weeks ago
Total downloads: 26

Release notes 

Several innovations concerning the application programming interface (API) of SPIP, specifically the number of functions available to programmers (especially for plugins).

This new version, therefore, earns much of its credit from the new plugins that will become available (for example, the "crayons" plugin which enables editing articles directly from the public site ; the automatic XHTML validation plugin, etc.)

When migrating an existing site to this new stable version, the following notes are important:

    * directory reorganisation, in particular the relocation of CACHE and ecrire/data to tmp/ ; image thumbnails relocated to local/, and relocating configuration files (mes_options.php, connect.php) to config/;
    * the ecrire/ directory therefore, now only contains scripts, and it can be shared amongst several site URLs (refer to the article on shared provisioning);
    * If you use image filters (most notably image_reduire), a now-repaired bug has broken compatibility in the thumbnail naming convention. So SPIP will need to recreate all your thumbnails. You can delete thumbnails in the IMG directory prior to migration.

Changelog 

View the full changelog

Several innovations concerning the application programming interface (API) of SPIP, specifically the number of functions available to programmers (especially for plugins).

This new version, therefore, earns much of its credit from the new plugins that will become available (for example, the "crayons" plugin which enables editing articles directly from the public site ; the automatic XHTML validation plugin, etc.)

When migrating an existing site to this new stable version, the following notes are important:

    * directory reorganisation, in particular the relocation of CACHE and ecrire/data to tmp/ ; image thumbnails relocated to local/, and relocating configuration files (mes_options.php, connect.php) to config/;
    * the ecrire/ directory therefore, now only contains scripts, and it can be shared amongst several site URLs (refer to the article on shared provisioning);
    * If you use image filters (most notably image_reduire), a now-repaired bug has broken compatibility in the thumbnail naming convention. So SPIP will need to recreate all your thumbnails. You can delete thumbnails in the IMG directory prior to migration.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.