| 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 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><strong>Update categories informations:</strong> For each category, |
|---|
| 15 | the following information is checked, and updated if necessary : list of parent |
|---|
| 16 | categories, number of pictures, last picture date, position among |
|---|
| 17 | brother categories, position among all categories. This action also checks |
|---|
| 18 | the representative picture consistency.</li> |
|---|
| 19 | |
|---|
| 20 | <li><strong>Update images information:</strong> For each picture, |
|---|
| 21 | information updated is : full path to file, average |
|---|
| 22 | rate. <em>Warning</em>, do not mix up: metadata information |
|---|
| 23 | must be synchronized from <span class="pwgScreen">Administration, |
|---|
| 24 | Categories, Synchronize</span>, or on 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 the database:</strong> |
|---|
| 29 | Perform re-order, repair and optimize operations on each table of the database. |
|---|
| 30 | </li> |
|---|
| 31 | </ul> |
|---|
| 32 | |
|---|
| 33 | <ul> |
|---|
| 34 | <li><strong>Purge history details:</strong> Delete all lines from the |
|---|
| 35 | <code>history</code> table. Screen <span class="pwgScreen">Administration, |
|---|
| 36 | Specials, History</span> will not longer show information for the past |
|---|
| 37 | history. <em>Warning</em>: all data will be lost, without any way to |
|---|
| 38 | get them 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 details.</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 searches history</strong></li> |
|---|
| 47 | |
|---|
| 48 | <li><strong>Purge compiled templates</strong></li> |
|---|
| 49 | </ul> |
|---|
