source: branches/2.4/language/hr_HR/help/maintenance.html @ 16299

Last change on this file since 16299 was 8723, checked in by rvelices, 14 years ago

feature 2102 : rename item/image/picture to photo (admin side)
also removed unnecessary/duplicate keys

  • Property svn:eol-style set to LF
File size: 2.4 KB
Line 
1<h2>Maintenance</h2>
2
3<p>To optimize page generation time, Piwigo uses cached
4information. For example, instead of counting the number of pictures
5contained in each category at each page reload, this information is stored
6in the database. In theory, this information should always be correct, but
7sometimes an error can occur and cached information becomes wrong.</p>
8
9<p>Some informations become useless with time. Deleting this useless
10information from database make you save disk space.</p>
11
12<ul>
13
14  <li>
15    <strong>Nepovezane stavke:</strong>
16    Prikaz slika koje nisu povezane ni s jednom nestvarnom skupinom.
17  </li>
18  <li>
19    <strong>Slike istog naziva u više od jednoj stvarnoj skupini:</strong>
20    Prikaz slika istog naziva koje se nalaze u više skupina.
21  </li>
22
23</ul>
24
25<ul>
26
27  <li><strong>Update categories informations:</strong> For each category,
28  informations to update or control are the following : list of parent
29  categories, number of pictures, date of the last picture, position among
30  brother categories, position among all categories. This action also checks
31  the coherence of representative picture.</li>
32
33  <li><strong>Update photos information:</strong> For each picture,
34  informations to update are : full path to file, average
35  rate. <em>Warning</em>: do not get confuse with metadata informations
36  which can be synchronized from <span class="pwgScreen">Administration,
37  Categories, Synchronize</span> or by reaching the modification screen of a
38  single picture (through <span class="pwgScreen">Picture</span> for
39  example).</li>
40
41  <li><strong>Repair and optimize database:</strong>
42  For each table, re-odrer, repair and optimize operations are done.
43  </li>
44</ul>
45
46<ul>
47  <li><strong>Purge history detail:</strong> Delete all lines from
48  <code>history</code> table. Screen <span class="pwgScreen">Administration,
49  Specials, History</span> shows no informations anymore on past
50  history. <em>Warning</em>: all data will be lost and there is no way to
51  get informations 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 detail.</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 search history</strong></li>
60 
61  <li><strong>Purge compiled templates</strong></li> 
62</ul>
Note: See TracBrowser for help on using the repository browser.