The oTable javascript variable is built with jQuery('#userList').dataTable(),
which returns a jQuery object, while jQuery(...).Datatable() would directly
return a DataTables API object. So now, to access the draw() function, we need
to get the api() first from the jQuery object.
https://datatables.net/manual/api#Accessing-the-API
On identification.php, do not show the "... not authorized..." error message
on redirection to when guest_access is false. This is "on purpose" and users
don't need to get this message.
Use the following syntax in HTML:
<label class="font-checkbox">
<span class="icon-dot-circled"></span>
<input type="radio" name="radio-name" value="my-value"{if template condition} checked="checked"{/if}>
A nice label
</label>
By default, we're in "view mode", with the showInfo icon on each tag. We can
switch to the "selection mode" and the showInfo icon is replaced by a
font-checkbox.
The actions are no longer displayed a individual submit buttons, but as a
select, like on other managers (users, photos, groups).
The edit/duplicate/merge forms are still displayed only after a first submit.
To be improved to be available right after the action selection.
When we display an action form edit/duplicate/merge, we don't show other
fieldsets on the page to focus on the important action.
Every 1000 log entry inserted, Piwigo performs an history summarize.
The summarize process has also been optimized: no longer used column
history.summarized (no longer need to update it, which took a lot in time),
we now save the history_id_from and history_id_to in history_summary table.
This way we know from where to start on next summarize.
For now, for a simple performance reason, we keep column history.summarized,
because removing it may take a long time on huge tables. Once we will have
automatic purge on history, it will be safer to drop this column.
plegall