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 photos |
---|
5 | contained in each album 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 information become useless with time going by. Deleting this useless |
---|
10 | information from database make you save disk space.</p> |
---|
11 | |
---|
12 | <ul> |
---|
13 | |
---|
14 | <li> |
---|
15 | <strong>Unlinked photos:</strong> |
---|
16 | Display photos which are not associated to any virtual album. |
---|
17 | </li> |
---|
18 | <li> |
---|
19 | <strong>Files with the same name in more than one physical album:</strong> |
---|
20 | Display photos or files which are found with the same filename in several albums. |
---|
21 | </li> |
---|
22 | |
---|
23 | </ul> |
---|
24 | |
---|
25 | <ul> |
---|
26 | |
---|
27 | <li><strong>Update albums informations:</strong> For each album, |
---|
28 | the following information is checked, and updated if necessary : list of parent |
---|
29 | albums, number of photos, last photo date, position among |
---|
30 | brother albums, position among all albums. This action also checks |
---|
31 | the representative photos consistency.</li> |
---|
32 | |
---|
33 | <li><strong>Update photos information:</strong> For each photo, |
---|
34 | information updated is : full path to file, average |
---|
35 | rate. <em>Warning</em>, do not mix up: metadata information |
---|
36 | must be synchronized from <span class="pwgScreen">Administration » |
---|
37 | Tools » Synchronize</span>, or on the modification screen of a |
---|
38 | single photo (through <span class="pwgScreen">Photo</span> for |
---|
39 | example).</li> |
---|
40 | |
---|
41 | <li><strong>Repair and optimize the database:</strong> |
---|
42 | Perform re-order, repair and optimize operations on each table of the database. |
---|
43 | </li> |
---|
44 | </ul> |
---|
45 | |
---|
46 | <ul> |
---|
47 | <li><strong>Purge history details:</strong> Delete all lines from the |
---|
48 | <code>history</code> table. Screen <span class="pwgScreen">Administration » |
---|
49 | Tools » History</span> will not longer show information for the past |
---|
50 | history. <em>Warning</em>: all data will be lost, without any way to |
---|
51 | get them back.</li> |
---|
52 | |
---|
53 | <li><strong>Purge history summary:</strong> Delete all the summary information about visit history. This summary is calculated from the history details.</li> |
---|
54 | |
---|
55 | <li><strong>Purge sessions:</strong> Delete expired user sessions.</li> |
---|
56 | |
---|
57 | <li><strong>Purge never used notification feeds</strong></li> |
---|
58 | |
---|
59 | <li><strong>Purge searches history</strong></li> |
---|
60 | |
---|
61 | <li><strong>Purge compiled templates</strong></li> |
---|
62 | </ul> |
---|