62 lines
2.4 KiB
HTML
62 lines
2.4 KiB
HTML
<h2>Maintenance</h2>
|
|
|
|
<p>To optimize page generation time, Piwigo uses cached
|
|
information. For example, instead of counting the number of pictures
|
|
contained in each category at each page reload, this information is stored
|
|
in the database. In theory, this information should always be correct, but
|
|
sometimes an error can occur and cached information becomes wrong.</p>
|
|
|
|
<p>Some information become useless with time going by. Deleting this useless
|
|
information from database make you save disk space.</p>
|
|
|
|
<ul>
|
|
|
|
<li>
|
|
<strong>Unlinked elements:</strong>
|
|
Display images which are not associated to any virtual category.
|
|
</li>
|
|
<li>
|
|
<strong>Files with the same name in more than one physical category:</strong>
|
|
Display images or files which are found with the same filename in several categories.
|
|
</li>
|
|
|
|
</ul>
|
|
|
|
<ul>
|
|
|
|
<li><strong>Update albums informations:</strong> For each category,
|
|
the following information is checked, and updated if necessary : list of parent
|
|
categories, number of pictures, last picture date, position among
|
|
brother categories, position among all categories. This action also checks
|
|
the representative picture consistency.</li>
|
|
|
|
<li><strong>Update images information:</strong> For each picture,
|
|
information updated is : full path to file, average
|
|
rate. <em>Warning</em>, do not mix up: metadata information
|
|
must be synchronized from <span class="pwgScreen">Administration,
|
|
Categories, Synchronize</span>, or on the modification screen of a
|
|
single picture (through <span class="pwgScreen">Picture</span> for
|
|
example).</li>
|
|
|
|
<li><strong>Repair and optimize the database:</strong>
|
|
Perform re-order, repair and optimize operations on each table of the database.
|
|
</li>
|
|
</ul>
|
|
|
|
<ul>
|
|
<li><strong>Purge history details:</strong> Delete all lines from the
|
|
<code>history</code> table. Screen <span class="pwgScreen">Administration,
|
|
Specials, History</span> will not longer show information for the past
|
|
history. <em>Warning</em>: all data will be lost, without any way to
|
|
get them back.</li>
|
|
|
|
<li><strong>Purge history summary:</strong> Delete all the summary information about visit history. This summary is calculated from the history details.</li>
|
|
|
|
<li><strong>Purge sessions:</strong> Delete expired user sessions.</li>
|
|
|
|
<li><strong>Purge never used notification feeds</strong></li>
|
|
|
|
<li><strong>Purge searches history</strong></li>
|
|
|
|
<li><strong>Purge compiled templates</strong></li>
|
|
</ul>
|