diff options
author | plegall <plg@piwigo.org> | 2010-03-24 19:34:41 +0000 |
---|---|---|
committer | plegall <plg@piwigo.org> | 2010-03-24 19:34:41 +0000 |
commit | c639ad1e7e3ec747cac37e230fd8380da98c508b (patch) | |
tree | 19ee9852a167074fa76e4e1692adff9ecf24684a /language/hr_HR/help/maintenance.html | |
parent | eafa796d88193b7e8e33d72ae866b0ae9df79e87 (diff) |
copy all languages (exceptions are en_UK and fr_FR) from branch 2.0 to trunk,
then convert the *.lang.php files with tools/convert_language_to_2.1.pl
Next step is to play with tools/translation_analysis.php to find which
language keys need translation for each language.
git-svn-id: http://piwigo.org/svn/trunk@5316 68402e56-0260-453c-a942-63ccdbb3a9ee
Diffstat (limited to '')
-rw-r--r-- | language/hr_HR/help/maintenance.html | 49 |
1 files changed, 49 insertions, 0 deletions
diff --git a/language/hr_HR/help/maintenance.html b/language/hr_HR/help/maintenance.html new file mode 100644 index 000000000..a0d47f7a3 --- /dev/null +++ b/language/hr_HR/help/maintenance.html @@ -0,0 +1,49 @@ +<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 informations become useless with time. Deleting this useless +information from database make you save disk space.</p> + +<ul> + + <li><strong>Update categories informations:</strong> For each category, + informations to update or control are the following : list of parent + categories, number of pictures, date of the last picture, position among + brother categories, position among all categories. This action also checks + the coherence of representative picture.</li> + + <li><strong>Update images informations:</strong> For each picture, + informations to update are : full path to file, average + rate. <em>Warning</em>: do not get confuse with metadata informations + which can be synchronized from <span class="pwgScreen">Administration, + Categories, Synchronize</span> or by reaching the modification screen of a + single picture (through <span class="pwgScreen">Picture</span> for + example).</li> + + <li><strong>Repair and optimize database:</strong> + For each table, re-odrer, repair and optimize operations are done. + </li> +</ul> + +<ul> + <li><strong>Purge history detail:</strong> Delete all lines from + <code>history</code> table. Screen <span class="pwgScreen">Administration, + Specials, History</span> shows no informations anymore on past + history. <em>Warning</em>: all data will be lost and there is no way to + get informations back.</li> + + <li><strong>Purge history summary:</strong> Delete all the summary information about visit history. This summary is calculated from the history detail.</li> + + <li><strong>Purge sessions:</strong> Delete expired user sessions.</li> + + <li><strong>Purge never used notification feeds</strong></li> + + <li><strong>Purge search history</strong></li> + + <li><strong>Purge compiled templates</strong></li> +</ul> |