Browser upload, Theme manager, Admin usability
Piwigo 2.1 introduces major improvements. We have been working to improve user experience, at administration level mainly. Photos are easier to upload, themes are easier to install, administration is easier to read (if you hate dark backgrounds), administration menu was reorganized, plugins are easier to manage, tags are easier to add and create, photos are easier to sort, features are easier to activate/deactivate.
At technical level, the theme architecture was redesigned to make theme creation easier. MySQL is no longer the only database backend, PostgreSQL and SQLite are available.
More than 100 bugtracker issues (features and bugs) were closed, 1000 commits were performed in the source code manager. Piwigo 2.1 is available in 23 languages out of the box (compared to 9 languages for Piwigo 2.0). Piwigo 2.1 includes code from more than 40 contributors including developpers, translators, beta-testers.
As soon as Piwigo is installed on your website, you get a big and obvious message "I want to add photos" which goes to the new photo upload form.
The goal is to avoid the question "OK, Piwigo installed, how do I add photos now?".
Piwigo 1.0 had a single method to add photos: FTP + synchronization. Piwigo 2.0 came with pLoader, the Piwigo Uploader.
Piwigo 2.1 brings a new method: add photos directly from your web browser:
Photos are automatically resized and thumbnails created.
Install, activate or set a theme as default just with a few mouse clicks.
The theme manager is directly connected to piwigo.org theme directory. As soon as a theme is added by a community contributor, you can install it on your Piwigo installation.
Installed themes can be active or inactive. An inactive theme can't be selected by your users.
With just 1 click, you can set a theme as default.
Just like the theme manager, you can install additionnal languages from the piwigo.org language directory, and deactivate languages you don't want available on your gallery.
We have performed many design changes in the administration with a specific goal in mind: improve usability.
New design for plugin installation screen.
New Admin > Configuration > Options > Display screen with many options to customize available features for users, and select photo properties to display.
Even if you are not currently browsing a tag, Piwigo displays the related tags of the current photo set.
We display a single link to display the "tag1" + "tag2" photo set.
The more you add tags, the more it reduces the number of matching photos.
Forget about template/theme, the 2 levels architecture. Now we have a single level architecture : themes. *.tpl files still exist: they are in the subdirectory "template" of the theme "default".
Each theme declares its parent theme. A child theme uses its parent template files, unless they are also available in the child theme itself. For example, your child theme can have only the picture.tpl template file, all other template files will be taken from parent theme.
A child theme can either overload or replace the CSS rules of its parent theme.
If you want a new theme that looks a lot like the "clear" theme, don't duplicate it: create the "clearChild" theme and only define a few CSS rules.
We have added a database abstraction layer. Depending on your configuration, Piwigo will use MySQL, PostgreSQL or SQLite as data backend. This is totally transparent for users of course.