diff options
Diffstat (limited to '')
21 files changed, 0 insertions, 703 deletions
diff --git a/language/en_US/help/cat_modify.html b/language/en_US/help/cat_modify.html deleted file mode 100644 index ce0281523..000000000 --- a/language/en_US/help/cat_modify.html +++ /dev/null @@ -1,133 +0,0 @@ -<h2>Edit album</h2> - -<h3>Informations</h3> - -<ul> - - <li><strong>name</strong>: rename the album (a virtual rename in case - of a physical album).</li> - - <li><strong>description</strong>: short text giving a general idea of the content, - this text will be displayed at the bottom of the thumbnails page.</li> - -</ul> - -<h3>Move</h3> - -<p>If the album is virtual, you can move it. Moving a album means -changing its parent album.</p> - -<h3>Options</h3> - -<ul> - - <li><strong>Access type</strong>: Permissions management. If you make a - album private, all its child albums becomes private. If you make a - album public, all its parent albums becomes public.</li> - - <li><strong>Lock</strong>: The album and its sub-albums will - be temporary disabled for maintenance.</li> - - <li><strong>Comments</strong>: Authorize users to comment photos of this - album.</li> - -</ul> - -<p>You can also manage these options on the "Properties" -management screen (screens <span -class="pwgScreen">Comments</span>, <span class="pwgScreen">Lock</span>, -<span class="pwgScreen">Public/Private</span>, <span -class="pwgScreen">Representative</span> available from <span -class="pwgScreen">Administration » Albums » Properties</span>).</p> - -<h3>Sort order</h3> - -<p>Use the default images sort order.</p> - -<p>Indicate whether this sort order will apply to subalbums also.</p> - -<p>Select specific sorting criteria to be used with this album.</p> -<ul> -<li><strong>Creation date</strong>: Photo shooting date</li> -<li><strong>Post date</strong>: Synchronization date</li> -<li><strong>Average rate (*)</strong>: Average rate could be changed by the visitor rating</li> -<li><strong>Most visited (*)</strong>: The current visit might change the most visited order</li> -<li><strong>File name</strong>: Name given in information field</li> -<li><strong>Id</strong>: Internal Id (recent categories have an higher id than previous ones.</li> - -</ul> -<p><strong>(*)</strong>Warning: Be sure to test these sort orders by yourself as they can give unexpected results.</p> - - -<h3>Representant</h3> - -<p>The album representative is the thumbnail displayed on the main page (<span class="pwgScreen">category.php</span>) to represent -the album when -it contains only sub-albums and no direct photo (just as the root album).</p> -photo of a album :</p> - -<ul> - - <li><span class="pwgScreen">Photo page</span>: one of the action buttons let you set the current photo as the representative for the - displayed album. This button is available only for administrators.</li> - - <li><span class="pwgScreen">Modify informations about a photo</span> in - administration. This screen can be reached from <span - class="pwgScreen">picture.php</span> or <span class="pwgScreen">Batch - management</span> in <em>unit mode</em>. See the help of this screen for - details.</li> - - <li><span class="pwgScreen">Administration » Albums » Properties, - Representative</span>. See the help of this screen for details.</li> - - <li><span class="pwgScreen">Edit album</span> (the present screen).</li> - -</ul> - -<p>The choice of a representative depends on the -<code>allow_random_representative</code> configuration parameter (see <span -class="filename">include/config_default.inc.php</span>).</p> - -<p>In default mode (<code>allow_random_representative</code> set to false), -each album containing at least one element is represented by a fixed -element. Once set (at album creation), the representative changes only -when an administrator ask for it. If the representative is not appropriate, -you can ask to <strong>Find a new representant by random</strong>.</p> - -<p>If the <code>allow_random_representative</code> configuration parameter is -set to true, a category containing photos may have no fixed -representant. Just use <strong>Delete representant</strong> button.</p> - -<p>If the album contains only sub-albums and no photo, it can nonetheless be represented by any element thanks to <span class="pwgScreen">Modify -informations about a photo</span> screen. The only option on the current screen -is the <strong>Delete representant</strong> button.</p> - -<h3>Link all album photos to a new album</h3> - -<ul> - -<li><strong>Virtual album name</strong>: Name of the new album to be created, -all photos of the current category will be linked to the new one.</li> - -<li><strong>Parent album</strong>: Where the new album will be, -leave empty to create it at root.</li> - -</ul> - -<h3>Link all album photos to existing albums</h3> - -<ul> - -<li><strong>Albums</strong>: Choose the destination album.</li> - -</ul> - -<h3>Send an information email to group members</h3> - -<ul> - -<li><strong>Group</strong>: recipients group</li> - -<li><strong>Mail content</strong>: Free text to send to them.</li> - -</ul>
\ No newline at end of file diff --git a/language/en_US/help/cat_move.html b/language/en_US/help/cat_move.html deleted file mode 100644 index 58f31152c..000000000 --- a/language/en_US/help/cat_move.html +++ /dev/null @@ -1,14 +0,0 @@ -<h2>Moving virtual Albums</h2> - -<p>Only virtual albums can have a new parent album.</p> - -<h3>Virtual albums to move</h3> - -<p>Select one or several virtual albums you want to move. -If the list is empty, that mean you have not created one yet.</p> - -<h3>New parent album</h3> - -<p>Select the new parent album (virtual or physical). -If you do not select any parent, the virtual selected albums will be moved to the root. -A album cannot be moved into itself or to one of its child.</p>
\ No newline at end of file diff --git a/language/en_US/help/cat_options.html b/language/en_US/help/cat_options.html deleted file mode 100644 index 11222f344..000000000 --- a/language/en_US/help/cat_options.html +++ /dev/null @@ -1,22 +0,0 @@ -<h2>Album options</h2> - -<p>Options management for several albums at once.</p> - -<dl> - -<dt>Comments</dt> -<dd>A photo can receive comments from your visitors if it belongs to an album with comments activated.</dd> - -<dt>Lock</dt> -<dd>Locked albums are disabled for maintenance. Only administrators can view them in the gallery.</dd> - -<dt>Public / private</dt> -<dd>Once an album become private, give access rights to users and groups</dd> - -<dt>Representative</dt> -<dd>This option is available when you set the configuration setting -<code>allow_random_representative</code> (see <span - class="filename">include/config_defaults.inc.php</span>) to -<em>true</em>. Each album can be represented by a random photo or by a photo chosen as a unique representative.</dd> - -</dl> diff --git a/language/en_US/help/cat_perm.html b/language/en_US/help/cat_perm.html deleted file mode 100644 index cabda09fc..000000000 --- a/language/en_US/help/cat_perm.html +++ /dev/null @@ -1,13 +0,0 @@ -<h2>Edit album permissions</h2> - -<p>This screen is only available for private albums. Here you can select -users and groups authorized for a album.</p> - -<h3>Groups</h3> - -<p>You can deny or grant groups access for the current album. By modifying -groups authorizations, the users belonging to these groups will be denied or granted access to the album.</p> - -<h3>Users</h3> - -<p>You can deny or grant access to individual users. Users that have access through a group can be denied access by exception.</p> diff --git a/language/en_US/help/configuration.html b/language/en_US/help/configuration.html deleted file mode 100644 index cb40e9a9d..000000000 --- a/language/en_US/help/configuration.html +++ /dev/null @@ -1,101 +0,0 @@ -<h2>Configuration</h2> - -<p>This screen let the administrator do basic gallery configuration. Indeed, this screen only shows simple configuration parameters that should be enough for the vast majority of administrators. If you want to see other numerous (and advanced) configuration parameters, read the default configuration file <span -class="filename">include/config_default.inc.php</span>.</p> - -<p>The screen is divided into different sections, grouping configuration parameters by theme.</p> - - -<h3>Main</h3> -<ul> - <li><strong>Gallery title</strong>: used in RSS feed and notifications by email.</li> - - <li><strong>Page banner</strong>: displayed on top of each public page.</li> - - <li><strong>Gallery URL</strong>: used for the RSS feed.</li> - - <li><strong>Lock gallery</strong>: Lock the entire gallery for maintenance. Only administrator users will be able to reach the gallery.</li> - - <li><strong>Rating</strong>: Photo rating feature is enabled.</li> - - <li><strong>Rating by guests</strong>: Even unregistered users can rate images.</li> - - <li><strong>Allow user registration</strong>: Anybody can register.</li> - - <li><strong>Mail address is mandatory for all users</strong>: mail address will be checked on registration or profile update, except if the action is done by an administrator.</li> - - <li><strong>Email admins when a new user registers</strong>: administrators will be notified by mail for each registration.</li> - - <li><strong>Default photos order</strong>: you can define a personalized order with these drop-down menus.</li> - -</ul> - -<h3>History</h3> - - <p>Visits on pages <span - class="pwgScreen">category.php</span> and <span - class="pwgScreen">picture.php</span> will be saved in the <code>history</code> table.</p> - - <p>Visits will be shown in <span class="pwgScreen">Administration » Tools » History</span>.</p> - -<ul> - <li><strong>Save page visits by guests</strong>: page visits by guests will be recorded.</li> - - <li><strong>Save page visits by users</strong>: visits by registrered users will be recorded.</li> - - <li><strong>Save page visits by administrators</strong>: page visits by administrators will be recorded.</li> - -</ul> - -<h3>Comments</h3> -<ul> - - <li><strong>Comments for all</strong>: Even unregistered guest can post comments.</li> - - <li><strong>Number of comments per page</strong>.</li> - - <li><strong>Validation</strong>: an administrator must validate users comments before they become visible on the site. User comments validation - takes place in screen <span class="pwgScreen">Administration » Tools » Pending Comments</span>.</li> - - <li><strong>Email admins when a valid comment is entered</strong>: Sends an email to the administrators when a user enters a comment and this comment is validated.</li> - - <li><strong>Email admins when a comment requires validation</strong>: -Sends an email to the administrators when a user enters a comment that requires validation by the admin. -User comments validation takes place in the screen <span class="pwgScreen">Administration » Tools » Pending Comments</span>.</li> - -</ul> - -<h3>Default display</h3> - -<p>Here you can change display options used by guest, the default user that is not connected. Once connected, these options are overridden by the user's own options -(modifiable in <span class="pwgScreen">profile</span>).</p> - -<p>It is possible to change the display options for all existing users on the <span class="pwgScreen">Administration » -Users » Manage</span> screen where you can select a list of users.</p> - -<ul> - - <li><strong>Language</strong>: Apply to Piwigo labels only. Album names, photo names and all descriptions fields are not localized.</li> - - <li><strong>Number of photos per row</strong></li> - - <li><strong>Number of rows per page</strong></li> - - <li><strong>Interface theme</strong></li> - - <li><strong>Recent period</strong>: By days. Period during which a photo is shown as new. Must be greater than 1 day.</li> - - <li><strong>Expand all albums</strong>: Expand all albums by - default in the menu <em>Warning</em>: this option is resources intensive and may generate a huge menu if your album tree contains many albums.</li> - - <li><strong>Show number of comments</strong>: Show the number of comments for each photo on the thumbnails page. Resource intensive.</li> - - <li><strong>Show hits count</strong>: Display hits observed on photo just under its thumbnail on the thumbnails page. Only when advanced configuration parameter is: <br> - $conf['show_nb_hits'] = true; <br> - Notice: false by default.</li> - - <li><strong>Maximum width of the photos</strong>: maximum displayed width. Photos larger than this setting will be resized on display. Rather than choosing this option, you might consider modifying the width of your photos; that would be a better practice.</li> - - <li><strong>Maximum height of the photos</strong>: Same as for the maximum width setting.</li> - -</ul>
\ No newline at end of file diff --git a/language/en_US/help/extend_for_templates.html b/language/en_US/help/extend_for_templates.html deleted file mode 100644 index a46f94779..000000000 --- a/language/en_US/help/extend_for_templates.html +++ /dev/null @@ -1,51 +0,0 @@ -<h2>Template Extension Configuration</h2> - -<h3>About</h3> -<p>Your Piwigo gallery can be customised by replacing existing template files with customised versions. For example, the default header template (header.tpl) can be replaced by a customised header template (my-header.tpl). After submitting the changes to the database the gallery will display the customised header instead of the original header.<br> -Template extensions are a powerful way to create customised themes for both new and advanced users. Used together with the LocalFiles Editor you can create your own child themes.</p> - -<h3>Original Template</h3> -<p>A theme contains a number of template files that make up the gallery pages. These are the original templates.</p> - -<h3>Optional URL Keyword</h3> -<p>These are words found in the gallery URL after the module name. They can also be active permalinks (See the permalink documentation for more information). <a href="#warnings">WARNING:</a> if the same original template and same keyword is used on more than one customised template only the last one is active.</p> - -<h3>Bound Theme</h3> -<p>The bound theme is the theme from which the template files are being replaced.</p> - -<h3>Where are the original templates?</h3> -<p>Original templates are the template files shipped with each theme. These are saved in <em>/themes/default/template</em> (or <em>themes/<theme name>/template</em>). These template files should not be edited in place as changes will be lost with theme upgrades.<br> -Supported original templates include:</p> -<ul> - <li><span class="filename">index.tpl</span></li> - <li><span class="filename">mainpage_categories.tpl</span> and/or <span class="filename">thumbnails.tpl</span></li> - <li><span class="filename">menubar.tpl</span></li> - <li><span class="filename">header.tpl</span> and/or <span class="filename">footer.tpl</span></li> - <li><span class="filename">picture_content.tpl</span> and/or <span class="filename">picture.tpl</span></li> - <!-- <li><span class="filename">slideshow.tpl</span></li> --> - <li><span class="filename">profile.tpl</span> and/or <span class="filename">profile_content.tpl</span></li> - <li><span class="filename">tags.tpl</span></li> - <li><span class="filename">upload.tpl</span></li> - <li><span class="filename">about.tpl</span></li> - <li><span class="filename">popuphelp.tpl</span></li> - <li><span class="filename">search.tpl</span> and/or <span class="filename">search_rules.tpl</span></li> - <li><span class="filename">nbm.tpl</span> and/or <span class="filename">notification.tpl</span></li> - <li><span class="filename">identification.tpl</span> and/or <span class="filename">register.tpl</span></li> - <li><span class="filename">redirect.tpl</span></li> -</ul> -<h3>Saving customised templates</h3> -<p>Customised templates should be saved in the template-extension folder or subfolders. For example, <em>/template-extension/my-default/header.tpl</em> (or <em>/template-extension/<my-theme-name>/header.tpl</em>) Template files can have any name with a .tpl extension. The template files in subfolders appear in the Template configuration screen as available custom templates.</p> -<h3>Activating customised templates</h3> -<p>Select the original template to replace. Optionally choose a URL keyword to ensure that the customised template is only shown on pages with that keyword. Select a bound theme and the changes will be effective on that theme. Submit the changes to the database.</p> -<h3>Deactivating customised templates</h3> -<p>Unselect the original template and submit the changes to the database.<br> -Delete the customised template files from the template-extension folder.</p> - -<a name="warnings"></a> -<h3>Warnings</h3> -<ul> - <li><strong>The original template</strong> must be the original template otherwise you may have unpredictable results.</li> - <li>If the same original template and same URL keyword is used on more than one customised template only the last one is active.</li> - <li>Distributed sample template files are for test purposes only. Do not edit them. Create your own ones or copy existing theme template files into <em>/template-extension/<my-theme>/</em></li> - <li>When the customised template is deleted the original template file is immediately reactivated.</li> -</ul>
\ No newline at end of file diff --git a/language/en_US/help/group_list.html b/language/en_US/help/group_list.html deleted file mode 100644 index eeae61d4c..000000000 --- a/language/en_US/help/group_list.html +++ /dev/null @@ -1,22 +0,0 @@ -<h2>Groups list</h2> - -<p>This is the place where you manage groups.</p> - -<h3>Add a group</h3> - -<p>Administrator can add groups.</p> - -<h3>Groups list</h3> - -<p>For each group the following actions can be applied:</p> - - -<ul> - <li>go to user management (Admin » Users » Manage)</li> - <li>go to permissions management screen to grant or deny access to private albums.</li> - <li>delete the group (requires a confirmation)</li> - <li>toggle status "default" (requires a confirmation)</li> -</ul> - -<h3>Default groups</h3> -<p>Default groups are groups that are automatically associated to each new user upon registration or creation by an administrator.</p> diff --git a/language/en_US/help/help_add_photos.html b/language/en_US/help/help_add_photos.html deleted file mode 100644 index 8a8841141..000000000 --- a/language/en_US/help/help_add_photos.html +++ /dev/null @@ -1,27 +0,0 @@ -<p>Several ways to add your photos in your gallery:</p> - -<ul> - <li><strong>Direct upload</strong> inside your web browser is the - simplest and most immediate way. It depends on your browser capabilities - and your web server. For a huge quantity of photos or in case you encounter some problem, - the other methods are just waiting for you!</li> -</ul> - -<p class="nextStepLink"><a href="admin.php?page=photos_add§ion=direct">Go to Direct Upload </a></p> - -<ul> - <li><strong>pLoader</strong> is a desktop application, to be installed on your computer. Drag & drop photos into pLoader window, click on <em>"Upload to Piwigo"</em> and let pLoader do the job. You can find other desktop applications such as <strong>WinToPiwigo</strong> or the <strong>Digikam</strong> export plugin to Piwigo.</li> -</ul> - -<p class="nextStepLink"><a href="admin.php?page=photos_add§ion=ploader">Go to pLoader</a></p> - -<div id="helpSynchro"> -<ul> - <li><strong>FTP transfer</strong> is the most recommended way to add a - very large collection of photos with a minimum number of clicks. Follow - the guide to prepare your photos. The FTP method let you control precisely - the physical organization of your photos on your server.</li> -</ul> - -<p class="nextStepLink"><a href="admin.php?page=photos_add§ion=ftp">Go to FTP</a></p> -</div>
\ No newline at end of file diff --git a/language/en_US/help/help_groups.html b/language/en_US/help/help_groups.html deleted file mode 100644 index aed7d7a8e..000000000 --- a/language/en_US/help/help_groups.html +++ /dev/null @@ -1,11 +0,0 @@ -<p>Groups are a convenient way to set permissions for a list of users.</p> - -<p>Create groups in <span class="pwgScreen">Administration » Users -» Groups</span> and associate users to this group -in <span class="pwgScreen">Administration » Users » -Manage</span>.</p> - -<p>A user can belong to several groups. Authorization takes precedence over -interdiction : if user "jack" belongs to groups "family" and "friends", and -that only group "family" can see album "Christmas 2010" album then -"jack" will be able to see "Christmas 2010".</p> diff --git a/language/en_US/help/help_misc.html b/language/en_US/help/help_misc.html deleted file mode 100644 index c46e82aaa..000000000 --- a/language/en_US/help/help_misc.html +++ /dev/null @@ -1,9 +0,0 @@ -<p>Once you created your gallery you can configure it for your visitor -<ul> - <li>The default display as you like in <span class="pwgScreen">Administration » Configuration » Options</span> tab <span class="pwgScreen">Guest Settings</span></li> - <li>The default theme in <span class="pwgScreen">Administration » Configuration » Themes</span></li> - <li>The default language in <span class="pwgScreen">Administration » Configuration » Languages</span></li> - </ul> - By default, each new user will inherit these properties upon registration. -</p> -<p>If you have any question, Piwigo community will welcome you on <a href="http://piwigo.org/forum">its forum</a>.</p>
\ No newline at end of file diff --git a/language/en_US/help/help_permissions.html b/language/en_US/help/help_permissions.html deleted file mode 100644 index 600d541ac..000000000 --- a/language/en_US/help/help_permissions.html +++ /dev/null @@ -1,57 +0,0 @@ -<fieldset> -<legend>Permissions on photos</legend> - -<p>Each photo has a <strong>privacy level</strong> (a lock). Each user also has a privacy level (a key). There are 5 privacy levels:</p> -<ol> - <li>None</li> - <li><em>Contacts</em></li> - <li><em>Friends (which is higher than a contact)</em></li> - <li><em>Family (which is higher than a friend)</em></li> - <li><em>Admins (which is higher than any other level)</em></li> -</ol> - -<p>Higher levels have permissions on lower levels. For a given user, the higher the privacy level, the more photos he can see.</p> - -<p>For example, if photo "peter_wedding-0024.jpg" has <em>"Family"</em> privacy level, then:</p> -<ul> - <li>Peter (who is an <em>"Admin"</em>) will see the photo because <em>"Admins"</em> can see all photos</li> - <li>Beth (who is a <em>"Family"</em> member) will also see the photo</li> - <li>Mary (who is just a <em>"Friend"</em>) won't see the photo</li> -</ul> - -<p>A user that has no permission to see the content of a album won't see the album itself, not even its title. The same principle applies to a tag.</p> - -<p>You can set the privacy level of a user on <span class="pwgScreen">Administration » Users » Manage</span> screen.</p> - -</fieldset> - -<fieldset> -<legend>Permissions on albums</legend> - -<p>If privacy levels do not fit your needs, you can also manage permissions on albums for a user or a group. You can manage permissions on photos and albums at the same time, without conflict.</p> - -<p>You can forbid access to albums. Switch the album access type to -"private" if you want to manage permissions.</p> - -<p>You can set a album to private by editing a single album -(<span class="pwgScreen">Administration » Albums » Manage -» edit</span>) or by setting options to your whole album tree -(<span class="pwgScreen">Administration » Albums » -Properties » Public / Private</span>).</p> - -<p>Once the album is private, you can manage permissions for groups and -users with 3 screens:</p> - -<ul> - - <li><span class="pwgScreen">Administration » Users » Manage » - permissions action</span> (one link per user)</li> - - <li><span class="pwgScreen">Administration » Users » Groups » - permissions action</span> (one link per group)</li> - - <li><span class="pwgScreen">Administration » Albums » Manage » edit - album permissions action</span> (one link per album)</li> - -</ul> -</fieldset> diff --git a/language/en_US/help/help_virtual_links.html b/language/en_US/help/help_virtual_links.html deleted file mode 100644 index f6b5ca84d..000000000 --- a/language/en_US/help/help_virtual_links.html +++ /dev/null @@ -1,12 +0,0 @@ -<p>Photos are displayed in the album corresponding to their file -directory.</p> - -<p>You can also display a photo in several albums, without duplicating -the file on your web server. Associate the photo to any album from the -photo editing screen (that any administrator can reach from the photo page -on the gallery side).</p> - -<p>Virtual albums are based on this concept: they have no corresponding -directory. Create virtual albums -from <span class="pwgScreen">Administration » Albums » -Manage</span>.</p> diff --git a/language/en_US/help/history.html b/language/en_US/help/history.html deleted file mode 100644 index 701b2de10..000000000 --- a/language/en_US/help/history.html +++ /dev/null @@ -1,22 +0,0 @@ -<h2>History</h2> - -<p>On these screens, you can monitor your gallery visits history according to the options you have chosen in: Administration » Configuration » Options » History</p> - -<h3>Statistics</h3> -<ul> - <p>If you have chosen to record the pages visited (<span class="pwgScreen">index.php</span> and <span class="pwgScreen">picture.php</span>), you can monitor them from this tab.</p> - <li><strong>Global statistics</strong>: visits per year. </li> - <li><strong>Yearly statistics</strong>: visits per month in the selected year .</li> - <li><strong>Monthly statistics</strong>: visits per days in the selected month .</li> - <li><strong>Daily statistics</strong>: visits per hours in the selected day.</li> -</ul> - -<h3>Search</h3> -<ul> - <p>If you have chosen to record the pages visited (<span class="pwgScreen">index.php</span> and <span class="pwgScreen">picture.php</span>), you can browse the details from this tab with the help of different filters.</p> - <li><strong>Filter by date:</strong> select the date range to search by setting start and end dates.</li> - <li><strong>Filter by type of element:</strong> select the type of element for statistics on that element.</li> - <li><strong>Filter by user:</strong> select the user for statistics on that user.</li> - <li><strong>Filter by image identifier:</strong> select the image identifier for statistics on that image.</li> - <li><strong>Filter by name of the file:</strong> select the file name for statistics on that file..</li> -</ul>
\ No newline at end of file diff --git a/language/en_US/help/index.php b/language/en_US/help/index.php deleted file mode 100644 index 41732f2fd..000000000 --- a/language/en_US/help/index.php +++ /dev/null @@ -1,30 +0,0 @@ -<?php -// +-----------------------------------------------------------------------+ -// | Piwigo - a PHP based photo gallery | -// +-----------------------------------------------------------------------+ -// | Copyright(C) 2008-2013 Piwigo Team http://piwigo.org | -// | Copyright(C) 2003-2008 PhpWebGallery Team http://phpwebgallery.net | -// | Copyright(C) 2002-2003 Pierrick LE GALL http://le-gall.net/pierrick | -// +-----------------------------------------------------------------------+ -// | This program is free software; you can redistribute it and/or modify | -// | it under the terms of the GNU General Public License as published by | -// | the Free Software Foundation | -// | | -// | This program is distributed in the hope that it will be useful, but | -// | WITHOUT ANY WARRANTY; without even the implied warranty of | -// | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU | -// | General Public License for more details. | -// | | -// | You should have received a copy of the GNU General Public License | -// | along with this program; if not, write to the Free Software | -// | Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, | -// | USA. | -// +-----------------------------------------------------------------------+ - -// Recursive call -$url = '../'; -header( 'Request-URI: '.$url ); -header( 'Content-Location: '.$url ); -header( 'Location: '.$url ); -exit(); -?> diff --git a/language/en_US/help/maintenance.html b/language/en_US/help/maintenance.html deleted file mode 100644 index 671c92ce6..000000000 --- a/language/en_US/help/maintenance.html +++ /dev/null @@ -1,26 +0,0 @@ -<h2>Maintenance</h2> - -<p>To optimise page generation time Piwigo uses cached information. For example, instead of counting the number of photos contained in each album 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 out of date.</p> - -<p>Some information becomes less useful as time goes by. Deleting this useless information from the database will save you some disk space.</p> - -<ul> - <li><strong>Delete orphan tags</strong></li> -</ul> -<ul> - <li><strong>Update albums informations:</strong> For each album, the following information is checked, and updated if necessary : list of parent albums, number of photos, last photo date, position among brother albums, position among all albums. This action also checks the representative photos consistency.</li> - <li><strong>Update photos information:</strong> For each photo, information updated is : full path to file, average rate. <em>Warning</em>, do not mix up: metadata information must be synchronised from <span class="pwgScreen">Administration » Tools » synchronise</span>, or on the modification screen of a single photo (through <span class="pwgScreen">Photo</span> for example).</li> -</ul> -<ul> - <li><strong>Repair and optimise the database:</strong>Perform re-order, repair and optimise operations on each table of the database.</li> - <li><strong>Reinitialize integrity check</strong></li> -</ul> - -<ul> - <li><strong>Purge history details:</strong> Delete all lines from the history table. Screen <span class="pwgScreen">Administration » Tools » History</span> will not longer show information for the past history. <em>Warning:</em> all data will be lost, without any way to get them back.</li> - <li><strong>Purge history summary:</strong> Delete all the summary information about visit history. This summary is calculated from the history details.</li> - <li><strong>Purge sessions:</strong> Delete expired user sessions.</li> - <li><strong>Purge never used notification feeds</strong></li> - <li><strong>Purge searches history</strong></li> - <li><strong>Purge compiled templates</strong></li> -</ul>
\ No newline at end of file diff --git a/language/en_US/help/notification_by_mail.html b/language/en_US/help/notification_by_mail.html deleted file mode 100644 index da9ac2a97..000000000 --- a/language/en_US/help/notification_by_mail.html +++ /dev/null @@ -1,15 +0,0 @@ -<h2>Notification By Mail (NBM)</h2> - -<p>Configure and manage email notifications to users notifying them of changes to your site.</p> - -<p>This screen comprises three tabs:</p> - -<h3>Settings</h3> -<p>Available only for webmasters, this tab sets the notification by mail parameters.</p> - -<h3>Subscribe</h3> -<p>Available only for webmasters, this tab manages a user's subscription to email notifications. Add users to the subscribed box for them to receive notifications by mail.</p> - -<h3>Send</h3> -<p>Available only for webmasters and administrators, this tab allows administrators to send notification emails to subscribed users.</p> - diff --git a/language/en_US/help/permalinks.html b/language/en_US/help/permalinks.html deleted file mode 100644 index fc4949237..000000000 --- a/language/en_US/help/permalinks.html +++ /dev/null @@ -1,7 +0,0 @@ -<h2>Permalinks</h2> - -<p>Permalinks are used to make album urls nicer. When a album has a permalink defined, the id of the album is not required anymore in the url.</p> - -<p>When a permalink is deleted, you can save it in the permalink history, so that external links to Piwigo pages still work. In the permalink history table you can see the date when the permalink has been deleted, the last time it was used and the number of times this permalink has been used.</p> - -<p>Note that permalinks must be unique per album. Also in the permalink history you cannot have the same permalink defined more than once.</p> diff --git a/language/en_US/help/photos_add_ftp.html b/language/en_US/help/photos_add_ftp.html deleted file mode 100644 index 3d39f1e63..000000000 --- a/language/en_US/help/photos_add_ftp.html +++ /dev/null @@ -1,70 +0,0 @@ -<fieldset> - <legend>Quick Start</legend> - -<ol> - <li>Create a directory on your computer.</li> - - <li>Copy some photos inside this directory, resize them for web display. <em>Warning</em>: the name of directories and files must contain only letters, figures, "-", "_" or ".". No blank space, nor accentuated characters.</li> - - <li>With a FTP client, copy your directory in the "galleries" directory of your Piwigo installation.</li> - - <li>Logon your gallery and go to <span class="pwgScreen">Administration</span> and click on the big Synchronization button.</li> -</ol> - -<p>Congratulations! You have successfully created the first album of your photo gallery.</p> -</fieldset> - -<fieldset> - <legend>Directories and files organization</legend> - -<ul> - - <li> - - <p>Album directories are in the Piwigo directory - "galleries". Here follows the directory tree of a very small gallery (but - using many features):</p> - - <pre> -galleries -|-- wedding -| |-- celebration -| | |-- arrival -| | | |-- paul-alone.jpg -| | | +-- sarah-alone.jpg -| | +-- departure -| | +-- paul-and-sarah.jpg -| +-- party -| |-- dancers001.jpg -| |-- dancers002.jpg -| +-- dancers003.jpg -+-- honeymoon - |-- hotel.png - |-- video-from-plane.avi - +-- pwg_representative - +-- video-from-plane.jpg -</pre> - - </li> - - <li>Except for "pwg_representative" (see explanations below), each directory under "galleries" produces a album. There is no limit on deepness.</li> - - <li>Basically, an element is represented by a file. A file can be a - Piwigo element if its extension is among <code>file_ext</code> - configuration parameter possibilities (see <span - class="filename">include/config_default.inc.php</span> file). A file can - be a picture if its extension is among <code>picture_ext</code> - configuration parameter possibilities.</li> - - <li>No photo elements (video, sounds, file texts, whatever you want...) are represented by default by an icon corresponding to the filename - extension. Optionally, you can associate a thumbnail and a representative - file (see video.avi in the example above).</li> - - <li><em>Warning</em>: the name of directories and files must contain only letters, figures, "-", "_" or ".". No blank space, nor accentuated characters.</li> - - <li>Once photos are correctly placed in the - directories, go to: <span class="pwgScreen">Administration » Tools » - Synchronize</span></li> - -</ul> -</fieldset> diff --git a/language/en_US/help/search.html b/language/en_US/help/search.html deleted file mode 100644 index ae1330a31..000000000 --- a/language/en_US/help/search.html +++ /dev/null @@ -1,24 +0,0 @@ -<h2>Search</h2> - -<p>This page let you search photos among the whole gallery.</p> - -<dl> - - <dt>Search for words</dt> - <dd>Search for one or several words among the attributes related to the photos - of the gallery. Use * as a wildcard for partial matches.</dd> - - <dt>Search for an author</dt> - <dd>Use * as a wildcard for partial matches.</dd> - - <dt>Search by date</dt> - <dd>Select a date and/or an ending date for your query. Leave date field empty - if you want to make a "before" query. The year in the last - field must be entered in the following format : AAAA (i.e. 2004)</dd> - - <dt>Search in albums</dt> - <dd>Select album or albums you wish to search. All - sub-albums can be searched by selecting the parent album and setting enable - search sub-albums below.</dd> - -</dl> diff --git a/language/en_US/help/synchronize.html b/language/en_US/help/synchronize.html deleted file mode 100644 index 7eac01a6a..000000000 --- a/language/en_US/help/synchronize.html +++ /dev/null @@ -1,14 +0,0 @@ -<h2>Synchronise</h2> - -<p>There are two different types of synchronisation:</p> -<ul> - <li>directories/files</li> - <li>file metadata</li> -</ul> - -<p>Synchronising directories and files is about updating your directories tree with the album tree in the database. -Synchronising file metadata is about updating photo information, such as filesize, dimensions in pixels, EXIF or IPTC information, in the database.</p> - -<p>When synchronising your uploads with your gallery you must first synchronise directories and files.</p> - -<p>The synchronisation process may take a long time (depending on server load and the number of elements to manage) so it is possible to do it album by album.</p>
\ No newline at end of file diff --git a/language/en_US/help/user_list.html b/language/en_US/help/user_list.html deleted file mode 100644 index 371facf87..000000000 --- a/language/en_US/help/user_list.html +++ /dev/null @@ -1,23 +0,0 @@ -<h2>Users list</h2> - -<p>This is where you manage the users of your Piwigo gallery.</p> - -<h3>Add a user</h3> - -<p>An administrator can add users manually. For each user create a username, a password and submit a valid email address.</p> - -<h3>Users list</h3> - -<p>The list of existing users can be filtered on username (use * as wildcard), group or status. It can be ordered by registration date or username, in ascending or descending order.</p> - -<p>This screen allows the management of several users at once, using different actions:</p> - -<ul> - <li>delete users (requires confirmation)</li> - <li>change the status of the user</li> - <li>associate or dissociate from groups</li> - <li>modify display properties</li> - <li>modify additional preferences</li> -</ul> - -<p>The target is the selected user (by default) or all users as displayed in the filtered list.</p>
\ No newline at end of file |