1 | <h2>Maintenance</h2> |
---|
2 | |
---|
3 | <p>To optimize page generation time, Piwigo uses cached |
---|
4 | information. For example, instead of counting the number of pictures |
---|
5 | contained in each category at each page reload, this information is stored |
---|
6 | in the database. In theory, this information should always be correct, but |
---|
7 | sometimes an error can occur and cached information becomes wrong.</p> |
---|
8 | |
---|
9 | <p>Some informations become useless with time. Deleting this useless |
---|
10 | information from database make you save disk space.</p> |
---|
11 | |
---|
12 | <ul> |
---|
13 | |
---|
14 | <li><strong>Update categories informations:</strong> For each category, |
---|
15 | informations to update or control are the following : list of parent |
---|
16 | categories, number of pictures, date of the last picture, position among |
---|
17 | brother categories, position among all categories. This action also checks |
---|
18 | the coherence of representative picture.</li> |
---|
19 | |
---|
20 | <li><strong>Update images informations:</strong> For each picture, |
---|
21 | informations to update are : full path to file, average |
---|
22 | rate. <em>Warning</em>: do not get confuse with metadata informations |
---|
23 | which can be synchronized from <span class="pwgScreen">Administration, |
---|
24 | Categories, Synchronize</span> or by reaching the modification screen of a |
---|
25 | single picture (through <span class="pwgScreen">Picture</span> for |
---|
26 | example).</li> |
---|
27 | |
---|
28 | <li><strong>Repair and optimize database:</strong> |
---|
29 | For each table, re-odrer, repair and optimize operations are done. |
---|
30 | </li> |
---|
31 | </ul> |
---|
32 | |
---|
33 | <ul> |
---|
34 | <li><strong>Purge history detail:</strong> Delete all lines from |
---|
35 | <code>history</code> table. Screen <span class="pwgScreen">Administration, |
---|
36 | Specials, History</span> shows no informations anymore on past |
---|
37 | history. <em>Warning</em>: all data will be lost and there is no way to |
---|
38 | get informations back.</li> |
---|
39 | |
---|
40 | <li><strong>Purge history summary:</strong> Delete all the summary information about visit history. This summary is calculated from the history detail.</li> |
---|
41 | |
---|
42 | <li><strong>Purge sessions:</strong> Delete expired user sessions.</li> |
---|
43 | |
---|
44 | <li><strong>Purge never used notification feeds</strong></li> |
---|
45 | |
---|
46 | <li><strong>Purge search history</strong></li> |
---|
47 | |
---|
48 | <li><strong>Purge compiled templates</strong></li> |
---|
49 | </ul> |
---|