File: /home/freeval/public_html/e-cards/docs/index_es.htm
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Foto Galer�a Coppermine - Documentaci�n & Manual</title>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
<meta name="language" content="en">
<meta name="author" content="Coppermine dev team">
<meta name="copyright" content="Coppermine dev team">
<meta name="description" content="Coppermine Photo Gallery project - Coppermine is an easily set-up, fast, feature-rich photo gallery script with mySQL base de datos, user management, private galleries, automatic thumbnail creation, ecard feature and a template system for easy customization to match the rest of a site.">
<meta name="keywords" content="photo gallery,galery,image,Coppermine,php,mysql,easy,feature,thumbnail,automatic,creation,gd,Image Magick,ecard">
<meta name="page-topic" content="photo gallery,galery,image,Coppermine,php,mysql,easy,feature,thumbnail,automatic,creation,gd,Image Magick,ecard">
<meta http-equiv="Content-Style-Type" content="text/css">
<meta name="MSSmartTagsPreventParsing" content="true">
<meta http-equiv="imagetoolbar" content="no"><!-- SVN version info: $Id: index.htm 3305 2006-10-16 02:46:59Z nibbler999 $ -->
<!--
Subversion information (for information and developer purposes only - safe to ignore for everybody else):
Coppermine version: 1.4.27
$HeadURL: https://coppermine.svn.sourceforge.net/svnroot/coppermine/trunk/cpg1.4.x/docs/index.htm $
$Revision: 4392 $
$Author: gaugau $
$Date: 2008-04-16 09:25:35 +0200 (Mi, 16 Apr 2008) $
-->
<link rel="stylesheet" type="text/css" href="style.css">
</head>
<body>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tbody>
<tr>
<td>
<p><img src="../images/coppermine_logo.png" alt="Coppermine Photo Gallery - Your Online Photo Gallery">
</p><h1>Foto Galer�a Coppermine v1.4.x: Documentaci�n y Manual</h1>
<h1>Sobre Coppermine</h1>
<p>Coppermine Photo Gallery es una galer�a de fotos avanzada, de f�cil
uso y con soporte para otros tipos de archivos (media/datos). La
galer�a puede ser privada, accesible solo a usuarios registrados o
disponible para todos los visitantes de su sitio web. Los usuarios, si
les est� permitido, pueden: subir im�genes a trav�s de su navegador
(las miniaturas y las im�genes de tama�o intermedio son creadas
autom�ticamente), valorarlas, agregar comentarios e incluso enviar
postales. El administrador del sitio web (en adelante "administrador")
decide cu�les de las caracter�sticas mencionadas son accesibles para
los usuarios registrados y no registrados. El administrador puede
tambi�n manejar galer�as y procesar en lote gran cantidad de im�genes
que hayan sido subidas el servidor por FTP.</p>
<p>Los archivos de imagen son almacenadas en �lbumes y los
�lbumes pueden ser agrupados en categor�as, las cuales, a su vez,
pueden ser reagrupadas bajo categor�as padre. El script soporta
m�ltiples usuarios y le provee al administrador las herramientas
necesarias para determinar qu� grupo de usuarios puede o no puede
realizar distintas acciones, como por ejemplo: crear �lbumes
personales, subir im�genes a los �lbumes p�blicos, enviar postales,
agregar comentarios, valorar las im�genes, etc.</p>
<p>Coppermine posee un sistema de selecci�n de temas (aspecto visual)
por parte del usuario y varios temas pre-instalados. Tambi�n admite el
uso de m�ltiples idiomas y contiene su propia librer�a idiom�tica. Esto
permite que sus usuarios utilicen la galer�a en su idioma preferido.
Coppermine utiliza PHP, una base de datos MySQL y la librer�a GD
(versi�n 1.x o 2.x) o ImageMagik para generar y guardar la informaci�n
de todas las im�genes (miniaturas, tama�o intermedio y tama�o
completo). Coppermine genera din�micamente el c�digo html necesario
para mostrar las categor�as, sub-categor�as, �lbumes e im�genes. Esto
reduce dr�sticamente la cantidad de archivos y espacio que su galer�a
necesitar�a utilizando HTML com�n. El script instalador (install.php)
permite comenzar a utilizar la galer�a de una manera r�pida y sencilla.</p>
<a name="top"></a>
<div id="toc">
<h1>Tabla de contenidos</h1>
<!--<ul class="level1">
<li class="level1"><a href="#testVersion" class="menu1">0. Beta (Testing) version</a></li>
</ul>-->
<ul class="level1">
<li class="level1"><a href="#what" class="menu1">1. Requerimientos</a></li>
</ul>
<ul class="level1">
<li class="level1"><a href="#installation" class="menu1">2. Instalaci�n y Configuraci�n</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#how" class="menu2">2.1 Como instalar el script</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#permissions">2.1.1 Estableciendo permisos</a></li>
</ul>
<ul class="level4">
<li class="level4"><a href="#permissions_chmod">2.1.1.1 Apache en Unix/Linux (CHMOD)</a></li>
<li class="level4"><a href="#permissions_apache_windows">2.1.1.2 Apache en Windows</a></li>
<li class="level4"><a href="#permissions_iis_windows">2.1.1.3 IIS en Windows</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#install_screen_start">2.1.2 La pantalla de instalaci�n</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#getting" class="menu2">2.2 Comenzando</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#creating" class="menu2">2.3 Creando o actualizando sus propios temas</a></li>
<li class="level2"><a href="#safe" class="menu2">2.3 Cuestiones del modo seguro (Safe mode)</a></li>
<li class="level2"><a href="#smtp" class="menu2">2.5 Utilizando SMTP para enviar correos</a></li>
</ul>
<ul class="level1">
<li class="level1"><a href="#upgrade" class="menu1">3. Actualizando</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#10" class="menu2">3.1 Actualizando desde la versi�n 1.0</a></li>
<li class="level2"><a href="#11" class="menu2">3.2 Actualizando desde lanzamientos de la versi�n 1.1</a></li>
<li class="level2"><a href="#12" class="menu2">3.3 Actualizando desde cpg1.2.0rc2 o cpg1.2.0final a la versi�n cpg1.2.1</a></li>
<li class="level2"><a href="#13" class="menu2">3.4 Actualizando desde cpg1.2.x o cpg1.3.x a la versi�n cpg1.4.19</a></li>
<li class="level2"><a href="#14" class="menu2">3.5 Actualizando desde cpg1.4.0 (o m�s reciente) a la versi�n cpg1.4.19</a></li>
<li class="level2"><a href="#versioncheck" class="menu2">3.6 La herramienta comprobadora de versi�n (version check tool)</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#versioncheck_description_start">3.6.1 What it does</a></li>
<li class="level3"><a href="#versioncheck_options_start">3.6.2 Options</a></li>
<li class="level3"><a href="#versioncheck_comparison_start">3.6.3 Version comparison</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#downgrading" class="menu2">3.7 Downgrading from cpg1.4.x</a></li>
</ul>
<ul class="level1">
<li class="level1"><a href="#administration" class="menu1">4. Configuration & Administration</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#cat_alb_pic" class="menu2">4.1 Categories, albumes and archivos</a></li>
<li class="level2"><a href="#admin_user_mode" class="menu2">4.2 Admin mode & User mode</a></li>
<li class="level2"><a href="#group_cp" class="menu2">4.3 The group control panel</a></li>
<li class="level2"><a href="#user_cp" class="menu2">4.4 The user control panel</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#user_cp_page">4.4.1 Page controls</a></li>
<li class="level3"><a href="#user_cp_search">4.4.2 Searching for user(s)</a></li>
<li class="level3"><a href="#user_cp_new">4.4.3 Creating new users</a></li>
<li class="level3"><a href="#user_cp_edit">4.4.4 Editing users</a></li>
<li class="level3"><a href="#user_cp_group">4.4.5 Group membership</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#cat_cp" class="menu2">4.5 The category control panel</a></li>
<li class="level2"><a href="#albmgr" class="menu2">4.6 The �lbum manager</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#albmgr_create">4.6.1 Creating albumes</a></li>
<li class="level3"><a href="#albmgr_rename">4.6.2 Renaming albumes</a></li>
<li class="level3"><a href="#albmgr_order">4.6.3 Changing the �lbum order</a></li>
<li class="level3"><a href="#albmgr_delete">4.6.4 Deleting albumes</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#modif_alb_pics" class="menu2">4.7 Modifying �lbum/archivos</a></li>
<li class="level2"><a href="#album_prop" class="menu2">4.8 Album properties</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#album_prop_reset_start">4.8.1 Reset �lbum properties</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#edit_pics" class="menu2">4.9 Editing archivos</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#edit_vids">4.9.1 Editing videos</a></li>
<li class="level3"><a href="#cust_thmb">4.9.2 Custom thumbnails</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#bbcode" class="menu2">4.10 Using bbcode to insert enlaces and format in descriptions</a></li>
<li class="level2"><a href="#uploading" class="menu2">4.11 Uploading pics/archivos</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#batch_add_pics">4.11.1 Uploading pics by FTP / Batch-Add Pictures</a></li>
<li class="level3"><a href="#upload_http">4.11.2 Uploading by HTTP</a></li>
<li class="level3"><a href="#xp">4.11.3 Using Windows XP Web Publishing Wizard with Coppermine</a></li>
</ul>
<ul class="level4">
<li class="level4"><a href="#xp_publish_setup">4.11.3.1 XP Web Publishing Wizard: Setup</a></li>
<li class="level4"><a href="#xp_publish_upload">4.11.3.2 XP Web Publishing Wizard: Uploading pictures</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#upload_trouble">4.11.4 Upload troubleshooting</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#admin" class="menu2">4.12 The gallery p�gina de configuraci�n</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#admin_general">4.12.1 General settings</a></li>
<li class="level3"><a href="#admin_language">4.12.2 Language & Charset settings</a></li>
<li class="level3"><a href="#admin_tema">4.12.3 Themes settings</a></li>
<li class="level3"><a href="#admin_album_list">4.12.4 Album list view</a></li>
<li class="level3"><a href="#admin_thumbnail_view">4.12.5 Thumbnail view</a></li>
<li class="level3"><a href="#admin_image_comment">4.12.6 Image view</a></li>
<li class="level3"><a href="#admin_comment_start">4.12.7 Comment settings</a></li>
<li class="level3"><a href="#admin_picture_thumbnail">4.12.8 Archivo and thumbnail settings</a></li>
<li class="level3"><a href="#admin_picture_thumb_advanced">4.12.9 Archivos and thumbnails advanced settings</a></li>
<li class="level3"><a href="#admin_user">4.12.10 User settings</a></li>
<li class="level3"><a href="#admin_custom">4.12.11 Custom fields for user proarchivo</a></li>
<li class="level3"><a href="#admin_custom_image">4.12.12 Custom fields for image description</a></li>
<li class="level3"><a href="#admin_cookie">4.12.13 Cookie settings</a></li>
<li class="level3"><a href="#admin_email">4.12.14 Email settings</a></li>
<li class="level3"><a href="#admin_logging">4.12.15 Logging & statistics</a></li>
<li class="level3"><a href="#admin_misc">4.12.16 Miscellaneous settings</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#exif" class="menu2">4.13 EXIF data</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#exif_manager">4.13.1 The EXIF manager</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#plugin" class="menu2">4.14 Plugins</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#plugin_definition">4.14.1 What is a plugin?</a></li>
<li class="level3"><a href="#plugin_api">4.14.2 The Plugin API</a></li>
<li class="level3"><a href="#plugin_manager">4.14.3 The Plugin Manager</a></li>
</ul>
<ul class="level4">
<li class="level4"><a href="#plugin_manager_upload">4.14.3.1 Uploading a plugin</a></li>
<li class="level4"><a href="#plugin_manager_install">4.14.3.2 Installing a plugin</a></li>
<li class="level4"><a href="#plugin_manager_configuration">4.14.3.3 Plugin Configuration</a></li>
<li class="level4"><a href="#plugin_manager_uninstall">4.14.3.4 Uninstalling a plugin</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#plugin_writing">4.14.4 Writing plugins</a></li>
</ul>
<ul class="level1">
<li class="level1"><a href="#integrating" class="menu1">5. Integrating the script with your bulletin board</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#integrating_bridge_start" class="menu2">5.1 Available bridge archivos</a></li>
<li class="level2"><a href="#integrating_prerequisites_start" class="menu2">5.2 Pre-requistes</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#integrating_cookie_start">5.2.1 Authentication by cookie</a></li>
<li class="level3"><a href="#integrating_standalone_start">5.2.2 Standalone versi�n first</a></li>
<li class="level3"><a href="#integrating_users_start">5.2.3 Coppermine users, groups and pics uploaded by users are lost when integrating</a></li>
<li class="level3"><a href="#integrating_backup_start">5.2.4 Backup</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#integrating_steps_start" class="menu2">5.3 Integration steps</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#bridge_manager_start">5.3.1 Using the bridge manager</a></li>
</ul>
<ul class="level4">
<li class="level4"><a href="#bridge_manager_app_start">5.3.1.1 choose application to bridge Coppermine with</a></li>
<li class="level4"><a href="#bridge_manager_path_start">5.3.1.2 path(s) used by your BBS app</a></li>
<li class="level4"><a href="#bridge_manager_specific_start">5.3.1.3 BBS-specific settings</a></li>
<li class="level4"><a href="#bridge_manager_enable_start">5.3.1.4 enable/disable BBS integration</a></li>
</ul>
<ul class="level3">
<li class="level3"><a href="#bridge_manager_recover_start">5.3.2 Recover from failed bridging</a></li>
<li class="level3"><a href="#integrating_steps_sync_start">5.3.3 Synchronising the bbs groups with Coppermine's groups</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#integrating_support_start" class="menu2">5.4 Bridging support</a></li>
</ul>
<ul class="level1">
<li class="level1"><a href="#translating" class="menu1">6. Translating Coppermine into other languages</a></li>
</ul>
<ul class="level1">
<li class="level1"><a href="#known_issues" class="menu1">7. Known Issues</a></li>
</ul>
<ul class="level1">
<li class="level1"><a href="#credits" class="menu1">8. Credits</a></li>
</ul>
<ul class="level2">
<li class="level2"><a href="#developers" class="menu2">8.1 Coppermine team</a></li>
<li class="level2"><a href="#contributors" class="menu2">8.2 Contributors</a></li>
<li class="level2"><a href="#codebase" class="menu2">8.3 Code used in Coppermine</a></li>
<li class="level2"><a href="#copyright" class="menu2">8.4 License</a> (Copyright & disclaimer)</li>
</ul>
</div><!-- end toc -->
<hr>
<a name="testVersion"></a>
<!--
<h1>0. Beta (Testing) version</h1>
<p>Dear Tester,</p>
<p>Thank you for taking the time to test Coppermine Photo Gallery. Please be rough on the program so that we can track down and eliminate bugs from our public release of version 1.4.</p>
<p>Please understand that this is still beta software that is meant to be used for testing purposes and not for production, so there is no support for cpg1.4.2 yet.</p>
<p>While testing CPG 1.4, please make certain to note any odd behavior you encounter. This could include typographical errors, misleading instructions, or any other out-right error. If you encounter a major error, please switch the debug mode to "on" in the configuration panel and copy the text in the debug window. This will greatly aid the development team in hunting down the problem.</p>
<p><strong>Areas to be particularly mindful of:</strong></p>
<ul>
<li>Please test every facet of CPG, from the installation on to every feature available (and in as many temas and languages as possible).</li>
<li>If you have the ability to test GD, GD2 and ImageMagick, please test all of them.</li>
<li>Please attempt to use multiple types of graphics such as JPEG, PNG and GIF (for ImageMagick and GD 2.0.28+ users).</li>
</ul>
<p>Please report your test results to the <a href="http://Coppermine.sourceforge.net/board/index.php?board=29.0">testing board</a>, but before starting a new thread aseg�rese that the potential bug you're going to report hasn't been posted before.</p>
<p><strong>The report format should include:</strong></p>
<ul>
<li>Server OS</li>
<li>Web Server Software</li>
<li>GD, GD2 or ImageMagick Test</li>
<li>PHP Version</li>
<li>BB Integration (if any)</li>
<li>Themes fully tested (by fully tested, we mean as many different features as possible using that tema)</li>
<li>Major Errors</li>
<li>Client OS and Browser</li>
<li>Fresh install or upgrade (if upgrade, from which version of cpg)</li>
</ul>
<p>Your test results will not merely be used to fix problems but will also be used to tout the compatibility of CPG with multiple browsers and OS's. That is why this information is important EVEN IF YOU FIND NOTHING WRONG.</p>
<p>Thanks for your participation and your time in making CPG the premiere open-source photo gallery!</p>
<p>Coppermine Development Team</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr />
-->
<a name="what"></a>
<h1>1. Requerimientos</h1>
<ul>
<li>Un servidor web que soporte PHP.</li>
<li>Una base de datos MySQL.<br>
Necesitar� MySQL versi�n 3.23.23 o posterior. MySQL 4.1 es la
recomendada, MySQL 5 es soportada. El usuario MySQL necesita tener
permisos para CREAR, MODIFICAR, SELECCIONAR, ACTUALIZAR, BORRAR e
INSERTAR informaci�n en la base de datos. La mayor�a de los usuarios
adquieren estos permisos cuando se alojan en un hosting. Si no posee
estos permisos no podr� utilizar esta galer�a u otro script similar. Si
tiene dudas sobre el estado de sus permisos conf�rmelos contact�ndose
con su proveedor de hosting. La mayor�a de estos proveedores podr�n
decirle si Coppermine puede o no funcionar en sus servidores.<br>
La base de datos debe estar creada para que Coppermine pueda usarla –
el script instalador no la crea, pero s� crear� las tablas y la
estructura de datos por usted. La mayor�a de los servicios de
alojamiento web brindan, al menos, una base de datos ya configurada. De
no ser as�, necesitar� crearla. En ese caso, consulte el procedimiento
necesario con su proveedor de hosting. Tenga a mano el nombre de su
base de datos, el nombre de usuario y la contrase�a ya que Coppermine
necesitar� estos datos para instalarse exitosamente.</li>
<li>PHP
(versi�n 4.2.0 o posterior), compilado con soporte para la librer�a GD
o permiso de utilizar la funci�n exec() para la utilidad “convert” de
ImageMagick, para poder crear las miniaturas y reducir las im�genes.</li>
<li>Una librer�a de im�gen: GD versi�n 1.x o 2.x (PHP debe estar compilado para soportarla) o ImageMagick.<br>
(vea <a href="http://www.f64foto.com.ar/CPG/faq.htm#whatIsImageMagick">Qu� es ImageMagick</a> y <a href="http://www.f64foto.com.ar/CPG/faq.htm#WhatIsGD">Qu� es GD</a>)</li>
<li>Es
una buena idea contactar primero con su proveedor de hosting y
preguntarle si conoce alg�n problema relacionado con la instalaci�n de
Coppermine.</li>
</ul>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="installation"></a>
<h1>2. Instalaci�n y Configuraci�n </h1>
<a name="how"></a>
<h2>2.1 Como instalar el script</h2>
<ul>
<li><strong>Descomprima el archivo manteniendo la estructura de los directorios.</strong><br>Puede renombrar el directorio Coppermine pero no los archivos ni los directorios dentro de �ste.</li>
<li><strong>Suba todos los archivos a su servidor web</strong> (aseg�rese de utilizar el modo ftp correcto).</li>
<li><strong>Utilizando el comando CHMOD <a href="#permissions">establezca los permisos</a> a 755</strong> (o 777, dependiendo de la configuraci�n en su servidor) <strong>a los directorios "<em>albums</em>" e "<em>include</em>" dentro de su directorio Coppermine.</strong> <span class="important">Este paso es muy importante y no debe ser pasado por alto!</span></li>
<li><strong>Posea la informaci�n necesaria y correcta sobre su base de datos:</strong> Ud. <em>debe saber</em>
la ruta (path) hacia el servidor de la base de datos (generalmente es
'localhost'), el nombre de la base de datos como as� tambi�n los
detalles del usuario MySQL y contrase�a con los que Coppermine deber�a
conectarse con la misma. La base de datos y el nombre de usuario deben
ya existir, y el usuario debe tener acceso a ella. Coppermine no crear�
la base de datos, pero crear� las tablas necesarias durante la
instalaci�n; no hay necesidad que usted agregue ninguna tabla.</li>
<li><strong>Ejecute el script instalador en su servidor:</strong> en la barra de direci�n de su navegador de internet escriba <tt class="code">http://su_servidor/directorio_Coppermine/install.php</tt> y siga las instrucciones que aparecer�n en la pantalla, escribiendo la informaci�n necesaria cuando sea solicitada. (<em>su_servidor</em> = su sitio web - <em>directorio_Coppermine</em> = el directorio en donde ha subido los archivos de Coppermine)</li>
</ul>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="permissions"></a>
<h3>2.1.1 Estableciendo permisos</h3>
Coppermine necesita <em>acceso de escritura</em> a ciertos archivos y directorios en el servidor para poder realizar lo siguiente:
<ul>
<li>Durante la instalaci�n, Coppermine necesita crear y escribir el
archivo "config.inc.php" en el directorio "include" con el fin de
almacenar la informaci�n necesaria de acceso a mySQL para ejecutar
Coppermine y para crear y escribir el archivo "install.lock", tambi�n
en el mismo directorio, para impedir que el instalador intente
ejecutarse una segunda vez despu�s de una instalaci�n exitosa.</li>
<li>Al subir los archivos por HTTP, Coppermine necesita ir
escribi�ndolos en los subdirectorios que usted o sus usuarios hayan
creado en el directorio <em>albums</em> de Coppermine.</li>
<li>Indistintamente del m�todo utilizado para subir los archivos al
servidor, Coppermine crear� un archivo de miniatura y un archivo
intermedio y los almacenar� en un subdirectorio dentro del directorio <em>albums</em>.</li>
</ul>
<p>Por defecto, los archivos y directorios en un servidor est�n
protegidos contra escritura, as� es que probablemente se deber�n
cambiar los permisos antes de la instalaci�n, por los motivos antes
mencionados. Es totalmente obligatorio que usted modifique (CHMOD)
estos permisos - o se le presentar�n problemas tarde o temprano.</p>
<p>Para ser capaz de establecer los permisos correctamente debe comprender c�mo funcionan: existen los permisos de <em><strong>r</strong>ead</em> (lectura), <em><strong>w</strong>rite</em> (escritura) y <em>e<strong>x</strong>ecute</em> (ejecuci�n) -abreviados como <strong>rwx</strong>-
para cada archivo y directorio. Los permisos en un directorio padre se
pueden propagar a un directorio hijo o a los archivos dentro de �l,
aunque tambi�n es posible evitar que los permisos no deseados se
propaguen.</p>
<p>Sin embargo, existen diferencias entre los distintos sistemas
operativos utilizados como servidores web. Ya que Coppermine est�
dise�ado para poder ejecutarse en varios de los distintos sistemas,
hemos incluido algunas instrucciones b�sicas. Aquellas personas
conocedoras del tema pueden encontrar estas instrucciones un poco
generalizadas y faltas de detalles.<br>Nota: no importa su computadora
o su configuraci�n, lo importante es el sistema operativo utilizado en
su servidor web. Si no est� seguro qu� sistema operativo se est�
ejecutando en su servidor web, intente primero con las instrucciones de
CHMOD ya que la mayor�a de los servidores web utilizan alguna versi�n
de Unix/Linux. <span class="important">Si no es capaz de comprender la metodolog�a, pida ayuda a su proveedor de hosting.</span></p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="permissions_chmod"></a>
<h4>2.1.1.1 Apache en Unix/Linux (CHMOD)</h4>
<ul>
<li><strong>B�sico</strong><br>
Existen distintos paquetes de Unix/Linux pero todos ellos comparten
algunas similitudes. Refiri�ndonos a esta arquitectura, la palabra
"Lunix" es utilizada por ambos Unix y Linux derivados. Permisos de
"Lectura" (Read) se aplica a los archivos que no est�n actualmente
ejecut�ndose, por ej. texto o archivos html. Los permisos de
"Escritura" (Write) son necesarios para crear archivos din�micamente,
modificarlos o borrarlos. Los permisos de "Ejecuci�n" (Execute) sirven
para ejecutar archivos, por ejemplo: scripts en PHP. Para servir
adecuadamente p�ginas web basadas en PHP, los servicios b�sicos
necesitados al menos son lo de "lectura" y "ejecuci�n" (abreviados como
r-x).<br>
Los par�metros posibles para permisos son:
<ul>
<li><tt class="code">r--</tt> ... solo lectura</li>
<li><tt class="code">r-x</tt> ... lectura y ejecuci�n</li>
<li><tt class="code">rwx</tt> ... lectura, escritura y ejecuci�n</li>
</ul>
Obviamente, otras combinaciones son t�cnicamente posibles (por ejemplo:
-wx, --x o -w-), pero no tienen mucho sentido en lo que se refiere a
configuraciones en servidores web por lo que ser�n ignoradas en este
tutorial.</li>
<li><strong>Grupos en Lunix</strong><br>
Lunix utiliza conjunto de permisos en "grupos de a tres", cada uno de
los cuales puede ser aplicada independientemente. Ellos son: <em>propietario</em> (owner), <em>grupo</em> (group) y <em>mundo</em>
(world). De esta manera puede especificar si un usuario due�o de un
archivo tiene permiso para modificarlo o borrarlo (permiso de
escritura) mientras que los dem�s usuarios solo podr�n verlo y
posiblemente, ejecutarlo. En su propio servidor, estos par�metros de
permisos para los tres grupos posibles est�n escritos en una sola l�nea
(en el �rden "propietario", "grupo", "mundo"). <br>
Ejemplos:
<ul>
<li><tt class="code">rwxrwxrwx</tt> ... permisos de lectura, escritura y ejecuci�n (rwx) para los tres grupos.</li>
<li><tt class="code">rwxr-xr-x</tt> ... permisos rwx para el propietario, permisos r-x para los dem�s.</li>
<li><tt class="code">r-xr-xr-x</tt> ... solo permisos de lectura y ejecuci�n para todos los grupos.</li>
</ul>
</li>
<li><strong>Daemon del Servidor Web</strong><br>
A�n cuando usted (el usuario due�o de los archivos en su servidor y el
que tiene el control sobre los permisos) pueda acceder a un archivo
(ej. usando una aplicaci�n FTP), quiz�s el script Coppermine no sea
capaz de hacerlo. Esto es generalmente causado por una opci�n de
configuraci�n en particular de los servidores: servicios (en Lunix
frecuentemente son llamados "daemons") que pueden ejecutarse en el
contexto de un usuario espec�fico y que es distinto del usuario que
tiene acceso a los archivos. En muchos de estos servidores, el servicio
de servidor web (apache) se ejecuta como el usuario "nadie" (nobody).
De esta manera, el servidor puede ser protegido contra los ataques de
los hackers. Por lo tanto, los par�metros de permisos en un servidor
para el "propietario" no funcionar�n en estas configuraciones
particulares, entonces, usted deber� fijar los permisos para ambos:
"grupo" y "mundo" (al menos para el grupo al que pertenece el daemon
del servidor web).</li>
<li><strong>Aritm�tica binaria</strong><br>
As you can see, permissions can be either "on" or "off" - this is the
equivalent to the two different states that a bit of data can have in
binary arithmetics (and therefore, also in the whole world of
computing).
As we have three types of different permissions (read, write, execute),
we will need three bits to assign a set of permissions. The highest bit
is the "<em><strong>r</strong>ead</em>" bit - decimal "4" is used to represent it. The middle bit "<em><strong>w</strong>rite</em>" is assigned to decimal "2", the lowest bit "<em>e<strong>x</strong>ecute</em>"
is represented by decimal "1".
This may be a bit hard to understand or follow at first, especially if
you haven't dealt with binary arithmetics before. If you would like to
learn more, google for it. It's easier to understand if you look at
some examples:
<div style="float: left; margin-right: 10px;">
<table class="maintable" border="0" cellpadding="0" cellspacing="0">
<tbody><tr><td class="tableh1">permission</td><td class="tableh1">bit value</td><td class="tableh1">set?</td><td class="tableh1">value</td></tr>
<tr><td class="tableb">read</td><td class="tableb">4</td><td class="tableb"><input checked="checked" onclick="javascript:this.checked=true" type="checkbox"></td><td class="tableb">4</td></tr>
<tr><td class="tableb">write</td><td class="tableb">2</td><td class="tableb"><input checked="checked" onclick="javascript:this.checked=true" type="checkbox"></td><td class="tableb">2</td></tr>
<tr><td class="tableb">execute</td><td class="tableb">1</td><td class="tableb"><input checked="checked" onclick="javascript:this.checked=true" type="checkbox"></td><td class="tableb">1</td></tr>
<tr><td colspan="3" class="tablef">sum (resulting byte value)</td><td class="tablef">7</td></tr>
</tbody></table>
</div>
<div style="float: left; margin-right: 10px;">
<table class="maintable" border="0" cellpadding="0" cellspacing="0">
<tbody><tr><td class="tableh1">permission</td><td class="tableh1">bit value</td><td class="tableh1">set?</td><td class="tableh1">value</td></tr>
<tr><td class="tableb">read</td><td class="tableb">4</td><td class="tableb"><input checked="checked" onclick="javascript:this.checked=true" type="checkbox"></td><td class="tableb">4</td></tr>
<tr><td class="tableb">write</td><td class="tableb">2</td><td class="tableb"><input onclick="javascript:this.checked=false" type="checkbox"></td><td class="tableb">-</td></tr>
<tr><td class="tableb">execute</td><td class="tableb">1</td><td class="tableb"><input checked="checked" onclick="javascript:this.checked=true" type="checkbox"></td><td class="tableb">1</td></tr>
<tr><td colspan="3" class="tablef">sum (resulting byte value)</td><td class="tablef">5</td></tr>
</tbody></table>
</div>
<div style="float: left; margin-right: 10px;">
<table class="maintable" border="0" cellpadding="0" cellspacing="0">
<tbody><tr><td class="tableh1">permission</td><td class="tableh1">bit value</td><td class="tableh1">set?</td><td class="tableh1">value</td></tr>
<tr><td class="tableb">read</td><td class="tableb">4</td><td class="tableb"><input checked="checked" onclick="javascript:this.checked=true" type="checkbox"></td><td class="tableb">4</td></tr>
<tr><td class="tableb">write</td><td class="tableb">2</td><td class="tableb"><input checked="checked" onclick="javascript:this.checked=true" type="checkbox"></td><td class="tableb">2</td></tr>
<tr><td class="tableb">execute</td><td class="tableb">1</td><td class="tableb"><input onclick="javascript:this.checked=false" type="checkbox"></td><td class="tableb">-</td></tr>
<tr><td colspan="3" class="tablef">sum (resulting byte value)</td><td class="tablef">6</td></tr>
</tbody></table>
</div>
<div style="clear: left;"></div>
</li>
<li><strong>�Qu� tiene de bueno todo esto?</strong><br>
Instead of having to remember and write <tt class="code">rwxrwxrwx</tt> for each archivo or directorio in your setup, you can now write <tt class="code">777</tt> in its place. The same applies for <tt class="code">rwxr-xr-x</tt>, you can write <tt class="code">755</tt>, instead.</li>
<li><strong>Aplicaci�n FTP</strong><br>Setting the permissions using
your FTP application will be the option available for most users who
are proveedor de hostinged. Depending on the FTP app you use, the user
interface will slightly differ: some apps will allow you to enter the
CHMOD command by entering the numbers (777 or 755), others will provide
you with checkboxes where you can tick the permissions separately for
each group. More advanced FTP apps may even provide you with both
mechanisms. As this documentation can't cover all individual FTP apps
that are available, the exact method might differ a bit from what you
have.<br>
Your FTP app will probably have two windows, one showing your local
archivos, the other one showing the archivos on your servidor. In the
window that shows the remote archivos on the servidor, navigate to the
directorio your Coppermine archivos reside in. Highlight the "albumes"
directorio that resides within the Coppermine directorio. From the
context menu (right-click!), choose "properties" (might be named
"chmod" or similar as well). The permissions dialog will then pop up.
Choose the proper permissions as suggested above (777 or 755, depending
on your servidor setup). If you have a checkbox that enables the
permissions to propagate for all sub-directorios and archivos, tick it.
If you don't have it, nevermind. Then click "OK" on the dialog box to
apply the permissions. Keep in mind that your FTP app might not have
the power to actually find out about the current permissions that <strong>are</strong>
applied, so you mustn't trust the information displayed in the dialog
box: even if it appears that the permissions are already set as needed,
this may not be the case, so you should re-apply the permissions no
matter what.<br>
After having applied the permissions for the albumes directorio, do the
same thing for the include directorio that resides within your
Coppermine directorio.</li>
<li><strong>Panel de control del sitio web</strong><br>
Some proveedor de hostings may not give you the option to access your
site using FTP, or they may not allow your FTP client to execute the
CHMOD command. If this is the case, you probably have a servidor setup
interface (e.g. cpanel) to apply permission to directorios and
archivos. In fact, this doesn't matter, the method for applying
permissions doesn't differ from the one described above in the section
"FTP application": navigate to the albumes directorio and apply the
permissions needed to give your webservidor write access to all
archivos and directorios within the albumes directorio. Do the same
thing for the include directorio as well.</li>
<li><strong>Shell access</strong><br>
If you have shell access to your servidor, you can apply the native <a href="http://www.die.net/doc/linux/man/man1/chmod.1.html" rel="external" class="external">CHMOD</a>
command on your archivos and directorios. Go to your Coppermine
directorio using your shell access, then apply the permissions to the
albumes and include directorio and everything within it. As explained
above, the user the apache daemon runs under needs write access, so you
should CHMOD to 777 or 755, depending on your servidor setup.</li>
</ul>
<a name="permissions_chmod_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="permissions_apache_windows"></a>
<h4>2.1.1.2 Apache en Windows</h4>
<p>Debe comprender que no existe CHMOD en los sistemas operativos
Windows - este comando est� solamente disponible en Unix/Linux aunque
su aplicaci�n FTP muestre las opciones CHMOD. Si intenta aplicar CHMOD
en Windows, el comando ser� simplemente ignorado. Sin embargo los
permisos tambi�n existen en Windows.</p>
<p>En Apache, el servicio de Servidor se ejecuta bajo un usuario en
particular - si usted tiene acceso completo al servidor revise el
control de servicios para averiguar cu�l es o de lo contrario consulte
con su proveedor de hosting.</p>
<p>Como medida temporal, establezca los permisos en directorios y archivos tal como se explica en la secci�n <a href="#permissions_iis_windows">IIS en Windows</a>,
aunque no para el IUSR (el cual solo existe en IIS), pero si para
"todos" (everyone). Sin embargo, permitiendo que "todos" tengan
permisos de lectura, escritura y ejecuci�n puede ser un riesgo de
seguridad y no es para nada recomendado.</p>
<a name="permissions_apache_windows_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="permissions_iis_windows"></a>
<h4>2.1.1.3 IIS en Windows</h4>
<p>Requisitos previos: necesitar� privilegios de administrador
completos para llevar a cabo este proceso. Si usted no es el encargado
del servidor, probablemente su proveedor de hosting haya puesto a su
disposici�n una interface en l�nea que le permita cambiar los permisos.
Si no est� seguro, contacte con su proveedor de hosting.</p>
<p>Dependiendo de la versi�n de Windows que posea, los cuadros de di�logo pueden diferir levemente:</p>
<ul>
<li>En su servidor, utilice el Explorador de Windows y navegue hasta el directorio de Coppermine.</li>
<li>Haga click con el bot�n derecho del mouse sobre el directorio al que quiere cambiar los permisos.</li>
<li>Elija "Propiedades" (Properties).</li>
<li>En el cuadro de Propiedades, marque la pesta�a "Seguridad" (Security).</li>
<li>Seleccione el usuario "Cuenta de Internet invitado (guest account
(hostname\IUSR_hostname)). Si no existe, utilice el comando
"Agregar..." (Add) para crear este usuario.</li>
<li>Marque la casilla de verificaci�n "Permitir" (Allow) accesos de "Escritura" (Write).</li>
<li>Presione el bot�n "Avanzado" (Advanced).</li>
<li>Para asegurarse de que el acceso de escritura se propaga a todos
los subdirectorios y archivos que est�n dentro del directorio que est�
editando, marque la casilla de verificaci�n "Restablecer permisos de
todos los objetos hijos y habilitar la propagaci�n hereditaria de
permisos".</li>
<li>Click en "OK"</li>
<li>Responda "SI" en el cuadro de di�logo de confirmaci�n que le pregunta si todos los permisos deber�n ser reemplazados.</li>
<li>Dependiendo de la cantidad de objetos hijos y de la velocidad de su
sistema, espere hasta que todos los permisos de todos los objetos hayan
sido cambiados y la ventana de estado desaparezca.</li>
<li>Click en "OK" para cerrar el cuadro de di�logo de permisos.</li>
</ul>
<p>Debe comprender que no existe CHMOD en los sistemas operativos
Windows - este comando est� solamente disponible en Unix/Linux aunque
su aplicaci�n FTP muestre las opciones CHMOD. Si intenta aplicar CHMOD
en Windows, el comando ser� simplemente ignorado. Sin embargo los
permisos tambi�n existen en Windows.</p>
<a name="permissions_iis_windows_end"></a>
<a href="http://www.f64foto.com.ar/CPG/permissions_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="install_screen_start"></a>
<h3>2.1.2 La pantalla de instalaci�n</h3>
<table border="0" cellpadding="5" cellspacing="0">
<tbody><tr>
<td style="border-top: 1px solid rgb(14, 114, 164); border-left: 1px solid rgb(14, 114, 164); border-right: 1px solid rgb(14, 114, 164);" colspan="2"><strong>Your admin account</strong> </td>
<td></td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164); border-right: 1px solid rgb(14, 114, 164);" colspan="2"> <span class="small">This
section requires information to create your administration account. Use
only alphanumeric characters. Enter the data carefully !</span> </td>
<td><span class="small">Invente
e ingrese un nombre de usuario administrador y una contrase�a en este
campo. Memorice estos datos o escr�balos en alg�n lugar seguro. Si
olvida o pierda esta informaci�n no podr� administrar su galer�a.</span></td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164);" width="20%"><strong>Username</strong> </td>
<td style="border-right: 1px solid rgb(14, 114, 164);" width="20%">
<input style="width: 100%;" readonly="readonly" name="admin_username" value="" type="text"> </td>
<td valign="top" width="60%"><span class="small">Este
ser� el nombre de usuario para su administraci�n diaria de Coppermine.
Elija uno sencillo de recordar pero tenga en cuenta que esta entrada es
sensible a may�sculas y min�sculas. Las im�genes que suba a trav�s de
esta cuenta de administrador mostrar�n el nombre elegido en el campo
"propietario", como as� tambi�n los comentarios que realice.</span></td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164);"><strong>Password</strong> </td>
<td style="border-right: 1px solid rgb(14, 114, 164);">
<input style="width: 100%;" readonly="readonly" name="admin_password" value="" type="text"> </td>
<td><span class="small">Esta
ser� su contrase�a de administrador. No utilice una demasiado sencilla
o trivial ya que si un atacante la deduce o la obtiene, �l/ella ser�
capaz de controlar su sitio. Use una combinaci�n de letras, n�meros y
caracteres especiales como por ej." j3e4n5n6y* " y recuerde que esta
entrada tambi�n es sensible a may�sculas y min�sculas.</span> </td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164);"><strong>Email address</strong> </td>
<td style="border-right: 1px solid rgb(14, 114, 164);">
<input style="width: 100%;" readonly="readonly" name="admin_email" value="" type="text"> </td>
<td><span class="small">Esta
direcci�n de correo ser� utilizada para enviar correos desde el
servidor (ej: verificaci�n de registro, notificaciones y postales).
Aseg�rese de especificar una direcci�n v�lida.</span></td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164); border-right: 1px solid rgb(14, 114, 164);" colspan="2"><strong>Your MySQL configuration</strong> </td>
<td rowspan="2"><span class="small">MySQL
es el tipo de base de datos disponible en la mayor�a de los servidores.
Si no la tiene no podr� instalarla a menos que el servidor sea de su
propiedad. Es obligatorio tener una base de datos mySQL para ejecutar
Coppermine o cualquier otro script basado en PHP. Usted no puede
falsificar la informaci�n de mySQL durante la instalaci�n... <strong>debe conocerla</strong> de antemano. Si tiene dudas contacte con su proveedor de hosting.</span></td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164); border-right: 1px solid rgb(14, 114, 164);" colspan="2"><span class="small">This
section requires information on how to access your MySQL database. If
you don't know how to fill them, check with your webhost support.</span> </td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164);"><strong>MySQL Host</strong><br><span class="small">(localhost is usually OK)</span> </td>
<td style="border-right: 1px solid rgb(14, 114, 164);" valign="top">
<input style="width: 100%;" readonly="readonly" name="dbservidor" value="localhost" type="text"> </td>
<td><span class="small"></span></td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164);"><strong>MySQL Database Name</strong> </td>
<td style="border-right: 1px solid rgb(14, 114, 164);">
<input style="width: 100%;" readonly="readonly" name="dbname" value="" type="text"> </td>
<td><span class="small">Coppermine <strong>no</strong>
crear� la base de datos por Usted. Debe existir antes de cualquier
intento por instalar el script. Si no tiene la base de datos, deber�
crearla (si es que dispone de los privilegios para poder hacerlo en su
servidor).</span></td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164);"><strong>MySQL Username</strong> </td>
<td style="border-right: 1px solid rgb(14, 114, 164);">
<input style="width: 100%;" readonly="readonly" name="dbuser" value="" type="text"> </td>
<td><span class="small">El nombre de usuario de mySQL <strong>no</strong>
tiene que ser el mismo nombre de usuario administrador de Coppermine,
ni necesariamente el mismo nombre de usuario FTP (aunque este <em>puede</em> ser el caso de algunos usuarios, solo por pura coincidencia o deliberadamente, para simplificar la administraci�n del sitio).<br>
El usuario de mySQL necesita permisos para CREAR TABLAS, INSERTAR, ALTERAR, ACTUALIZAR, BORRAR, SELECCIONAR.</span></td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164);"><strong>MySQL Password</strong> </td>
<td style="border-right: 1px solid rgb(14, 114, 164);">
<input style="width: 100%;" readonly="readonly" name="dbpass" value="" type="text"> </td>
<td><span class="small">La contrase�a para el usuario de mySQL.</span></td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164);"><strong>MySQL table prefix</strong><br><span class="small">(the default value is OK; do not use dots!)</span> </td>
<td style="border-right: 1px solid rgb(14, 114, 164);" valign="top">
<input style="width: 100%;" readonly="readonly" name="table_prefix" value="cpg140_" type="text"> </td>
<td><span class="small">Las
tablas de Coppermine pueden co-existir en una base de datos que ya
contenga tablas usadas por otras aplicaciones. Todas las tablas de
Coppermine usar�n un prefijo diferente a las dem�s, como el
especificado aqu�. Usted puede tener varias instalaciones de Coppermine
utilizando una sola base de datos - solamente los prefijos de las
tablas deben diferir en cada caso. A menos que sepa lo que est�
haciendo, no cambie el valor que viene por defecto.</span></td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164); border-right: 1px solid rgb(14, 114, 164);" colspan="2"><strong>ImageMagick</strong> </td>
<td rowspan="3" valign="top"><span class="small">No puede falsificar la ruta hacia ImageMagick, <em>debe conocerla</em>.
Si no est� seguro, deje este campo vac�o - Coppermine intentar�
utilizar la librer�a GD. Puede modificar la ruta despu�s en la <a href="#admin_picture_thumb_advanced">pantalla de configuraci�n</a>.
Usted puede instalar ImageMagick o GD si el servidor es de su
propiedad, pero si est� en un hosting, probablemente no. El usuario del
servidor que desea utilizar ImageMagick, necesitar� permisos de
lectura/escritura/ejecuci�n en el directorio donde residen los archivos
ejecutables de conversi�n de ImageMagick.</span></td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164); border-right: 1px solid rgb(14, 114, 164);" colspan="2" valign="top"><span class="small">Coppermine can use the <a href="http://www.imagemagick.org/" rel="external" class="external">ImageMagick</a> 'convert' program to create thumbnails. Quality of images produced by ImageMagick is superior to GD1 but equivalent to GD2.<br><br>
If ImageMagick is installed on your system and you want to use it, you
need to input the full path to the 'convert' program below. On Windows
the path should look like 'c:/ImageMagick/' (use / not \ in the path)
and should not contain any space, on Unix is it something like
'/usr/bin/X11/'.</span> </td>
</tr>
<tr>
<td style="border-left: 1px solid rgb(14, 114, 164);" valign="top"><strong>ImageMagick path</strong> </td>
<td style="border-right: 1px solid rgb(14, 114, 164);" valign="top">
<input style="width: 100%;" readonly="readonly" name="impath" value="" type="text"> </td>
</tr>
<tr>
<td colspan="2" style="border-left: 1px solid rgb(14, 114, 164); border-right: 1px solid rgb(14, 114, 164); border-bottom: 1px solid rgb(14, 114, 164);" align="center"><br>
<input value="Let's Go !" type="submit"><br><br> </td>
<td><span class="small">Luego de haber introducido toda la informaci�n requerida, presione este bot�n para enviar el formulario.</span></td>
</tr>
</tbody></table>
<a name="install_screen_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="getting"></a>
<h2>2.2 Comenzando</h2>
<p>Identif�quese (log in) con el nombre de usuario y contrase�a
especificados durante la instalaci�n, pulse en el enlace "admin mode"
si est� visible, dir�jase a la p�gina <strong>Configuraci�n</strong>
(Config) y comience a configurar su galer�a. Tenga en cuenta que aunque
usted pertenezca al grupo de los administradores necesita estar en el
"modo administrador" (admin mode) para poder configurar la galer�a.</p>
<p>Existen algunos par�metros que no podr�n ser cambiados despu�s (si
es que existen archivos en la base de datos) - aseg�rese de fijarlos
correctamente la primera vez. Aunque seguramente querr� comenzar a
utilizar su galer�a inmediatamente, es recomendable configurar algunos
par�metros (marcados con un asterisco "*") adecuadamente al principio.</p>
<p>Utilice el "<strong><a href="#albmgr">Administrador de �lbum</a></strong>"
(Album Manager) (el enlace "Albumes" en el men� del administrador) para
crear y ordenar sus �lbumes. Necesitar� al menos un �lbum para subir
sus archivos en �l.</p>
<p>Utilice el grupo <strong>an�nimos</strong> (anonymous) para definir lo que los usuarios no registrados pueden o no pueden hacer. (desde el panel <a href="#group_cp">grupos</a> (groups)).</p>
<p>Utilice las <strong><a href="#modif_alb_pics">propiedades</a></strong> (properties) de un �lbum para modificar su descripci�n y permisos.</p>
<p>Para que un usuario pueda subir archivos a un �lbum, se deben presentar dos condiciones:</p>
<ul>
<li>El usuario debe pertenecer de un <a href="#group_cp">grupo</a> que pueda subir archivos.</li>
<li>Debe existir al menos un �lbum donde la opci�n "<strong>Visitantes pueden subir archivos</strong>" haya sido fijada en "<strong>Si</strong>",<br> <strong>o</strong> <br>que el usuario haya creado un �lbum en las 'galer�as de usuarios' (user galleries), si le fu� permitido.</li>
</ul>
<p>Lo mismo se aplica para <strong>valorar im�genes</strong> (picture rating) y para <strong>publicar comentarios</strong> (comment posting).</p>
<p>Si ha instalado el script exitosamente pero est� teniendo problemas para hacerlo funcionar correctamente, puede habilitar el "<strong><a href="#debug_mode">modo de depuraci�n</a></strong>" (debug mode) en la p�gina <strong> Configuraci�n</strong>.
En este modo, el script muestra la mayor�a de los mensajes de error
producidos por PHP. Esto proporciona valiosa informaci�n para poder
comprender qu� es lo que est� mal.</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="creating"></a>
<h2>2.3 Creando o actualizando sus propios temas</h2>
<p>Para actualizar un tema personalizado a la versi�n 1.4.x, lea la documentaci�n <a href="http://www.f64foto.com.ar/CPG/theme/index.html"> actualizar tema</a>.</p>
<p>Los temas de Coppermine est�n almacenados en el directorio "<strong>themes</strong>", cada uno consiste de 3 archivos primarios: </p>
<ul>
<li>"<strong>template.html</strong>" la plantilla principal en HTML plano.</li>
<li>"<strong>style.css</strong>" la hoja de estilos asociada a la plantilla.</li>
<li>"<strong>theme.php</strong>" el archivo tema PHP.</li>
</ul>
<p>Su instalaci�n de Coppermine tambi�n incluye un directorio de "tema
de ejemplo" (sample theme). El "tema de ejemplo" incluye estos archivos
pero no se muestra en la lista desplegable de temas ubicada en la
pantalla de Coppermine. El archivo theme.php del tema de ejemplo
contiene adem�s una copia de cada funci�n y plantilla
"temeable/adaptable" para su referencia. Si usted opta por utilizar el
"tema de ejemplo" para comenzar a crear su propio tema, deber�a seguir
las instrucciones theme.php en la documentaci�n "<a href="http://www.f64foto.com.ar/CPG/theme/index.html">actualizar tema</a>" y comenzar con un archivo theme.php en blanco.</p>
<p>Para crear una nueva plantilla, la mejor opci�n es utilizar una
existente. Para ello haga una copia del directorio del tema que quiere
usar como base. Luego edite los archivos "<strong>template.html</strong>" y "<strong>theme.php</strong>" y reemplace todos los sucesos de "<strong>themes/directorio_tema_antiguo</strong>" con "<strong>themes/directorio_tema_nuevo</strong>" para que los enlaces (enlaces) apunten al lugar correcto. </p>
<p>Mientras edita el archivo "<strong>template.html</strong>" no borre los elementos que est�n entre <strong>{}</strong> ya que estos son marcadores utilizados por el script. Adem�s tenga en cuenta que, si bien este archivo est� localizado en "<strong>themes/directorio_de_su_tema</strong>",
debe ser codificado como si se encontrara en el directorio principal de
Coppermine. Por ejemplo, para mostrar una imagen debe usar <em><img src="<strong>themes</strong>/directorio_de_su_tema/images/imagen.gif" alt=""/></em> y no <em><img src="images/imagen.gif" alt=""/>.</em> Este mismo principio se aplica para el archivo "<strong>theme.php</strong>".</p>
<p>Tenga cuidado de no borrar la l�nea <em><script type="text/javascript" src="scripts.js"></script></em> ya que este javascript es necesario para ejecutar algunas funciones relacionadas con JavaScript.</p>
<p>Si est� utilizando un editor HTML para dise�ar su plantilla, la manera m�s pr�ctica puede ser ubicar el archivo "<strong>template.html</strong>"
dentro del directorio principal de su Coppermine y editarlo all�. Cada
vez que Coppermine se cargue, si el script encuentra un archivo llamado
"<strong>template.html</strong>" en el directorio principal, lo cargar�
en lugar del que haya asignado en el men� de configuraci�n. Una vez que
haya terminado de editar su tema aseg�rese de mover el archivo al
directorio al que pertenece.</p>
<p>Para modificar los colores, fuentes, tama�os, etc... utilizados por el script deber�a editar la hoja de estilos llamada "<strong>style.css</strong>". Por ejemplo: si quiere aumentar o disminuir el tama�o de las fuentes puede simplemente modificar la l�nea que contiene <em>table { font-size: 12px; }</em>. Muchos de los tama�os de fuentes usados por el script est�n definidos en porcentajes.</p>
<p>El archivo "<strong>theme.php</strong>" contiene todas las
plantillas que utiliza el script y puede editarlas tambi�n pero tenga
cuidado de no alterar las l�neas que comienzan con <em><!-- BEGIN xxx --></em> y <em><!-- END xxx --></em>.
Estas l�neas son generalmente usadas para identificar el principio y el
fin de bloques de c�digo que el script utilizar� para mostrar su
galer�a.</p>
<p>Si tiene dudas sobre c�mo crear sus propios temas puede visitar la
secci�n de descargas (download) en la p�gina principal del sitio web de
Coppermine: all� encontrar� <a href="http://sourceforge.net/project/showarchivos.php?group_id=89658&package_id=98541">temas cedidos por los usuarios</a> disponibles para descargar y pueden ser previsualizados en la <a href="http://coppermine.sourceforge.net/demo/">p�gina de demostraci�n de Coppermine</a>.</p>
<p>Mientras se encuentre creando o probando un nuevo tema, es probable
que no desee que los visitantes observen este proceso pero a la vez ser
capaz de previsualizar los cambios. Para esto, agregue <tt class="code">theme=nombre_de_su_tema</tt> en la url de su navegador de internet.</p>
<br>
<strong>Ejemplos:</strong>
<ul>
<li><tt class="code">http://susitio.tld/Coppermine/index.php?theme=nombre_de_su_tema</tt> mostrar� la p�gina de inicio de Coppermine usando su tema.</li>
<li><tt class="code">http://susitio.tld/Coppermine/thumbnails.php?album=1&theme=nombre_de_su_tema</tt> mostrar� la vistas en miniatura del �lbum 1 usando su tema.</li>
<li><tt class="code">http://susitio.tld/Coppermine/?theme=xxx</tt> regresar� al tema elegido y configurado como predeterminado.</li>
</ul>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="safe"></a>
<h2>2.4 Cuestiones del modo seguro (Safe mode)</h2>
<p>Un significante n�mero de proveedores de hosting ejecutan PHP en
modo seguro. Coppermine funciona sin problemas en modo seguro
(correctamente configurado) y con la "open basedir restriction" activa.
Desafortunadamente, en muchos de ellos el modo seguro no est�
configurado adecuadamente.</p>
<p>Si �ste es su caso, puede que necesite hacer lo siguiente:</p>
<ul>
<li>Con una aplicaci�n FTP, cambie el modo del directorio "<strong>include</strong>" de Coppermine en su servidor a <strong>0777</strong>.</li>
<li>Haga lo mismo con los directorios "<strong>albums</strong>" y "<strong>userpics</strong>".</li>
<li>Aseg�rese que al comienzo del archivo "<strong>include/config.inc.php</strong>" existe una l�nea con: "<strong>define('SILLY_SAFE_MODE', 1);</strong>"</li>
</ul>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="smtp"></a>
<h2>2.5 Utilizando SMTP para enviar correos</h2>
<p>Predeterminadamente el script usa la funci�n incorporada <strong>mail</strong> de PHP para enviar los correos pero en algunos casos esta funci�n no puede ser utilizada.</p>
<p> Si, para enviar correos con PHP, se le solicita un <strong>nombre de servidor</strong> (hostname), un <strong>nombre de usuario</strong> (username) y una <strong>contrase�a</strong>
(password), necesitar� editar los par�metros de la secci�n
"Configuraci�n de correo" (Email settings) del men� Configuraci�n e
introducir los valores correspondientes. Si no necesita un nombre de
usuario y una contrase�a para conectarse a su servidor SMTP, deje estos
campos en blanco. Si no conoce la informaci�n necesaria, deber�
consultarlo con su proveedor de hosting.</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="upgrade"></a>
<h1>3. Actualizando</h1>
<a name="10"></a>
<h2>3.1 Actualizando desde la versi�n 1.0</h2>
<p>Si usted tiene instalada la versi�n 1.0 y quiere transferir sus �lbumes a la versi�n 1.4x realice los siguientes pasos:</p>
<ul>
<li>Primero, haga una copia de respaldo (volcado/dump) de su base de datos.</li>
<li>Instale
la versi�n 1.4.x normalmente pero en un directorio diferente al que
contiene su versi�n 1.0. Note que para usar el script de actualizaci�n,
las <strong>tablas de la versi�n 1.0 y 1.4.x deben estar almacenadas en la misma base de datos</strong>.</li>
<li>Copie el directorio "<strong>albums</strong>" de la versi�n 1.0 dentro del directorio donde ha instalado la versi�n 1.4.x</li>
<li>El script de actualizaci�n asume que usted a usado el prefijo "<strong>CPG_</strong>"
para las tablas (valor predeterminado) cuando instal� la versi�n 1.0,
si este no es el caso, edite el archivo upgrade-1.0-to-1.2.php y
modifique la variable $prefix10.</li>
<li>Ingrese (log in) a su galer�a 1.4.x en el modo administrador (admin mode).</li>
<li>Ejecute el script de actualizaci�n, http://nombredesusitio/directorio_Coppermine/upgrade-1.0-to-1.2.php</li>
<li><strong>La actualizaci�n desde 1.0 a 1.4.x es un proceso de dos pasos.</strong> Debe cliquear en el enlace que aparece en la parte inferior de la p�gina para completar la actualizaci�n!.</li>
<li><strong>Borre el archivo upgrade-1.0-to-1.2.php de su servidor</strong>.</li>
<li>Si aparece un error, dir�jase a la p�gina de configuraci�n de Coppermine 1.4.x, habilite <a href="#debug_mode">modo de depuraci�n</a> (debug mode), intente ejecutar nuevamente el script de actualizaci�n y revise qu� errores le muestra.</li>
</ul>
<p> <strong>Este proceso de actualizaci�n deja a su galer�a v1.0 sin cambios.</strong></p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="11"></a>
<h2>3.2 Actualizando desde lanzamientos de la versi�n 1.1</h2>
<ul>
<li>Primero, haga una copia de respaldo (volcado/dump) de su base de datos.</li>
<li>Haga una copia de respaldo de su archivo include/config.inc.php, de su archivo anycontent.php y de su directorio "albums".</li>
<li>Descomprima el archivo.</li>
<li>Si el archivo <strong>install.php</strong> existe en el directorio principal, b�rrelo.</li>
<li>Suba todos los nuevos archivos y directorios.</li>
<li>CHMOD al directorio albums y a sus subdirectorios una vez m�s a 755 o 777 (dependiendo de la configuraci�n de su servidor).</li>
<li>Ejecute el script de actualizaci�n, http://nombredesusitio/directorio_Coppermine/update.php</li>
<li>Su actualizaci�n deber�a estar completa.</li>
</ul>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="12"></a>
<h2>3.3 Actualizando desde cpg1.2.0rc2 o cpg1.2.0final a la versi�n cpg1.2.1</h2>
<ul>
<li>Primero, haga una copia de respaldo (volcado/dump) de su base de datos.</li>
<li>Haga una copia de respaldo de su archivo include/config.inc.php, de su archivo anycontent.php y de su directorio "albums".</li>
<li>Descomprima el archivo.</li>
<li>Si el archivo <strong>install.php</strong> existe en el directorio principal, b�rrelo.</li>
<li><strong>Excepto por el directorio "albums"</strong>,
suba todos los nuevos archivos y directorios asegur�ndose de no
sobreescribir su archivo include/config.inc.php, su archivo
anycontent.php o su directorio "albums".</li>
<li>Cree un
directorio llamado "edit" dentro de su directorio "albums" - este
directorio ser� usado por Coppermine como un directorio temporal, no
suba archivos por ftp all�. Aseg�rese que el nuevo directorio "edit"
sea CHMODado de la misma forma en que su directorio albums est� (755 o
777, dependiendo de la configuraci�n de su servidor).</li>
<li>No es necesaria una actualizaci�n de la base de datos. Listo!</li>
</ul>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="13"></a>
<h2>3.4 Actualizando desde cpg1.2.x o cpg1.3.x a la versi�n cpg1.4.19</h2>
<ul>
<li>Primero, haga una copia de respaldo (volcado/dump) de su base de datos.</li>
<li>Haga una copia de respaldo de su archivo include/config.inc.php, de su archivo anycontent.php y de su directorio "albums".</li>
<li>Descomprima el archivo.</li>
<li>Si el archivo <strong>install.php</strong> existe en el directorio principal, b�rrelo.</li>
<li><strong>Excepto por el directorio "albums"</strong>,
suba todos los nuevos archivos y directorios asegur�ndose de no
sobreescribir su archivo include/config.inc.php, su archivo
anycontent.php o su directorio "albums".</li>
<li>Borre todos los archivos de idiomas que sean anticuados o de sobra del directorio lang que se llamen XXX-utf-8.php</li>
<li>Si
a�n no lo ha hecho, cree un directorio llamado "edit" dentro de su
directorio "albums" - este directorio ser� usado por Coppermine como un
directorio temporal, no suba archivos por ftp all�. Aseg�rese que el
nuevo directorio "edit" sea CHMODado de la misma forma en que su
directorio albums est� (755 o 777, dependiendo de la configuraci�n de
su servidor).</li>
<li>Ejecute el archivo "update.php" del
directorio Coppermine en su navegador de internet (ej.
http://sudominio.tld/Coppermine/update.php). Esto actualizar� su
instalaci�n de Coppermine realizando los cambios necesarios en la base
de datos.</li>
<li>Si usted hizo un tema personalizado,
apl�quele los cambios que fueron introducidos en la estructura de los
temas. - Refi�rase a la <a href="http://www.f64foto.com.ar/CPG/theme/index.html">Gu�a de actualizaci�n de temas</a>.</li>
<li>No
puede usar los archivos idiom�ticos de antiguas versiones de Coppermine
como idioma primario (el idioma que el administrador utilizar�) -
Aseg�rese de tener dentro del directorio lang solamente los archivos
idiom�ticos que vienen con este paquete (borre o renombre todos los
archivos de versiones anteriores que est�n dentro del directorio lang).<br>
Si necesita utilizar un idioma que no ha sido traducido para cpg1.4.x,
puede intentar usar el de cpg1.3.x, sin embargo existen algunas
advertencias: <ul>
<li>Necesita habilitar la opci�n retorno de idioma (language fallback) en la p�gina de configuraci�n de Coppermine.</li>
<li>Las frases de cpg1.4.x que no existen en su viejo archivo de idioma aparecer�n sin traducir o en ingl�s.</li>
<li>Coppermine no puede ser administrado utilizando un archivo idiom�tico antiguo - debe ser espec�ficamente para cpg1.4.x.</li>
<li>Usted
tiene la libertad de intentar usar archivos idiom�ticos antiguos, sin
embargo, cuando encuentre problemas o mensajes de error, cambie al
idioma US-English y compruebe si desaparecen. No brindamos soporte por
la utilizaci�n de archivos de idioma desactualizados.</li>
</ul>
</li>
<li>El
m�todo de "puenteo" (bridging) ha cambiado desde cpg1.3.x a cpg1.4.x.
Cuando actualice, su instalaci�n puenteada de Coppermine dejar� de
funcionar - deber� volver a aplicar el puenteo utilizando el <a href="#integrating">Manejador de Puente</a>
(bridge-manager) (utilizando su cuenta de administrador que us�
inicialmente para configurar Coppermine). No perder� nada, no se
preocupe.</li>
</ul>
<p>Atenci�n: al existir cambios en los archivos y en la base de datos
de Coppermine desde cpg1.3.0 (o m�s reciente) a cpg1.4.x, los usuarios
de versiones anteriores deber�n poner en pr�ctica los pasos antes
explicados que incluyen: el reemplazo de los archivos con los nuevos y
la ejecuci�n del script update.phpto por �nica vez.</p>
<a name="14"></a>
<h2>3.5 Actualizando desde cpg1.4.0 (o m�s reciente) a la versi�n cpg1.4.19</h2>
<ul>
<li>Primero, haga una copia de respaldo (volcado/dump) de su base de datos.</li>
<li>Haga una copia de respaldo de su archivo include/config.inc.php, de su archivo anycontent.php y de su directorio "albums".</li>
<li>Descomprima el archivo.</li>
<li>Si el archivo <strong>install.php</strong> existe en el directorio principal, b�rrelo ya que no es necesario al llevar a cabo una actualizaci�n.</li>
<li><strong>Excepto por el directorio "albums"</strong>,
suba todos los nuevos archivos y directorios asegur�ndose de no
sobreescribir su archivo include/config.inc.php, su archivo
anycontent.php o su directorio "albums".</li>
<li>Ejecute el
archivo "update.php" del directorio Coppermine en su navegador de
internet (ej. http://sudominio.tld/Coppermine/update.php). Esto
actualizar� su instalaci�n de Coppermine realizando los cambios
necesarios en la base de datos.</li>
<li>Si usted hizo un tema
personalizado, apl�quele los cambios que fueron introducidos en la
estructura de los temas. - Refi�rase a la <a href="http://www.f64foto.com.ar/CPG/theme/index.html">Gu�a de actualizaci�n de temas</a>.</li>
</ul>
<p>Atenci�n: al existir cambios en los archivos y en la base de datos
de Coppermine desde cpg1.3.0 (o m�s reciente) a cpg1.4.x, los usuarios
de versiones anteriores deber�n poner en pr�ctica los pasos antes
explicados que incluyen: el reemplazo de los archivos con los nuevos y
la ejecuci�n del script update.phpto por �nica vez.</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="versioncheck"></a>
<h2>3.6 La herramienta comprobadora de versi�n (version check tool)</h2>
<p>Desde el lanzamiento de cpg1.3.2, Coppermine trae una herramienta
adicional "comprobadora de versi�n" para ayudarle a resolver
inconvenientes relacionados con las actualizaciones. Excepto por
archivos espec�ficos de Coppermine que �nicamente funcionar�n con la
versi�n para la que fueron creados originalmente, la herramienta
comprobadora de versi�n puede ser usada con todas las versiones a
partir de la cpg1.2.1. Para iniciar esta herramienta, simplemente
agregue <tt>versioncheck.php</tt> en la barra de direcciones de su explorador de internet luego de haber ingresado a Coppermine como administrador (ejemplo: <tt>http://sudominio.tld/su_directorio_Coppermine/versioncheck.php</tt>).
Con la versi�n 1.4x, se puede iniciar la herramienta comprobadora de
versi�n desde el men� Herramientas Administrativas (Admin Tools).</p>
<a name="versioncheck_description_start"></a>
<h3>3.6.1 Lo que hace</h3>
<p>El script "comprobador de versi�n" est� dirigido a usuarios que
hayan actualizado su instalaci�n de Coppermine. Este script explora los
archivos en su servidor web e intenta determinar si la versi�n de los
mismos es id�ntica a los alojados en el repositorio de
http://Coppermine.sourceforge.net.<br> Luego de la comprobaci�n se
mostrar�n los archivos que no coinciden y los archivos a los que
deber�a actualizar. En Cpg1.4.x usted puede intercambiar la URL a la
actualizaci�n m�s reciente para archivos individuales en la p�gina
comprobadora de versi�n.</p>
<p>Se mostrar� en <span style="color: red; font-weight: bold;">rojo</span> todo lo que necesite ser reparado. Las entradas en <span style="color: rgb(255, 190, 0); font-weight: bold;">amarillo</span> deber�n ser examinadas y las mostradas en <span style="color: green; font-weight: bold;">verde</span> (o en el color de fuente de su tema) est�n OK y deber�an dejarse tal cual. Cuando una entrada sea <span style="color: red; font-weight: bold;">roja</span> o <span style="color: rgb(255, 190, 0); font-weight: bold;">amarilla</span>,
aparecer� un icono de ayuda a su lado que le dar� m�s informaci�n si lo
cliquea. Adem�s, al pasar el puntero del mouse sobre un item, se
mostrar� informaci�n adicional (tooltip).</p>
<p>La pantalla de la herramienta comprobadora de versi�n tiene varias secciones:</p>
<ul>
<li>Secci�n 1 explica para qu� puede ser utilizada esta herramienta.</li>
<li>Secci�n 2 ("<a href="#versioncheck_options_start">Opciones</a>") muestra las opciones entre las que puede elegir.</li>
<li>Secci�n 3 mostrar� una advertencia si Coppermine no fue capaz de
conectarse al repositorio en l�nea (donde se almacena la informaci�n
m�s reciente). Predeterminadamente el script har� una copia local del
archivo del repositorio. Si la conexi�n fue exitosa, obviamente, no
habr� mensaje de error.(ni secci�n 3).</li>
<li>Secci�n 4 mostrar� la versi�n de Coppermine actualmente en uso. Esta informacion se desprende del archivo <em>include/init.inc.php</em>
- si usted no ha reemplazado su copia de este archivo con la nueva
versi�n durante la actualizaci�n, su antigua (desactualizada) versi�n
se visualizar� en esta secci�n.</li>
<li>Secci�n 5 mostrar� el n�cleo de la herramienta comprobadora de
versi�n: la comparaci�n de versiones. El script se mover� por todos los
archivos que se supone que existen (basado en la informaci�n del
repositorio) y los comparar� con los archivos que usted tiene
actualmente en su servidor web.</li>
<li>Secci�n 6 mostrar� un res�men de los archivos y directorios revisados.</li>
</ul>
<a name="versioncheck_description_end"></a>
<a name="versioncheck_options_start"></a>
<h3>3.6.2 Opciones</h3>
<p>La pantalla de opciones le permite configurar la herramienta
comprobadora de versi�n. Las opciones no son guardadas, por lo que
deber� adjustarlas cada vez que ejecute la herramienta. Las opciones
predeterminadas deber�an ser las adecuadas para la mayor�a de los
usuarios - c�mbielas solo si tiene una buen motivo para hacerlo.</p>
<img src="pics/es_versioncheck_options.gif" alt="" title="" border="0" height="255" width="911">
<ul>
<li><em>mostrar directorios/archivos opcionales</em><br>Desm�rquela para ocultar los archivos que est�n etiquetados como "opcionales" (solo visualizar� los archivos obligatorios).</li>
<li><em>mostrar archivos obligatorios</em><br>Desm�rquela para ocultar
los archivos que est�n etiquetados como "obligatorios" (tenga en cuenta
que al deshabilitar ambas opciones no se mostrar� ning�n archivo).</li>
<li><em>mostrar informaci�n adicional</em><br>Conmuta la visualizaci�n
de la informaci�n sobre la versi�n del Coppermine instalado y el estado
de la conexi�n con el repositorio. Desm�rquela si est� haciendo
capturas de pantalla para ahorrar espacio y reducir dimensiones.</li>
<li><em>mostrar versiones de archivo</em><br>Conmuta la visualizaci�n
de la informaci�n adicional sobre la versi�n de un archivo que
pertenece a la versi�n que usted est� usando. Al mirar el c�digo fuente
de un archivo de Coppermine, la versi�n del mismo es el n�mero que se
parece a esto: <tt>Id: index.htm,v 1.66 2004/08/26 04:42:19 gaugau Exp</tt> (en este ejemplo la versi�n del archivo es 1.66)</li>
<li><em>mostrar solo directorios/archivos con errores</em><br>Conmuta
la visualizaci�n de los archivos que no presentan errores. Habilite
esta opci�n si quiere realizar una captura de pantalla y una consulta
en el foro de Coppermine.</li>
<li><em>Coppermine est� instalado en la ra�z del servidor web</em><br>Experimental:
si todos sus archivos son mostrados como "no-existe", probablemente
haya instalado Coppermine en el directorio ra�z de su servidor web, o
que est� usando subdominios. Marque esta opci�n si est� experimentando
problemas pero, como esta opci�n no ha sido testeada a fondo a�n, no
hay garant�as de que funcione correctamente en su configuraci�n.</li>
<li><em>tratando de conectar al repositorio en l�nea</em><br>Conmuta si
la herramienta comprobadora de versi�n deber�a intentar conectarse con
el repositorio en l�nea (marcada por defecto). �nicamente desmarque
esta opci�n si est� seguro de que no puede acceder al repositorio en
l�nea debido a la configuraci�n de su servidor y quiere reducir un poco
el tiempo que el script necesita para ejecutarse.</li>
<li><em>mostrar permisos de directorio</em><br>Conmuta la opci�n para mostrar/ocultar los permisos de lectura/escritura de un directorio.</li>
<li><em>no mostrar el enlace svn</em> / <em>mostrar el enlace svn a la rama estable</em> / <em>mostrar el enlace svn a la rama en desarrollo</em><br>Conmuta
la visualizaci�n de una columna adicional que contiene un enlace al svn
en l�nea . �nicamente recomendado si la versi�n de su cpg est� OK (<span style="color: green; font-weight: bold;">verde</span>),
pero la versi�n de su archivo parece estar desactualizada. Usted puede
luego conectarse al svn en l�nea para conseguir una versi�n m�s
reciente de su archivo. Esto es recomendado solo si sabe lo que est�
haciendo (o si alg�n miembro del equipo de soporte del foro de
Coppermine le haya dicho que lo haga).</li>
<li><em>mostrar resultado condensado (para capturas de pantalla m�s f�ciles)</em><br>Al
marcar estas opciones se minimiza el ancho de las columnas de
comparaci�n de versi�n, lo que le permitir� crear capturas de pantalla
de reducidas dimensiones y tama�o.</li>
</ul>
<a name="versioncheck_options_end"></a>
<a name="versioncheck_comparison_start"></a>
<h3>3.6.3 Version comparison</h3>
<p>There is a lot of information packed into a small space. Here's an example of a possible output and what the output means:</p> <br>
<img src="pics/es_versioncheck_comparison.gif" alt="" title="version comparison" border="0" height="288" width="471">
<ul>
<li>The column "icon" shows if the entry is a directorio or a archivo.
Clicking on the icon takes you to the p�gina, e.g. clicking on util.php
will take you to the "admin tools page" (although not all Coppermine
archivos can be opened directly by running them in the browser).<p>In above example, rows "A" to "E" are directorios, rows "F" to "K" are archivos.</p></li>
<li>The column "directorio/archivo" holds the relative path from your Coppermine root to the directorio/archivo in question.<br>
<p>If an entry is in your default font color, it exists (in above example, all rows but "G" and "H").<br>
</p><p>If the entry is in <span style="color: rgb(255, 190, 0); font-weight: bold;">yellow</span>
(row "G"), the corresponding directorio/archivo doesn't exist on your
webservidor, but it is only considered to be optional (e.g. a language
archivo that comes with the Coppermine package that you don't want to
use can be deleted from the webservidor. It will then be shown in <span style="color: rgb(255, 190, 0); font-weight: bold;">yellow</span>, as it's only optional to have it). It's up to you if you need it.</p>
<p>If the entry is in <span style="color: red; font-weight: bold;">red</span>
(row "H"), the directorio/archivo in question doesn't exist on your
webservidor, but it is mandatory to have it. You should upload the
archivo from your Coppermine package to your webservidor. Only leave it
as-is if you really know what you're doing.</p></li>
<li>The column "writable" shows information if the directorio in
question is writable, and whether this is correct or not. The write
permissions for archivos are not being displayed, as this would slow
down the script considerably. Usually, there are icons that show the
writable status of your directorio (if you have the icon resources on
your webspace). Optionally, a plain text message in brackets might be
visible (if you don't have the icon resources).
<ul>
<li>A white pencil with a <span style="color: green; font-weight: bold;">green</span> "x" indicates that the directorio is not writable and is isn't suppossed to be writable - everything is OK then (row "A")</li>
<li>A <span style="color: green; font-weight: bold;">green</span> pencil indicates that the directorio is writable and it is suppossed to be writable as well - everything is OK then (row "D"</li>
<li>A white pencil with a <span style="color: red; font-weight: bold;">red</span>
"x" indicates that the directorio is not writable, although it should
be (row "C"). You should change write permissions (CHMOD) for this
directorio and everything within it, usually using your <acronym title="Archivo Transfer Protocol">FTP</acronym> software.</li>
<li>A <span style="color: red; font-weight: bold;">red</span> pencil
indicates that the directorio is writable, but it shouldn't be (row
"E"). Unless absolutely necessary, leaving archivos writable could be a
security risk. Where possible, you should change permissions for this
directorio and everything within it to read/execute only.</li>
</ul>
</li>
<li>A question mark in a yellow box (help icon) indicates that there is
additional information available. Click on the icon to display the
pop-up window with this information.</li>
<li>The column "cpg versi�n" displays what Coppermine package your
archivo on your webservidor is from, and what versi�n it should be
from. The data is being extracted from the header of the archivo,
that's why directorios are shown as "n/a" - they have no header
information containing their Coppermine versi�n (rows "A" to "E").
<p>Archivos that contain header information are being displayed with
your archivo versi�n and the cpg versi�n of the archivo in the
repository, separated with a slash. It is possible that a archivo
versi�n may differ from the versi�n of your whole package - this
doesn't matter as long as both your versi�n and the repository versi�ns
match (the are displayed in <span style="color: green; font-weight: bold;">green</span>) - in above example: rows "F", "J" and "K".</p>
<p>Of course, versi�n numbers from archivos that don't exist can't be
extracted, that's why rows "G" and "H" have a dash as cpg versi�n. If
your cpg versi�n is lower than the repository versi�n, your versi�n is
being displayed in <span style="color: red; font-weight: bold;">red</span>:
if this is the case, you probably haven't successfully uploaded the
proper archivo of archivos from the Coppermine package to your
webservidor (replacing archivos that may have already existed on your
webservidor) - you should do so now (row "I").</p>
<p>If your local versi�n is being displayed in <span style="color: rgb(255, 190, 0); font-weight: bold;">yellow</span>,
you are using a archivo that belongs to a higher Coppermine versi�n
than the rest of your archivos - you probably downloaded a archivo from
the devel branch: remember that using devel archivos go unsupported, do
so on your own risk (if you know what you're doing). If most or all of
your archivos are being displayed in <span style="color: rgb(255, 190, 0); font-weight: bold;">yellow</span>,
you probably have upgraded some archivos, but you forgot to upgrade the
archivo "include/init.inc.php" (that holds the versi�n info for your
install). aseg�rese to upload <strong>all</strong> archivos from the package to your servidor.</p>
</li>
<li>
<p>The column "archivo versi�n" holds the individual archivo's versi�n
that get's increased during development of a new Coppermine versi�n
(each time a developer modifies a certain archivo, the versi�n number
increases by one). As directorios can't contain such versi�n numbers,
they are again labelled as "n/a" (rows "A" to "E"); the same applies to
archivos that don't exist, that's why their archivo versi�n is
displayed as dash (rows "G" and "H"). Also the archivo versi�n is
irrelevant when comparing archivos from different Coppermine packages,
that's why row "I" has a dash as well.</p>
<p>The coloring scheme is similar to the cpg versi�n system: <span style="color: green; font-weight: bold;">green</span> means "everything is OK", <span style="color: red; font-weight: bold;">red</span> means "you're using an outdated versi�n" and <span style="color: rgb(255, 190, 0); font-weight: bold;">yellow</span> means "you're using a newer versi�n than you're actually suppossed to.</p>
<p>The difference between the cpg versi�n and the archivo versi�n
columns is indicative of the way you should obtain the archivo that you
need to replace the existing one on your servidor: a <span style="color: red; font-weight: bold;">red</span>
entry in the cpg versi�n column means the archivo on your servidor
hasn't been replaced with the archivo from the Coppermine package; a <span style="color: red; font-weight: bold;">red</span>
entry in the archivo versi�n column (row "J") usually means that there
have been updates to a certain archivo after the release of the package
- you should either check if there is a newer package available or get
the most recent archivo from the <acronym title="Subversion">SVN</acronym> (enable the web svn enlace column in the versi�ncheck <a href="#versioncheck_options_start">options</a>).</p>
</li>
<li>The column "web svn" (off by default) enlaces to the corresponding archivo in the <acronym title="Subversion">SVN</acronym>.
You're recommended to use this only if there appears to be a newer
versi�n in the svn than your Coppermine package has and you know what
you're doing.</li>
</ul>
<a name="versioncheck_comparison_end"></a>
<a name="versioncheck_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="downgrading"></a>
<h2>3.7 Downgrading from cpg1.4.x to an older versi�n</h2>
<p>CPG1.4.x incorporates many new features (compared to older
versi�ns), so we encourage all users to upgrade. However, there may be
some who want to test cpg1.4.x and decide later that they want to go
back to an older versi�n. You have to keep in mind that a full upgrade
changes the overall layout of Coppermine's base de datos that includes
converting the encoding to unicode. This process can't be reverted:
once you have done the conversi�n, the only way back is to restore a
complete mySQL base de datos dump (of course you have to create this
backup <strong>before</strong> you upgraded in the first place). Creating mySQL dumps (backups) is recommended anyway, so you should do so <strong>now</strong>.</p>
<p>If you haven't converted your base de datos to unicode (utf-8)
encoding, you can downgrade as explained below. To make this absolutely
clear: you can only downgrade if you used to have cpg1.3.x before and
upgraded this versi�n to cpg1.4.x without converting the base de datos.
If you <em>have</em> converted the base de datos or if you have made a <em>fresh</em> install of cpg1.4.x, you can't downgrade at all!</p>
<p>To actually perform the downgrade, replace all cpg1.4.x archivos on
your servidor with the archivos from the older versi�n (as if you were
doing an upgrade, see above). You then have to undo some changes in the
base de datos structure. To do so, run a query like<br>
</p><pre>ALTER TABLE `CPG_users` CHANGE `user_location` `user_proarchivo1` VARCHAR(255);
ALTER TABLE `CPG_users` CHANGE `user_interests` `user_proarchivo2` VARCHAR(255);
ALTER TABLE `CPG_users` CHANGE `user_website` `user_proarchivo3` VARCHAR(255);
ALTER TABLE `CPG_users` CHANGE `user_occupation` `user_proarchivo4` VARCHAR(255);</pre><br>
using a tool like <a href="http://www.phpmyadmin.net/" rel="external" class="external">phpMyAdmin</a>, replacing <tt class="code">CPG_</tt> in the query with the prefix you have chosen during Coppermine install.<p></p>
<a name="downgrading_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="administration"></a>
<h1>4. Configuraci�n y Administraci�n</h1>
<h2>4.1 Categor�as, albumes y archivos<a name="cat_alb_pic"></a></h2>
<p>La Foto Galer�a Coppermine (CPG) funciona de la siguiente manera:</p>
<ul>
<li>Los archivos son almacenados en albumes.</li>
<li>Los albumes est�n organizados en categor�as.</li>
<li>Las categor�as pueden ser jerarquizadas (en subcategor�as).</li>
</ul>
<p>If you don't plan to have many albumes, you really won't need to use
the categories feature. If this applies to you, simply do not create
any categories and all your albumes will automatically appear on the
main p�gina of the script.</p>
<p>Si usted no planea tener demasiados albumes, no hay necesidad de
utilizar las categor�as. En ese caso no cree categor�as y todos sus
albumes aparecer�n autom�ticamente en la p�gina principal del script.</p>
<p>Existe, sin embargo, una categor�a especial llamada"<strong>Galer�as de usuario</strong>"
(User galleries). Esta categor�a no puede ser borrada. Si un usuario
pertenece al grupo "puede tener una galer�a personal" y �ste est�
establecido en SI, ese usuario tendr� la posibilidad de crear sus
propios albumes y su galer�a ser� una sub-categor�a de "Galer�as de
usuario". De todos modos, este enlace no estar� visible para los
visitantes de su sitio si usted no les permite a los usuarios subir
im�genes y tener sus propios albumes. </p>
<p>El administrador puede crear albumes en cualquier categor�a. Los
usuarios no-administrativos solo pueden crear albumes en "Galer�as de
usuario/su_nombre_de_usuario".</p>
<p>Adem�s puede renombrar la "Galer�as de usuario" y su descripci�n. Para ello dir�jase a su <a href="#cat_cp">Panel de control de categopr�a</a> (category control panel) y cambie su nombre all� (por ejemplo, para traducir las palabras "User galleries" a su idioma).</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<h2>4.2 Admin mode & User mode<a name="admin_user_mode"></a></h2>
<p>When you are logged in as an administrator, the script provides two
modes of operation : Admin mode & User mode. You can switch between
Admin & User mode by clicking on the corresponding enlace in the
menu bar at the top of the screen.</p>
<p>When you are in admin mode, you can administer your gallery using the menu bar that appears when in admin mode, as shown below :</p>
<p><a name="admin_menu"></a><img src="pics/es_admin_menu.gif" alt="Admin menu" border="0" height="45" width="930"></p>
<p>When you are in user mode you are still logged in as an admin user,
but the admin controls (the admin menu bar etc.) are hidden from the
screen to give you a basic preview of what the p�gina would look like
for "regular users". However (as you still are logged in as admin),
certain permissions and options in user mode will still look the same
as if you were in admin mode; you can <strong>not</strong> use "<em>User Mode</em>"
to see what a non-admin user is actually allowed to see. To see what a
casual visitor can see and do on your site, simply log out. To see what
a registered user can see and do on your site, create a test user
account (non-admin) and log in with this particular user (when doing
this it is recommended that you use two different browsers, NOT two
instances of the same browswer, to view your site so you can stay
logged in as admin on one and view what regular users see while making
changes in admin mode. You will have to refresh the non-admin mode
screen to see what changes you incorporated).</p>
<p>The items in the admin menu should be pretty self-explanatory:</p>
<ul>
<li><strong>Upload approval</strong><br>See all pics that await approval by the admin (if you set admin approval as a required step on the settings in the "<a href="#group_cp">groups</a>" control panel)</li>
<li><strong>Config</strong><br>Configure the overall look of your gallery and the settings using the "<a href="#admin">Config</a>" button in the admin menu (note: you can not access the configuration by manually entering the url of the config archivo)</li>
<li><strong>Categories</strong><br>Create/edit/delete <a href="#cat_cp">categories</a></li>
<li><strong>Albums</strong><br>Create/edit/delete <a href="#albmgr">albumes</a></li>
<li><strong>Groups</strong><br>Create/edit/delete <a href="#group_cp">groups</a></li>
<li><strong>Users</strong><br>Create/edit/delete <a href="#user_cp">users</a></li>
<li><strong>Ban Users</strong><br>Ban
users based on hostname or IP address. aseg�rese not to ban yourself!
Use this feature with extreme caution, as most users today do not have
static IP addresses, this feature should only be employed if you really
know what you're doing.<br>
<span class="small">[cpg1.3.0 or better required]</span> </li>
<li><strong>Review Comments</strong><br>edit/delete user's comments</li>
<li><a name="ecard_log"></a><strong>Display Ecards</strong><p>View the ecards sent by users.</p>
<p>You
must have ecard-logging enabled in the config menu, first (by default,
logging is disabled). When enabled, all ecards that are being sent are
written into the base de datos, where the Coppermine admin can view
them.</p>
<img src="pics/es_ecard_log.gif" alt="" border="0" height="246" width="793"><br>
You can sort the log by clicking on the arrow icons next to each
heading, and you can delete single or multiple log entries (deleting
the log entries will not disable the ecard recipient to view the ecard).<br>
<p>Before
switching this option on, aseg�rese that logging such information is
legal in your country. It is also advisable to notify your users that
all ecards are being logged (preferrably on the registration screen).</p>
<span class="small">[cpg1.3.0 or better required]</span>
<a name="ecard_log_end"></a> </li>
<li><strong>Sort my pictures</strong><p>Picture
manager that can be used to custom-sort archivos within an �lbum. By
default, the p�gina de miniaturas that displays the contents of an
�lbum will be sorted by the sorting order specified in "<a href="#admin_thumbnail_default_sortorder">Default sort order for archivos</a>"
on the p�gina de configuraci�n. The "sort my pictures" option overrides
the default sorting mechanism and displays the thumbnails in the order
you specify. As this means an additional effort in the maintenance of
each �lbum, it's recommended to use the default sorting by archivoname
and (instead of specifying a custom sort order) and naming the archivos
appropriately before upload.</p>
<p>Note: each user (including the
admin) can use the sorting controls on the �lbum's thumbnails display
page to manually override the sorting option that was specified in
Coppermine's config and the "Sort my pictures" option; this final
method of changing the sort order is stored locally in a cookie of the
client and reverts to the config settings when this cookie is discarded.</p></li>
<li><strong>Batch add archivos</strong><br><a href="#batch_add_pics">Batch-add archivos</a>
to the Coppermine base de datos that have been previously uploaded by
FTP. Batch-add archivos does not upload archivos for you. You must
upload archivos using your proveedor de hosting's archivo manager or an
FTP client software. You FTP archivos into directorios that you create
in the Coppermine �lbum directorio. You must not, however, create these
directorios in the <em>userpics</em> directorio.</li>
<li><a name="admin_tools"></a><strong>Admin Tools (Resize Pictures)</strong><br>A collection of utilities to:
<dl>
<dt>Rebuild or resize intermediate pictures and thumbnails.</dt>
<dd><img src="pics/es_util_re-size.gif" alt="" border="0" height="180" width="513"><br>
<p>Use
this if you have changed the settings for thumbnail or intermediate
images in config, or if you have to replace corrupt versi�ns.</p><p>Select the radio button for this action, then choose to rebuild the thumbnails, intermediates, or both.</p><p>This
uses a lot of servidor resources, so if you experience timeout issues,
try setting it to process smaller batches ( 45 is the current default ).</p></dd>
<dt>Delete full-size pictures.</dt>
<dd><p>Use this to save space on your webspace.</p><p>When
selected, Coppermine checks to see if an intermediate copy exists, and
if it does, it deletes the original sized picture, then re-names the
intermediate. If no intermediate exists, Coppermine leaves the original
in place.</p></dd>
<dt>Delete orphaned comments.</dt>
<dd>Sometimes,
when pictures have been deleted, any comments associated with them
remain in the base de datos. Use this to remove them from the base de
datos entirely.</dd>
<dt>Rename archivo titles.</dt>
<dd>Use this to re-name the title of all archivos in an �lbum, using info from the archivoname.</dd>
<dt>Delete archivo titles.</dt>
<dd>Use this to clear the archivo titles from one or more albumes.</dd>
<dt>View your servidor php info.</dt>
<dd><p>If,
you after following the troubleshooting guides in the documents
provided here, you are still having problems with your Coppermine
installation, these problems are sometimes caused by a misconfigured
servidor setup. Clicking this enlace will provide you with all your php
and mySQL settings, as well as information on the GD library (if
installed). The information may be required by the support team, if you
are unable to sort problems yourself.</p><p>It is not possible for
visitors to your site to access this information, so if asked for it,
copy and paste it on the support board. Do not post this information or
any debug information unless requested first. You may post <em>ERROR</em> messages verbatim, but refrain from posting <em>warning</em> messages. </p></dd>
<dt>Run a base de datos update (update.php).</dt>
<dd>After
an update/upgrade, it is usually necessary to run update.php. This can
be done by typing the address directly into your browser, or by
clicking this enlace.<a name="admin_tools_end"></a></dd>
</dl>
</li>
<li><strong>My proarchivo</strong><br>Edit your own user proarchivo</li>
</ul>
<p>In previous beta versi�ns of cpg1.4.x there used to be an admin mode
and user mode for "regular registered" users, somewhat like those for
the true administrator. This feature has been removed as it was both
confusing for end users and really didn't serve any special purpose.</p>
<p>The user with upload permissions has the following admin options:</p>
<ul>
<li><strong>Create / order my albumes</strong><br>similar to �lbum manager in admin mode, the user can create albumes within his user gallery</li>
<li><strong>Modify my albumes</strong><br>The user can edit �lbum title and description (similar to "<a href="#%E1lbum_prop">�lbum properties</a>" for the admin, but the user can't move his albumes to other categories)</li>
<li><strong>My proarchivo</strong><br>The
user can edit his proarchivo (changing passwords, edit location,
interests, p�gina de inicio and occupation properties, view quota
usage). When integrated with a bbs service, the "My proarchivo" enlace
will send the user to the bbs's profile p�gina. </li>
</ul>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="group_cp"></a><h2>4.3 The group control panel</h2>
<p><img src="pics/es_group_cp.gif" alt="" border="0" height="291" width="897"></p>
<p>This is where you define what members of a user <em>group</em> can and can't do.</p>
<p>The disk quota applies only for groups where "<em>Personal gallery</em>" has been set to "<strong>Allowed</strong>".
Both archivos uploaded by a user in his personal gallery as well as
archivos uploaded to public galleries are included in the quota.</p>
<p>Use the <strong>anonymous</strong> group to define what non-registered users can and can't do. Quota and "<em>Personal gallery</em>" are meaningless for anonymous users.</p>
<a name="group_cp_permissions"></a>
<p><em>Permissions</em> control what the user is allowed to do in the gallery (Rating/Sending Ecards/Posting Comments).</p>
<p>Bear in mind that if a user is a member of a group where "<em>Rating</em>", "<em>Comments</em>" or "<em>Public albumes upload</em>" is set "<em>YES</em>",
s/he will have the right to perform these operations only in albumes
where they are allowed. ( ie. uploading archivos will only be possible
in albumes where "<em>Visitors can upload archivos</em>" has been set to <em>YES</em>.)</p>
<a name="group_cp_permissions_end"></a>
<a name="group_cp_personal"></a>
<p>If "<em>Personal gallery</em>" is set to <em>Allowed</em>, the members of the group will be able to have their own gallery in the "<em>User galleries</em>" category where they will be able to create their own albumes.</p>
<p>If "<em>Approval</em>" is set to <em>NO</em>, archivos uploaded by members of the group in albumes created in their own gallery won't need to be approved by the admin. If "<em>Approval</em>" is set to <em>YES</em>,
the users in the particular group will be able to upload, however the
uploaded archivos will only be shown after the admin (you) has approved
them.</p>
<a name="group_cp_personal_end"></a>
<p>The group control panel enables you to control the upload parameters of any group.</p>
<a name="group_cp_upload_method"></a>
<p><em>Upload method</em> lets you select the type of upload method that a particular group may use. Four forms or methods are currently available.</p>
<ul>
<li><strong>Single archivo uploads only</strong> - Users of this group
may not use advanced uploading features. They may upload one archivo at
a time. To enable single archivo uploads only, set <em>Archivo upload boxes</em> to "1", <em>URI upload boxes</em> to "0" and <em>No. of boxes</em> to "fixed"</li>
<li><strong>Multiple archivo uploads only</strong> - Users of this group may upload multiple archivos at one time. To enable multiple archivo uploads, set <em>Archivo upload boxes</em> to any number higher than "1", <em>URI upload boxes</em> to "0" - it's up to you to let users configure the <em>No. of boxes</em>,
but it's recommended to set it to "fixed" to avoid confusion and to
limit the load on your servidor should several users try to upload
simultaneously.</li>
<li><strong>URI uploads only</strong> - The group may only upload
archivos using URIs. Acceptable URIs must begin with 'http://' or
'ftp://'. To enable URI uploads only, set <em>Archivo upload boxes</em> to "0", <em>URI upload boxes</em> to "1" or higher.</li>
<li><strong>Archivo-URI</strong> - Users of this group may upload archivos using archivo upload boxes and URIs. To enable both archivo and URI uploads, set <em>Archivo upload boxes</em> to "1" or higher, <em>URI upload boxes</em> to "1" or higher</li>
</ul>
<p><em>No. of boxes </em> set to "variable" allows the user to select
the number of upload boxes for an upload. Usually, you will leave this
option set to "fixed", as it presents the user with an additional step
in the upload wizard that is not necessary.</p>
<p><em>Archivo upload boxes</em> controls the number of archivo upload boxes presented to the user. If the user may customize the number of boxes (<em>No. of boxes </em>
set to "variable"), this setting serves a maximum limit for the number
of boxes he may request. Otherwise, this setting determines the number
of boxes that will appear on the upload form.</p>
<p><em>URI upload boxes</em> is the same type of control as <em>Archivo upload boxes</em>, but it controls the presentation of URI upload boxes.</p>
<a name="group_cp_upload_method_end"></a>
<p><strong>Please note</strong>: on unbridged installs (or standard,
stand-alone Coppermine installs), the group "banned" feature really
doesn't accomplish much. A user who is member of this group is still
able to log in and view pics, he's just not able to upload, rate, send
ecards or post comments. If you truly want to place a full ban on
someone you should use the "banning" feature (which isn't group-based
but individually based), instead.</p>
<a name="group_cp_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="user_cp"></a><h2>4.4 The user control panel</h2>
<p>The user control panel can be found when clicking "users" from the
admin menu. It is the place where you create and manage your users.</p>
<p><span class="important">If you have enabled integration (bridging)
Coppermine with another application (e.g. your favorite BBS app),
Coppermine will use the member table of the application you bridged
with (your BBS), so the built-in Coppermine user management will be
disabled in favor of the user management that comes with the bridged
application. This has been incorporated to eliminate redundancy and
facilitate a seemless integration.</span></p><p>As a result, you will
not have this user control panel; clicking the "users" enlace will send
you to your bridge application's user management instead.</p>
<img src="pics/es_usermgr.gif" alt="" title="user control panel" border="0" height="294" width="929"><br>
<a name="user_cp_page"></a><h3>4.4.1 Page controls</h3>
<ul>
<li>You can sort the user management display by either clicking the arrow icons (<img src="../images/ascening.gif" alt="" title="ascending" border="0" height="9" width="9"><img src="../images/descending.gif" alt="" title="descending" border="0" height="9" width="9">) next to each column header or by choosing the sort order from the dropdown at the top right.</li>
<li>If you have more than 25 users, a page tab will apear at the bottom
right of the screen, allowing you to go to subsequent p�ginas of your
member list</li>
<li>Clicking on a user's name will <strong>display</strong> the profile page of the individual user (read only)</li>
<li>The edit icon (<img src="pics/edit.gif" alt="" title="edit" border="0" height="16" width="16">) will send you to the user's proarchivo in <strong>edit</strong> mode - you can change the password, email account and other user-related settings there</li>
<li>If a user has uploaded any archivos, a enlace of "recent uploads"
will show up next to his name. Clicking on this enlace will display
archivos that have been uploaded by that user</li>
<li>The "group" column displays the primary member group the user is in</li>
<li>The column "Registered on" will show the date that the user account was created</li>
<li>The "Last visit" column will show the last login of the user. <br>Note:
if the user has ticked the checkbox "Remember me" on the login screen,
he will not have to login every time he visits the gallery so this date
may be accurate.</li>
<li>The "Archivos" column displays how many archivos the user has
uploaded to date (including those that are awaiting admin approval)</li>
<li>The "Space used" column shows how much of the space that is
assigned to the user has already been used. The total space the user is
allowed to have ("Space Quota") depends on the user's group - which you
set in the <a href="#group_cp">groups panel</a>.</li>
<li>You can change a number of settings for several users at once by
clicking the checkbox in front of the user row (use the checkbox at the
very top or bottom of the p�gina to select/unselect all users on the
p�gina) and then chosing an action to perform from the dropdown box
"With selected" at the bottom left of the p�gina. The actions you can
choose from are "Delete", "Deactivate", "Activate", "Reset password",
"Change primary membergroup" and "Add secondary membergroup". The user
currently logged on (you as gallery admin) has no checkbox to avoid
accidental deletion or deactivation of your own admin account.</li>
</ul>
<a name="user_cp_page_end"></a>
<a name="user_cp_search"></a><h3>4.4.2 Searching for user(s)</h3>
<p>You can use the wildcards: <tt class="code">*</tt> (for any <em>string</em>) and <tt class="code">?</tt> (<em>any single character</em>) or even <tt class="code">%expression%</tt>.<br>Example: searching for <tt class="code">j*</tt> will return both <tt class="code">Jack</tt> and <tt class="code">Jill</tt></p>
<a name="user_cp_search_end"></a>
<a name="user_cp_new"></a><h3>4.4.3 Creating new users</h3>
<p>To create a new user, simply click on the button "Create new user"
at the bottom of the user manager and fill in the form that will come
up.</p>
<p>This does of course not apply if you have bridging enabled, as user
management is being handled by the app you have bridged Coppermine
with. In this case, the user management screen of your bridged app
should show - create a new user there.</p>
<a name="user_cp_new_end"></a>
<a name="user_cp_edit"></a><h3>4.4.4 Editing users</h3>
<p><img src="pics/usermgr_edit.gif" alt="" align="right" border="0" height="326" width="295">To edit the properties of a user, click the <img src="pics/edit.gif" alt="" title="edit" border="0" height="16" width="16">-button
next to the user name. You will then find a p�gina where you can modify
all user proarchivo fields the user has. This includes the option to
change the password of that user. If you don't want to change a user's
password, leave the password field blank.<br>
The dropdown list determines the primary group the user is in, the checkboxes beneath it determine the secondary groups.</p>
<p>Please note that this screen (as well as the rest of Coppermine's user management) will not be available if you have enabled <a href="#integrating">bridging</a>,
because then the user management of the application you have bridged
with (e.g. your BBS) kicks in and handles everything related to user
management.<br>
The button "Album permissions by group" can <em>not</em> be used to set permissions, but only to <em>view</em> them. You can set permissions using the <a href="#%E1lbum_prop">�lbum properties</a> screen.</p>
<a name="user_cp_edit_end"></a>
<a name="user_cp_group"></a><h3>4.4.5 Group membership</h3>
<p>When creating a new user or editing an existing user, you will
notice a row named "User group" - it determines what group(s) the user
is in.<br>
The first field (a dropdown field) determines the primary user group.
It determines the status of a user. You should set it to
"Administrator" (for users you want to assign admins powers to) or
"Registered".<br>
Additional (secondary) group membership can be assigned using the
checkboxes beneath the dropdown field. Here, all your custom groups
(that you can create and manage using the <a href="#group_cp">group control panel</a>)
should show as well as the core groups (the ones that come with
Coppermine out of the box and can't be deleted). Assign additional
group membership to your users here. Privileges for a particular user
inherited from group membership are added: the least restrictive
permissions are taken into account.</p>
<p>Example: if you want your registered users to be capable of viewing
the gallery only, and only privileged users of your custom user group
"photographers" are allowed to actually upload archivos, make all your
users members of the built-in group "registered" (by default, they
already are). Only for user you want to give the privilege to upload,
tick the check box "photographers" as secondary group. Then go to your
groups control panel and disallow uploads for the registered group
there, but allow uploads for the custom group "photographers".</p>
<p class="important">Note: the button "�lbum permission by group" beneath the checkboxes is <strong>not</strong> meant to <strong>assign</strong> �lbum permissions, but only to <strong>check</strong> the permissions set. You can only assign particular �lbum permissions on the <a href="#%E1lbum_prop">�lbum properties</a> screen.<br clear="all"></p>
<a name="user_cp_group_end"></a>
<a name="user_cp_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="cat_cp"></a><h2>4.5 The categories control panel</h2>
<p><img src="pics/es_category_cp.gif" alt="" border="0" height="558" width="929"></p>
<p>This panel allows you to edit your categories.</p>
<ul>
<li>The <img src="pics/edit.gif" alt="" border="0" height="16" width="16"> button
allows you to edit the title, description and parent category of an
existing cetegory.</li>
<li>The <img src="pics/delete.gif" alt="" height="16" width="16"> button
allows you to delete a category. Deleting a category does not delete the
albumes and archivos it contains. These are moved to the "Root"
category if it is a subcategory that is deleted or to the root of the category list if it is a parent category that is deleted..</li>
<li>The <img src="pics/up.gif" alt="" height="16" width="16"> and <img src="pics/down.gif" alt="" height="16" width="16"> buttons allow you to
order your categories.</li>
<li>The "<strong>Move into</strong>" dropdown lists allow you to change the parent
of a specific category. </li></ul>
<p>"<strong>User galleries</strong>" is a special category. It is not visible unless
you have some users that have created their own gallery. It can't be
deleted but you can edit its title and description by using the <img src="pics/edit.gif" alt="" height="16" width="16"> button. </p>
<p>You can specify how you want categories sorted in Coppermine:
alphabetically (instead of a customized order) by setting "Sort
categories alphabetically" to "Yes". This setting is available both in
Coppermine config and the category manager. If you enable alphabetical
sorting, the move up and move down arrows that normally let you
manually sort the categories will disappear. Disable this feature if
you want to organize your categories in some other order.</p>
<p>You can only assign a picture to the category only if you have an �lbum with images nested directly within it.</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="albmgr"></a><h2>4.6 The Album Manager</h2>
<p><img src="pics/es_albmgr.gif" alt="" title="Album Manager" border="0" height="425" width="485"></p>
<p>Coppermine stores archivos inside of albumes, so you'll need at
least one �lbum for your pictures/archivos to be placed in. Albums can
be stored in categories (but they don't <em>HAVE</em> to be in a category, they can just as well go into the Coppermine "root").</p>
<p>When you click on "albumes" in the admin menu, you will see the <em>Album Manager</em>.</p>
<h3><a name="albmgr_create"></a>4.6.1 Creating albumes</h3>
<ul>
<li><strong>Choose a category from the dropdown list</strong> "Select
category" and highlight the selection where you would like your �lbum
to reside in. (or choose "* No category *" if the �lbum should go into
the Coppermine "root"). If you haven't created a category yet, go to
the <a href="#cat_cp">categories control panel</a> first. Or, you can
proceed with these steps to first create an �lbum and move the �lbum
into a category later. You can also perform this moving task by using
the <a href="#%E1lbum_prop">�lbum properties</a> p�gina.</li>
<li><strong>To create an �lbum, click on the "New" button</strong> - a new �lbum will appear on the list, by default this �lbum is labelled "New �lbum"</li>
<li><strong>Click on the text input field at the bottom of the screen</strong>, highlight the default name "New �lbum" </li>
<li><strong>Then type in the �lbum name you want to use</strong></li>
<li>(repeat steps 2 through 4 to add additional albumes)</li>
<li><strong>Click "Apply modifications"</strong> to submit your changes
to the base de datos. failure to do so will result in the loss of all
the changes you just made. You can always return to this panel to edit
and change �lbum names, sort them within their parent category, and/or
move them to different parent categories.</li>
<li><strong>After clicking to Apply Modification, confirm your intent in the alert box with &the quot;OK" </strong> (<em>Are you sure you want to make these modifications ? button.</em>)</li>
</ul>
<h3><a name="albmgr_rename"></a>4.6.2 Renaming albumes</h3>
<ul>
<li><strong>Choose a category from the dropdown list</strong></li>
<li><strong>Click on the �lbum you want to change</strong></li>
<li><strong>Click on the text input archivod at the bottom of the screen</strong>, highlighting the �lbum name</li>
<li><strong>Type the �lbum name you want to assign</strong></li>
<li><strong>Click "Apply modifications"</strong></li>
<li><strong>After clicking to Apply Modification, confirm your intent in the alert box with &the quot;OK" </strong> (<em>Are you sure you want to make these modifications ? button.</em>)</li>
</ul>
<h3><a name="albmgr_order"></a>4.6.3 Changing the �lbum order</h3>
<ul>
<li><strong>Choose a category from the dropdown list</strong></li>
<li><strong>Click on the �lbum you want to move up or down in the list</strong></li>
<li><strong>Use the arrow buttons to move the �lbum up<img src="../images/move_up.gif" alt="" title="move the �lbum up" border="0" height="21" width="26"> or down<img src="../images/move_down.gif" alt="" title="move the �lbum down" border="0" height="21" width="26"></strong></li>
<li><strong>Click "Apply modifications"</strong></li>
<li><strong>After clicking to Apply Modification, confirm your intent in the alert box with &the quot;OK" </strong> (<em>Are you sure you want to make these modifications ? button.</em>)</li>
</ul>
<h3><a name="albmgr_delete"></a>4.3.4 Deleting albumes</h3>
<ul>
<li><strong>Choose a category from the dropdown list</strong></li>
<li><strong>Click on the �lbum you want to delete</strong></li>
<li><strong>Click the "Delete" button</strong></li>
<li><strong>Confirm the alert box with "OK"</strong> (<em>Are you sure you want to delete this �lbum ? All archivos and comments it contains will be lost !</em>)</li>
<li><strong>Click "Apply modifications"</strong></li>
<li><strong>After clicking to Apply Modification, confirm your intent in the alert box with &the quot;OK" </strong> (<em>Are you sure you want to make these modifications ? button.</em>)</li>
</ul>
<a name="albmgr_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<h2>4.7 Modifying albumes/archivos<a name="modif_alb_pics"></a></h2>
<p>When you are in admin mode there is a menu displayed next to each �lbum</p>
<p></p>
<p><img src="pics/es_album_menu.gif" alt="" border="1" height="152" width="358"></p>
<p><strong>Delete</strong> allows you to delete the �lbum and <strong>(CAUTION</strong>) all archivos within it.</p>
<p><strong><a href="#album_prop">Properties</a></strong> allows you to modify the name, description and permissions of the �lbum</p>
<p><strong><a href="#edit_pics">Edit archivos</a></strong> allows you to modify the title/caption/keywords etc... of the archivos in the �lbum</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="album_prop"></a><h2>4.8 Album properties</h2>
<p><img src="pics/es_edit_album.gif" alt="" border="0" height="634" width="935"></p>
<p>The "Album category" drop down list allows you to move an �lbum from
one category to another. If you set this to "* No category *" then the
�lbum will be displayed on your p�gina principal.</p>
<p>Use <a href="#bbcode">bbcode</a> to add enlaces and additional formatting to your descriptions.</p>
<p>The thumbnail option lets you select the picture that will represent
the �lbum in the �lbum list. Do not assign a picture here if you would
like the �lbum to select images randomly.</p>
<p>If you have set "Users can can have private albumes" to YES on the <a href="#admin">p�gina de configuraci�n</a>, you can determine who will have permission to view the archivos of this �lbum.</p>
<p>When "visitors can upload archivo" is set to YES, it is possible for
them to upload archivos into albumes by enabling this permission.</p>
<a name="album_prop_visitor_start"></a>
<p><strong>Note that only visitors who are members of a <em>group</em> for which the setting "Can upload pictures" is set to YES.</strong>
Members not in the permitted group will not be able to upload archivos
into such an �lbum. Non-registered users are members of the "Anonymous"
group. </p>
<p>The same rules as above apply for "Visitors can post comments" and "Visitors can rate archivos".</p>
<a name="album_prop_visitor_end"></a>
<a name="album_prop_keyword_start"></a>
<p>In 1.4.x the <strong>Album Keyword</strong> is <em>no</em> longer
being used for searching purposes, but, rather, to enlace images from
other �lbum into another. Using this method, archivos/images can be
displayed in various albumes while the archivo itself need only exists
in one �lbum on your webservidor. You simply upload a archivo to one
�lbum as you would normally do, then assign one or more keywords to the
archivo. The keyword function reads blank spaces between words as a
'break' and assumes that these words are separate words. If you must
use phrases for your keywords, connect them with an underscore or by
using the ascii space holder ctrl+Alt+0160 (NOTE: the latter option
only works with latin based character sets.) Each �lbum can only have
ONE (1) keyword or keyword phrase. All pictures residing in different
albumes that you would like to be displayed in this �lbum must have the
same keyword or keyword phrase in their respective keyword fields.
Pictures, unlike albumes can have multiple keywords or keyword phrases
separated by spaces. This provides you with the option to display
pictures in many albumes. For the visitor of these albumes, it will
appear as if the archivo/image had been uploaded to each. </p>
<a name="album_prop_keyword_end"></a>
<a name="album_prop_password_start"></a>
<p><strong>Album Password</strong>: you can specify an �lbum to be
password-protected (instead of relying on the "regular" group-based
permissions). This way, you can even allow access for unlogged users
(guests) who you provide the password to. Use this option, for example,
to set up an �lbum for your family members only by specifying a
password that only they can come up with answering an additional
password hint (e.g. "<em>What was the maiden name of aunt Emma?</em>"),
or you could decide to send the particular password to specific
friends, family or business associates by email. The optional <strong>password hint</strong> will be displayed at the password prompt, when set.</p>
<p>Note: when setting an �lbum password, the permission dropdown field "<em>Album can be viewed by</em>" will be switched automatically to "<em>me only</em>" - this is expected behaviour. If you change the "<em>Album can be viewed by</em>" to another selection, you must disable the �lbum password as well.</p>
<a name="album_prop_password_end"></a>
<a name="album_prop_reset_start"></a>
<h3>4.8.1 Reset �lbum properties</h3>
<img src="pics/es_modifyalb_reset.gif" alt="" border="0" height="152" width="740">
<p>You can reset the number of views count and total ratings in the
�lbum properties panel and even delete all pics at once in the
sub-section "Reset �lbum" by ticking the desired checkboxes and then
submitting the form. To prevent accidental resets, you will have to
place a tick on the checkbox "I'm sure" before changes can be submitted
(the button will be greyed out (disabled) if you don't).</p>
<p>Use these options with care: the deleting of archivos is
irreversible, as well as the reset of views and ratings (you can only
restore views and ratings by manually editing Coppermine's base de
datos entries with third-party tools like <a href="http://www.phpmyadmin.net/" class="external" rel="external">phpMyAdmin</a> - not recommended).</p>
<a name="album_prop_reset_end"></a>
<a name="album_prop_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="edit_pics"></a><h2>4.9 Editing archivos</h2>
<p><img src="pics/es_edit_picture.gif" alt="" border="0" height="399" width="926"></p>
<p>Use this enlace to modify your archivo's title, description, keywords, and custom fields (if they are used).</p>
<p>Use the �lbum drop down menu in the panel to move the archivo between albumes.
Use keywords to enlace archivos to other albumes (see description in the albumes section above).</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<h3>4.9.1 Editing videos<a name="edit_vids"></a></h3>
<p><img src="pics/edit_video.gif" alt="" border="0"></p>
<p>Here, you can modify the title, description, keywords, and custom fields (if they are used) of your video archivos.</p>
<p>Use the �lbum drop down menu to move the video to another �lbum.</p>
<p>Use the height and width fields to set the size of the video.</p>
<p>Video uploads are possible beginning with cpg1.3.0 (or latter) and
are included as part of the distribution package. For cpg1.2.1 you must
install a separate modification.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<h3>4.9.2 Custom Thumbnails<a name="cust_thmb"></a></h3>
<p><img src="pics/cust_thmb.gif" alt="" border="1"></p>
<p><strong>Order of thumbnails:</strong><br>
<strong class="important">Thumbnails are defined by different levels
(these are: user-defined, tema-defined, global) then in the order of
their type (archivo-specific, extension-specific, media-specific).</strong>
User-defined thumbnails are stored in the directorio where the parent
archivo is located. Theme-defined thumbnails are stored in the temas
'images' directorio. Global thumbnails are stored within the 'images'
directorio of the Coppermine root. <strong class="important">Thumbnails can be one of the following archivo types: 'gif', 'png', or 'jpg'.</strong></p>
<p><strong>Types of thumbnails:</strong><br>
<strong class="important">Archivo-specific thumbnails must have the same base name as the archivo.</strong> Using the above screenshot of a video archivo as an example, the thumbnails for this archivo could be 'thumb_<strong>thailand_waterfall</strong>.gif', 'thumb_<strong>thailand_waterfall</strong>.png', or 'thumb_<strong>thailand_waterfall</strong>.jpg', and searched for by cpg in that order.</p>
<p><strong class="important">Extension-specific thumbnails are named after the extension of the archivo.</strong> (Examples: 'thumb_wmv.jpg', 'thumb_wav.jpg'.)</p>
<p><strong class="important">The base name for media-specific thumbnails are 'thumb_movie', 'thumb_document', and 'thumb_audio'.</strong> Images use archivo-specific thumbnails by default.</p>
<p><strong>Uploading:</strong><br>
There are 2 ways to upload custom thumbnails:</p>
<p>1. Have an image already uploaded then upload a video via the upload
p�gina. (or vice versa) The video will share the thumbnail of the image.<br>
</p><br><br>
<p><img src="pics/cust_thmb_3.gif" alt="" border="1"></p>
<p>2. FTP upload both the video and (thumbnail or image) then <a href="#batch_add_pics">batch-add</a>.
If you FTP upload the thumbnail, the thumbnail will be display in the
batch add p�gina instead of the default Coppermine thumbnail. If you
upload an image it will look like the above screenshot. However, when
the both archivos are added to the base de datos, the thumbnail of the
image will be used by the video.</p>
<br><br>
<p><img src="pics/cust_thmb_final.gif" alt="" border="1"></p>
<p>Final result.</p>
<p>Note: If the first method is used and the image later deleted, the
thumbnail will also be deleted and the default Coppermine thumbnails
will be displayed, instead.<br>
If a previously uploaded video is to be uploaded again, via FTP, the
accompanying thumbnail must also be uploaded, via FTP, to the same
directorio.</p>
<p>Video uploads are permitted from verstion 1.3.0 of cpg (or better)
and are included as part of the distribution package. For cpg1.2.1,
this option is only available as a separate modification. The use of
custom thumbnails aren't supported in versi�ns prior to 1.3.0. <strong class="important"> NOTE: Using the above instructions, a custom thumbnail can be applied to any archivo, not just videos.</strong></p>
<p><strong>FAQS:</strong></p>
<ul>
<li><strong>Quote</strong><br><div class="quote">I have a video named <strong>'movie.wmv'</strong>, when I upload a thumbnail for it <strong>'thumb_movie.jpg'</strong> it replaces the thumbnails for multiple videos!!!!</div>
Duhh. <strong>'thumb_movie.jpg'</strong> is a <em>media-specific</em> thumbnail. Rename the video and the thumbnail with something other than just <strong>'movie'</strong>.</li>
<li><strong>Quote</strong><br><div class="quote">I can't find my user's directorio!</div>
From within Coppermine, browse to the user's �lbum. Look in the url of
your browser and you should see the directorio's name. (See screenshot
for an example.)<br>
<img src="pics/user_folder_link.gif" alt=""><br>
Your users can upload their own thumbnails by using this trick: Create
an �lbum. Change the permissions on it so no one can view it except
that specific user. Then upload the fullsized images of the thumbnails
to this directorio. Archivos outside this �lbum will be able to use the
thumbnails of these images. (See above for naming.)</li>
<li><strong>Quote</strong><br><div class="quote">How do I stop my users from creating their own custom thumbnails?</div>
Currently, this is not possible.</li>
</ul>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="edit_pics_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="bbcode"></a>
<h2>4.10 Using bbcode to insert links and special formatting in various description fields</h2>
<p>Coppermine understands the following bbCodes (the same bbCodes that are used by phpBB and many other BBS apps) in image and album description</p>
<ul>
<li><tt class="code">[b]Bold[/b]</tt> => <strong>Bold</strong></li>
<li><tt class="code">[i]Italic[/i]</tt> => <em>Italic</em></li>
<li><s><tt class="code">[url=http://yoursite.com/]Url Text[/url]</tt> => <a href="http://yoursite.com">Url Text</a></s> (* see below)</li>
<li><tt class="code">[email]user@domain.com[/email]</tt> => <a href="mailto:user@domain.com">user@domain.com</a></li>
<li><tt class="code">[color=red]some text[/color]</tt> => <span style="color:red">some text</span></li>
<li><s><tt class="code">[img]http://coppermine.sf.net/demo/images/red.gif[/img]</tt> => <img src="../images/red.gif" border="0" alt="" /></s> (* see below)</li>
</ul>
<p>(*) As of cpg1.4.21, the bbcode tags [img] and [url] are no longer processed properly. These two tags can be used to launch an attack against your website called a Cross-Site Request Forgery attack (<a href="http://en.wikipedia.org/wiki/Cross-site_request_forgery" rel="external" class="external">CSRF definition</a>). In such an attack a user puts a malicious link in an [img] or [url] tag and can gain control of your website. With such a serious vulnerability, the Coppermine dev team removed processing of these tags to address the immediate risk of such an attack. This is not a final solution but a necessary one.</p>
<p>Now the following processing is done (so that users won't be completely confused):</p>
<ul>
<li><tt class="code">[url=http://yoursite.com/]Url Text[/url]</tt> => Url Text<img src="../images/descending.gif" alt="" title="http://yoursite.com/" /></li>
<li><tt class="code">[url]http://yoursite.com[/url]</tt> => http://yoursite.com<img src="../images/descending.gif" alt="" title="http://yoursite.com" /></li>
<li><tt class="code">[img]http://site.com/image.gif[/img]</tt> => <img src="../images/thumbnails.gif" border="0" alt="" title="http://site.com/image.gif" /></li>
</ul>
<p>As you can see above, no links are displayed for [url] tags, but you will see the link either as plain text or as a mouse-over/tooltip on the image next to the link text: <img src="../images/descending.gif" alt="" />. For [img] tags, a placeholder image (<img src="../images/thumbnails.gif" border="0" alt="" />) is shown with the mouse-over/tooltip showing the image link.</p>
<p>We realize that some administrators will want to process [img] and [url] tags correctly. The Coppermine dev team is working on a solution for cpg1.5 and also one that can be applied to cpg1.4. Information can be found on this <a href="http://forum.coppermine-gallery.net/index.php/topic,58309.0.html" rel="external" class="external">thread</a> on the Coppermine support forum. For those who want to hack the code themselves, the relevant function is <tt class="code">bb_decode()</tt> in <tt class="code">include/functions.inc.php</tt>. Please be <strong>very</strong> careful to address CSRF attacks and read as much as you can about them before going live on your website with your hacked fix.</p>
<a name="bbcode_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="ftp"></a><a name="uploading"></a>
<h2>4.11 Uploading pics/archivos</h2>
<p>There are several methods to upload archivos within Coppermine. You (as gallery admin) should use <a href="#batch_add_pics">FTP-upload plus batch-add</a> (only the admin can do this). Regular users are supposed to use the "regular" <a href="#upload_http">http upload</a> or (if they have Windows XP) the <a href="#xp">XP Publisher</a>.</p>
<a name="uploading_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="ftp"></a><a name="batch_add_pics"></a>
<h3>4.11.1 Uploading pics by FTP / Batch-Add Pictures</h3>
<p>It is recommended that the Coppermine admin use ftp to upload
multiple pics/archivos at a time. Use your ftp software to create
sub-directorios within <em>your_Coppermine_directorio/albumes/</em>, where your ftp uploads can be saved. Though not mandatory, it's always a good idea to have a directorio structure within the <em>albumes</em> directorio that reflects or mirrors your Coppermine categories and albumes.</p><p><span class="important">Important</span>: do not create directorios or ftp upload to the <em>userpics</em>- nor to the <em>edit</em>-directorio by ftp: these directorios are used by Coppermine internally and must not be used for any other purpose! <strong><strong>Folder names must not contain dots</strong></strong>. We also highly recommend refraining from the use of any other special characters - use only a-z, numbers and <tt class="code">-</tt> (dashes) or <tt class="code">_</tt> (underscores) to fill blank spaces. aseg�rese to upload in binary or auto-mode.</p>
<p>Once you have uploaded your photos by ftp, click on the "Batch Add Pictures" button. The batch-add is performed in three steps:</p>
<ul>
<li>find the directorio under which you have uploaded your photos. Select this directorio by clicking on it.
<br><img src="pics/es_searchnew_1.gif" alt="" border="0" height="304" width="775"><a name="ftp_select_dir_end"></a></li>
<li><a name="ftp_select_archivo"></a>select the photos you wish to
upload (by ticking them). New pics are automatically pre-selected,
those that already are in your Coppermine base de datos are not
selected. Next select thee �lbum you wish to insert them into. Click
"Insert Selected Pictures" to start the batch-add process.<br>
<img src="pics/es_searchnew_2.gif" alt="" border="0" height="385" width="740"><a name="ftp_select_archivo_end"></a></li>
<li><a name="ftp_show_result"></a>CPG will then display the results of the batch-add (allow some time for all results to display).<br>
If the OK, DP, or PB 'signs' does not appear, click on the broken archivo image to see if any error message was produced by PHP.<br>
Should your browser time out, hit the reload button.
<ul>
<li>OK : means that the archivo was succesfully added</li>
<li>DP : means that the archivo is a duplicate and is already in the base de datos</li>
<li>PB : means that the archivo could not be added, check your
configuration and the permission of directories where the archivos are
located</li>
<li>NA : means that you haven't selected an �lbum the archivos should
go to, hit 'back' and select an �lbum. If you don't have an �lbum
create one first</li>
</ul>
<a name="ftp_show_result_end"></a></li>
</ul>
<p>Giving FTP-access to other users can pose a serious security threat,
this is why batch-add is only available for the Coppermine gallery
admin.</p>
<p>Once archivos have been added to Coppermine's base de datos,
aseg�rese that you never rename or delete them via ftp - use
Coppermine's admin menu options to remove or rename archivos, instead.
Only in this way will these archivos be removed from both the archivo
system <strong>and</strong> the base de datos.</p>
<a name="ftp_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="upload_http"></a>
<h3>4.11.2 Uploading by HTTP</h3>
<p>Regular HTTP uploads use the browser's built-in capabilities to
upload archivos to a servidor. The maximum archivo size is determined
by two basic factors: the speed and amount of data the web-browser can
upload before timing out, and the allowed archivo size determined by
servidor settings. Note that those settings are not determined by
Coppermine, but the servidor config (php.ini). Users who are proveedor
de hostinged usually can't edit php.ini, so they will have to live with
the settings the webservidor admin has set up. Those who actually run
their own servidor and can edit php.ini should take a look at the
settings if (large) http uploads fail:</p>
<ol>
<li><strong>max_input_time</strong>- 60 seconds is the default time limit for uploading archivos.<br>
This time limit includes the time it takes for the archivos to upload,
so if you exceed this limit, the archivo will not even parse, and the
browser will not get a response. You can workaround this by trying to
upload smaller or fewer archivos, or you can try uploading over
broadband. The best solution, of course, is to increase the time limit
to something more in line with your needs.</li>
<li><strong>upload_max_archivosize</strong> - 2MB is the default limit for individual archivos.</li>
<li><strong>post_max_size</strong> - 8MB is the default limit for post requests.</li>
<li><strong>memory_limit</strong> - 8MB is the default size.</li>
<li>PHP's <strong>LimitRequestBody</strong> - 512KB default limit. (mainly an issue on Redhat/Apache systems. Found in /etc/http/conf.d)<br>
In general, upload_max_archivosize < post_max_size < memory_limit
in order for uploads to function properly. Coppermine may warn you if a
archivo exceeds upload_max_archivosize, but it cannot warn you if the
total size of all the archivos exceeds the post limit or the memory
limit.</li>
<li><strong>archivo_uploads</strong> - This determines whether or not PHP will allow archivo uploads. It must be set to 'On'.</li>
<li><strong>upload_tmp_dir</strong> - This specifies the temporary directorio where PHP stores uploaded archivos.<br>
The most common issue caused by this setting is an open_basedir
warning. In this situation, your servidor administrator has restricted
the archivos that PHP can work with to a certain directorio. If he does
not create and specify a temporary directorio within the open_basedir
restriction, PHP will attempt to use the OS temporary directorio, and
it will be rebuffed by the open_basedir restriction.</li>
<li><strong>allow_fopen_url</strong> - This controls PHP's ability to
read archivos using URL/URIs. If it is disabled, Coppermine will not be
able to upload from URLs.</li>
</ol>
<p>It should be obvious that the archivos have to be uploaded somewhere
(into some directorio) on your webservidor - this is the albumes
directorio within the directorio you installed Coppermine on your
servidor. The HTTP uploads go into subdirectorios of the "userpics"
directorio (which resides within the "albumes" directorio). Obviously,
the Coppermine upload script needs write permissions to upload the
archivos there. This is why you have to change permissions on the
albumes directorio and everything within it during Coppermine install -
make it writable for the user the webservidor runs under. This is done
using the CHMOD command on Unix/Linux based servidors. If you
experience issues with uploading, aseg�rese that you have set the
permissions correctly.</p>
<a name="upload_http_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="xp"></a>
<h3>4.11.3 Using Windows XP Web Publishing Wizard with Coppermine</h3>
<p>If you are using Windows XP, you can use its built-in web publishing wizard to upload your photos to your gallery.</p>
<p>Once you have properly installed the script on your servidor, call
the xp_publish.php archivo from your web browser
(http://your_site.com/Coppermine_dir/xp_publish.php).</p>
<p>The script displays some information on how to do the installation
on the client side and how to use the Wizard. Basically you will need
to download a small archivo created by the script that needs to be
loaded into your Windows registry.</p>
<p>If you want to allow your users to use the Windows XP Web Publishing
Wizard, it's advisable to promote it by showing a enlace to the archivo
somewhere on your p�gina.</p>
<a name="xp_publish_setup"></a>
<h4>4.11.3.1 XP Web Publishing Wizard: Setup</h4>
Before you can use the XP Web Publishing Wizard, it needs to know the address of the your gallery.
<ul>
<li>Open your browser and type the following into the address box
replacing "your_site.com" and "Coppermine_dir" with your own Gallery
address information : <tt class="code">http://your_site.com/Coppermine_dir/xp_publish.php</tt></li>
<li>On "Archivo Download - Security Warning" click "Save" to save the
cpg_###.reg archivo on your Desktop. (The ### represents a 10-digit
numerical timestamp.)</li>
<li>Open Windows Explorer</li>
<li>Select Desktop from the left panel</li>
<li>Double click on the archivo name that you just saved</li>
<li>On Registry Editor's "Are you sure..." dialog click "Yes"</li>
</ul>
Above procedure needs to be done only once by users wishing to use the XP Publishing Wizard.
<a name="xp_publish_upload"></a>
<h4>4.11.3.2 XP Web Publishing Wizard: Uploading pictures</h4>
The process of uploading pictures is a matter of following a simple
dialog. It takes much longer to describe the process than do it.
<ul>
<li>Start Windows Explorer and locate the directorio with your photographs and select one or more pictures for upload.</li>
<li>If the Windows Explorer left panel is not titled "Picture Tasks",
click on the "X" in the top right corner of the panel to close it and
to reveal the Picture Tasks panel.</li>
<li>Select "Publish xxxx to the Web" from "Archivo and Folder Tasks" on
the left panel. "xxxx" could say "this archivo, these archivos or this
directorio" depending on what is highlighted on the right panel.</li>
<li>On Web Publishing Wizard's Welcome screen click "Next".</li>
<li>You can change your selection if necessary on the Thumbnail window showing up. Click "Next" when you are ready.</li>
<li>From the service provider window highlight your Photo Gallery name and click "Next".</li>
<li>Enter your Coppermine username and password to login to your gallery and click "Next".</li>
<li>From the "Welcome username" window you have an option of uploading
your picture(s) into one of the existing albumes or starting a new
�lbum. Click "Next" when you are ready.</li>
<li>Click "Next" in the upload starting confirmation window.</li>
<li>Select the picture sizes for the uploaded pictures. If you are
unsure about acceptable picture sizes, verify with your Gallery
administrator. Click "Next" when you are ready.</li>
<li>You are presented with the last window of the dialog and given a choice of opening the Gallery when the upload is complete.</li>
<li>Click "Finish" to end the XP Web Publishing Wizard and to enter the Gallery to check the new �lbum contents.</li>
</ul>
<p class="small">[cpg1.1.1 or better required]</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="upload_trouble"></a>
<h3>4.11.4 Upload troubleshooting</h3>
<p>If you are experiencing issues with Coppermine's upload process,
temporarily change your Coppermine settings as suggested below to get
more detailed error messages:</p>
<ul>
<li>Go to your Coppermine p�gina and log in as admin</li>
<li>Go to the config screen</li>
<li>Scroll to the bottom of the p�gina</li>
<li>Expand the "Maintenance settings" section by clicking on it</li>
<li>Enable debug mode for everyone</li>
<li>Leave display of notices switched off</li>
<li>Save the new settings by clicking on "Save new configuration"</li>
<li>Go to the "groups" panel</li>
<li>Set the upload form configuration for all groups to "Single archivo uploads only" (set <em>Archivo upload boxes</em> to "1", <em>URI upload boxes</em> to "0" and <em>No. of boxes</em> to "fixed")</li>
<li>Save your new settings</li>
</ul>
<p>Then try to upload (using http uploads, even if you experienced
troubles using another upload method) - you should get a more detailed
error message that tells you what exactly goes wrong with your uploads.
If the error message doesn't mean anything to you, <a href="http://coppermine-gallery.net/forum/index.php?action=search" rel="external" class="external">search the support board</a> for the error message you get.<br>
<span class="important">When asking for support on the Coppermine forum, post a enlace to your site and a <a href="#user_cp_new">test user account</a>
(the test user mustn't be in the admin group!) with upload privileges,
with the above mentioned settings in place - this way, supporters can
see the error messages as well. Do not post debug_output unless
requested.</span></p>
<p>When people have issues with uploading and decide to post their
question on the Coppermine support board, they usually are told to read
this upload troubleshooting section. Many of them fail to do so
properly, which results in frustration both for users as well as
supporters. To make this absolutely clear: the above mentioned steps
are absolutely <strong>mandatory</strong>, no matter what skill level you have, no matter what upload method you have troubles with. Failing to do <strong>exactly</strong> as suggested will result in your request for help being ignored. Yes, this applies to you. We mean it!</p>
<a name="upload_trouble_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<h2>4.12 The gallery configuration p�gina<a name="admin"></a></h2>
<p>This is where you will configure the most important parts of your
Coppermine gallery. Some settings have an impact on the archivos you
upload - changing the ( * ) astericked options after you have alreaded
added a large number of archivos in your gallery can be a difficult
undertaking. For this reason, it is important that you spend time with
your Coppermine setup at the early stages of gallery development to get
those settings exactly the way you want them, before actually uploading
too many pics or listing the gallery to the general public.</p>
<a name="admin_general"></a>
<h3>4.12.1 General settings</h3>
<a name="admin_general_name"></a><h4>Gallery name</h4>
<p>Enter the name of your gallery in this text field. The name you
enter will appear as the title that is displayed in the web browser's
title bar and is also displayed in many of the different tema templates.</p>
<a name="admin_general_name_end"></a>
<a name="admin_general_description"></a><h4>Gallery description</h4>
<p>Enter a short description of your gallery in this text field. This
description is also displayed in some of the tema templates just below
the name of your gallery.</p>
<a name="admin_general_description_end"></a>
<a name="admin_general_email"></a><h4>Gallery administrator email</h4>
<p>All emails sent by the gallery will be sent using this email address. This must be a valid email address.</p>
<a name="admin_general_email_end"></a>
<a name="admin_general_Coppermine-url"></a><h4>URL of your Coppermine gallery directorio</h4>
<p>This is the URL where a user will be directed to when s/he clicks on the "See more pictures" enlace in an e-card. This <em>must</em>
be the URL to the root of your Coppermine installation followed by a
forward slash (just the path to your Coppermine directorio, e.g. <em>http://yourdomain.tld/Coppermine/</em>). Do not specify a specific archivo (such as index.php) or subdirectorio within the Coppermine gallery in this field.</p><p>In
previous versi�ns of Coppermine, this field was called "Target address
for the 'See more pictures' enlace in e-cards", but as this url is now
being used for other functions in Coppermine, it has been changed,
appropriately.</p>
<a name="admin_general_Coppermine-url_end"></a>
<a name="admin_general_home-url"></a><h4>URL of your p�gina de inicio</h4>
<p>This is the URL where a user will be directed when he clicks on the "Home" button in the main menu.</p>
<p>You can use "/" for the root of your domain, "index.php" for your
gallery's default starting p�gina, or any other valid URL. By default
this is "index.php".</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_general_home-url_end"></a>
<a name="admin_general_zip-download"></a><h4>Allow ZIP-download of favorites</h4>
<p>When enabled, users of your site may download archivos that they previously saved into their <em>favorites</em>
collection. These archivos are dowloaded from the user's "My favorites"
p�gina and saved onto their computers in a zip-archivo format. This
option requires zlib to be installed on your servidor (run <a href="http://www.php.net/phpinfo" class="external">phpinfo</a> to check if this php library archivo exists on your servidor).</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_general_zip-download_end"></a>
<a name="admin_general_time-offset"></a><h4>Timezone difference relative to GMT</h4>
<p>Specify the time zone difference between your local time and the
time zone your webservidor is in. This value will be used to adjust
time stamps in ecards and other places.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_general_time-offset_end"></a>
<a name="admin_general_encrypt_password_start"></a><h4>Enable encrypted passwords</h4>
<p>This option affects changes on user passwords that are stored as
plain text in your base de datos (this is the case if you have upgraded
from previous versi�ns of Coppermine that did not have this feature).
It will encrypt all passwords in the base de datos, and all future
passwords will be stored encypted as well. This process can not be
reversed: once encryption in turned on, it can not be turned off, so
use this option only after giving it some serious consideration.</p>
<p>This option increases user security in Coppermine, but comes with a
drawback inherent to this method: even the admin will not be able to
recover a lost password of a user (or his own password). The password
can only be reset to another value using the "I forgot my password"
option during login.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_general_encrypt_password_end"></a>
<a name="admin_general_help"></a><h4>Enable help-icons</h4>
<p>Enables the display of help icons in various sections of the
Coppermine admin pages. When enabled, aseg�rese you have also uploaded
the "docs" directorio into your Coppermine directorio on your
webservidor.</p>
<p>If you choose to set this to "Yes: everyone", logged in (registered)
users will be able to see the help icons in strategic locations as
well, e.g. when creating a user gallery.</p>
<p>As the help text is based on the documentation that comes with
Coppermine, it is available in English only. If the native language of
your user(s) is not English, it is advisable to set this option to
"Yes: admin only" to avoid confusion among your users.</p>
<p>It is strongly recommended that you do not disable the help icons
altogether: even though you feel that you know your way around in your
Coppermine install, the help icons might help you with the functinos of
a new or unfamiliar option later.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_general_help_end"></a>
<a name="admin_general_keywords_start"></a><h4>Enable clickable keywords in search</h4>
<p>When enabled, a list of all keywords entered in the "<a href="#edit_pics">Edit archivos</a>"
p�gina will appear at the bottom of the search p�gina, with each
keyword being a clickable search enlace. Enabling this option is
recommended only if you have a small number of keywords in use (e.g.
less than 100) - it will provide your users with some ideas as to what
they could be searching for in your gallery (in addition to the
standard full-text search). Please note that enabling this option for a
large list of keywords (e.g. thousands of keywords) can slow down the
p�gina de b�squeda considerably and may be confusing for new users and
visitors to your site.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_general_keywords_end"></a>
<a name="admin_general_enable-plugins"></a><h4>Enable plugins</h4>
<p>Enable or disable <a href="#plugin">plugins</a>, with a enlace to the <a href="#plugin_manager">plugin manager</a>.
This is a brand-new feature of Coppermine. This feature allows advanced
Copperminers to create plug-ins that can control the way Coppermine
looks and behaves without modifying the inherent code of the script
itself. We anticipate many exciting, user-contributed, plug-ins in the
near future. More details can be found in the <a href="#plugin_start">plugins section of this documentation</a>.
Since plugins add on to the core Coppermine system, if you are having
problems, try to disable all plugins using this setting to see if a
plugin may be at fault. If so, you can then enable all plugins here,
then uninstall or install one plugin at a time in the <a href="#plugin_manager">plugin manager</a> to figure out which one is at fault.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_general_enable-plugins_end"></a>
<a name="admin_general_private-ip"></a><h4>Allow banning of non-routable (private) IP addresses</h4>
<p>Today, most people on the internet have dynamic IP addresses that
are assigned to them when connecting to the internet by their Internet
Service Provider. These IP addresses change each time the user connects
to the internet, but during an internet session these IP addresses are
"visible" at the web-sites that thee user is surfing. Within the range
of all IP addresses (0.0.0.0 to 255.255.255.255), certan ranges are
reserved for special purposes (mostly for the use on private networks).
The banning feature will not accept IP addresses banning of addresses
that belong to these private ranges (e.g. 192.168.0.1). This is
necessary to prevent unexperienced, as well as experienced, Coppermine
admins from banning IP addresses within their own LAN. If you're
actually running Coppermine on your LAN/WAN that uses private IP
addresses (e.g. on a company's intranet) and you want the authority to
be able to ban users, switch this option to "Yes". If you're running
Coppermine on a webservidor located in the internet (e.g. you're
proveedor de hostinged), you should keep this option set to "No".<br>
If you don't use banning at all, you can safely ignore this setting completely.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_general_private-ip_end"></a>
<a name="admin_general_browsable_batch_add"></a><h4>Browsable batch-add interface</h4>
<p>When <a href="#batch_add_pics">batch-adding</a> archivos (that you have uploaded using <acronym title="Archivo Transfer Protocol">FTP</acronym>
before) to your gallery, you have the option to switch between a
browsable list, where you can go scroll through the directorio
structure in your <tt class="code">albumes</tt>-directorio or to
display the whole directorio structure at once. Enable this option if
you have a larger structure of directories and subdirectories you want
to browse through (this requires your browser to be capable of
displaying <a href="http://www.w3schools.com/tags/tag_iframe.asp" class="external" rel="external">iframes</a>).
Set this option to "No" (disabled) if you want to use the "classic"
Coppermine interface that shows a complete list of the structure at
once.<br>
Should you have difficulties using one, try the other. You can toggle between these options on the <a href="#batch_add_pics">batch-add</a> page as well.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_general_browsable_batch_add_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_language"></a>
<h3>4.12.2 Language & Charset settings</h3>
<p><img src="pics/es_config_language.gif" alt="" border="1" height="201" width="764"></p>
<a name="admin_language_language"></a><h4>Language</h4>
<p>This sets the default language for your gallery. All language archivos are stored in the <strong>lang</strong> directorio on your servidor.</p>
<p>Language archivos with an "<strong>-utf8</strong>" suffix are
unicode encoded archivos. If you select an -utf8 archivo as the default
language and you set "Character encoding" to "Unicode (utf-8)" then the
script will auto detect the preferred language of your visitors based
on what default language is configured in their browsers. If the
corresponding language is available in your language directorio, it
will be used. Otherwise, the default language archivo will be used.</p>
<p>When the script auto detects the preferred language, it stores the
result in a cookie on the visitor's computer. To reset this cookie (and
thus force the script to do another auto detection) the user must call
this autodetect function with something like: <a href="#">http://yoursite.com/Coppermine_dir/index.php?lang=xxx</a></p>
<p>Once you have added comments or archivos to your gallery, you should
not change the character set of your gallery. If you do so, non-ASCII
characters may display properly.</p>
<a name="admin_language_language_end"></a>
<a name="admin_language_fallback"></a><h4>Fallback to English if translated phrase not found?</h4>
<p>Enable this option if you're using languages other than english. If
a certain word or phrase doesn't exist within your language archivo,
Coppermine will display the equivalent english phrase, instead.</p><p>This
feature has been introduced to allow the use of previous versi�n
language archivos -- language archivos that may have not been
translated for the this versi�n, yet. Until an updated versi�n of the
language archivo is made available, you can use this option. Most
translation differences affect the admin part of Coppermine only, so
the admin will experience most of these untranslated strings. The admin
will see some phrases in english instead of his/her preferred language
for strings and words that don't exist in the currently available
language archivo. NOTE: this fallback option only works for 95% of all
phrases, there may still be some other translation omissions.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_language_fallback_end"></a>
<a name="admin_language_charset"></a><h4>Character encoding</h4>
<p>This should normally be set to "Unicode (utf-8)" (or "Default (language archivo)"). See the discussion in the "<strong><a href="#admin_language">language</a></strong>" section of this p�gina.</p>
<a name="admin_language_list"></a><h4>Display language list</h4>
<p>Enable this option if you want your users to be able to select a
preferred language from a dropdown list (you can specify to display
only the list itself or a label saying "<strong>Choose your language:</strong>"
in front of the list). Edit your template archivo
(/themes/yourtheme/template.html) to specify where the language
dropdown list should appear on your gallery (look for the call tag: <strong>{LANGUAGE_SELECT_LIST}</strong>).</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_language_list_end"></a>
<a name="admin_language_flags"></a><h4>Display language flags</h4>
<p>Enable this option if you would like the option of having your users
select languages appropriate for their use by merely clicking on a flag
icon which representing their language or country (you can specify to
display the flags themselves or include a label that states: "<strong>Choose your language:</strong>"
in front of the flags). Edit your template archivo
(/themes/yourtheme/template.html) to specify where the flags should
appear in your gallery (look for the call tag:<strong>{LANGUAGE_SELECT_FLAGS}</strong>).</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_language_flags_end"></a>
<a name="admin_language_reset"></a><h4>Display "reset" in the language selection</h4>
<p>This option only applies only if you enabled user language selection
- it will show a "default"-icon or list entry to let the users go back
to the original language of your gallery.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_language_reset_end"></a>
<a name="admin_language_charset_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_tema"></a>
<h3>4.12.3 Themes settings</h3>
<a name="admin_tema_tema"></a><h4>Theme</h4>
<p>Use this dropdown list to select the default tema for your gallery (Themes are stored in sub-directories of the <strong>temas</strong> directorio ).</p>
<a name="admin_tema_tema_end"></a>
<a name="admin_tema_tema_list"></a><h4>Display tema list</h4>
<p>Enable this option if you want your users to be able to select other
temas from a dropdown list (you can specify to display only the list
itself or a label saying "<strong>Choose your tema:</strong>" in front
of the list). Edit your template archivo
(/themes/yourtheme/template.html) to specify where the tema dropdown
list should appear on your gallery (look for <strong>{THEME_SELECT_LIST}</strong>).</p>
<p>This option only makes sense if you have at least one alternative
tema in your /themes/ directorio other than your default tema. We
recommend using this option only if there's are additional benefits for
the user (for example a tema with less graphics in it that loads faster
for users on a dial-up connection, or a tema with reduced color
pallettes and good contrast).</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_tema_tema_list_end"></a>
<a name="admin_tema_tema_reset"></a><h4>Display "reset" in tema selection</h4>
<p>This option applies only if you enabled the user tema selection
option - it will show a "default" list entry to let the users go back
to the original tema of your gallery.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_tema_tema_reset_end"></a>
<a name="admin_tema_faq"></a><h4>Display FAQ</h4>
<p>This option adds a "FAQ" enlace to the menu bar when enabled. If a
user clicks on it, it will display a list of "Frequently asked
question" on how to use Coppermine. To change the content of the FAQ,
edit the archivo /your_Coppermine_directorio/lang/yourlanguage.php
(e.g. english.php) and look for</p>
<pre>// ------------------------------------------------------------------------- //
// Archivo faq.php
// ------------------------------------------------------------------------- //</pre>
<p>Edit the content that comes after it.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_tema_faq_end"></a>
<a name="admin_tema_custom_lnk_name"></a><h4>Name of your custom enlace</h4>
<p>Use this if you want to create a custom enlace that will appear in
the menu. What you enter here will be the name of the menu enlace or
button. Leave space blank if you do not have any specific use for it.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_tema_custom_lnk_name_end"></a>
<a name="admin_language_custom_lnk_url"></a><h4>URL of your custom enlace</h4>
<p>This is the URL where the user's browser will be directed to when
s/he clicks on the "Custom enlace name" button in the main menu.</p>
<p>You can use any valid URL.</p>
<p>Leave this blank if you do not have any specific use for it.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_language_custom_lnk_url_end"></a>
<a name="admin_tema_bbcode"></a><h4>Display bbcode help</h4>
<p>When enabled, this will display the <a href="#bbcode">bulletin board codes</a> that may be used in description fields to help with the formatting of text, images and enlaces.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_tema_bbcode_end"></a>
<a name="vanity_block"></a><h4>Display the vanity block on temas that are defined as XHTML and CSS compliant</h4>
<p>When enabled and using a tema that has been defined as XHTML and CSS
compliant, the vanity block will be shown. The vanity block contains
the logos and enlaces for HTML and CSS compliance at w3.org, as well as
pointers to the PHP, and MySQL projects.</p>
<p class="small">[cpg1.4.2 or better required]</p>
<a name="vanity_block_end"></a>
<a name="admin_tema_include_path_start"></a>
<h4>Path to custom header include</h4>
<p>Optional relative path to a custom header archivo. Using this
option, you can include non-Coppermine code bits to be included into
your tema, e.g. an overall navigation that gets included on your whole
website. You can only add a relative path (seen from the root path of
your Coppermine install) - not an absolute one, nor a http include from
another website. This option is only meant for experienced users who
have some PHP know-how. </p>
<p><span class="important">Warning: you mustn't include full html p�ginas that contain an html header or footer (tags like <tt class="code"><head></tt> or <tt class="code"><body></tt>), nor can the included archivo do archivo header manipulation, e.g. reading another (non-Coppermine) cookie.</span></p>
<p class="small">[cpg1.4.0 or better required]</p>
<h4>Path to custom footer include</h4>
<p>Optional relative path to a custom footer archivo. The same remarks apply as for the custom header include path.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_tema_include_path_end"></a>
<a name="admin_tema_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_album_list"></a>
<h3>4.12.4 Album list view</h3>
<a name="admin_album_table-width"></a>
<h4>Width of the main table (pixels or %)</h4>
<p>The number you type in here becomes the default width of the display
tables used on your p�gina principal or when you are viewing thumbnails
of an �lbum. You can enter the width in pixels or specify it in
percentages. The default value is 100%.</p>
<a name="admin_album_table-width_end"></a>
<a name="admin_album_category-levels"></a>
<h4>Number of levels of categories to display</h4>
<p>The default value is 2. With this value the script will display the current categories plus one level of sub-categories.</p>
<a name="admin_album_category-levels_end"></a>
<a name="admin_album_number"></a>
<h4>Number of albumes to display</h4>
<p>This is the number of albumes to display on a p�gina. If the current
category contains more albumes than what is allowed on the p�gina, the
�lbum list will be split over multiple p�ginas with tabs at the bottom
of each �lbum list table that users can click on to advance to the next
set of albumes in a particular category.</p>
<a name="admin_album_number_end"></a>
<a name="admin_album_columns"></a>
<h4>Number of columns for the �lbum list</h4>
<p>Self-explanatory. The default value is 2.</p>
<a name="admin_album_columns_end"></a>
<a name="admin_album_thumbnail-size"></a>
<h4>Size of thumbnails in pixels</h4>
<p>This sets the maximum size of the thumbnails that are to be
displayed for each �lbum. 50 means that the thumbnail will fit inside a
square of 50x50 pixels.</p>
<p>If the size you specify there is larger than "Pictures and
thumbnails settings/Max width or height of a thumbnail", the thumbnail
will be stretched. Aesthetically, it is better to have thumbnails
smaller than or equal to the Max width or height settings here.</p>
<a name="admin_album_thumbnail-size_end"></a>
<a name="admin_album_list_content"></a><a name="changing"></a><h4>The content of the p�gina principal</h4>
<p>This option allows you to change the content of the p�gina principal displayed by the script.</p>
<p>The default value is "<strong>catlist/alblist/random,2/lastup,2</strong>"</p>
<p>You can use the following "codes" to include other items:</p>
<ul>
<li>'<strong>breadcrumb</strong>': navigation inside the gallery (e.g. "home > category > subcategory > �lbum")</li>
<li>'<strong>catlist</strong>': category list</li>
<li>'<strong>alblist</strong>': �lbum list</li>
<li>'<strong>random</strong>':
random archivos (leaving random archivos "on" for huge galleries with
more than 10,000 pics might result in performance problems; switch
random "off" in this case)</li>
<li>'<strong>lastup</strong>': last uploads</li>
<li>'<strong>topn</strong>': most viewed</li>
<li>'<strong>toprated</strong>': top rated</li>
<li>'<strong>lastcom</strong>': last comments </li>
<li>'<strong>lasthits</strong>': last viewed </li>
<li>'<strong>anycontent</strong>':
inserts php-generated content that has to reside within the archivo
'anycontent.php' into the index page. Can be used to include
banner-rotation scripts or similar.</li>
<li>'<strong>lastalb</strong>': last created albumes</li>
</ul>
<p>Unless you really know what you are doing you should always keep catlist and alblist in "<em>the content of the p�gina principal</em>", as they make up the core parts of the index page or any gallery site, for that matter.</p>
<p>The <strong>,2</strong> dictates that cpg should display 2 rows of thumbnails.</p>
<a name="admin_album_list_content_end"></a>
<a name="admin_album_first-level_thumbs"></a>
<h4>Show first level �lbum thumbnails in categories</h4>
<p>Use this setting to choose whether or not to display thumbnails from
the first �lbum of the categories listed on the default gallery entry
page.</p>
<a name="admin_album_first-level_thumbs_end"></a>
<a name="admin_album_list_alphasort_start"></a>
<h4>Sort categories alphabetically (instead of custom sort order)</h4>
<p>You can dictate that Coppermine sort all categories alphabetically
(instead of in a custom order) by setting "Sort categories
alphabetically" to "Yes". This setting is accessible both in the
Coppermine config menu and in the category manager. If you enable
alphabetical sorting, the up and down arrows that normally let you move
categories up and down in the custom sorting list will disappear.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_album_list_alphasort_end"></a>
<a name="admin_album_enlaceed_archivos_start"></a><h4>Show number of enlaceed archivos</h4>
<p>If you use �lbum keywords to display images/archivos in more than
one �lbum, enabling this option will display additional information for
the �lbum stats: if an �lbum doesn't only contain "regular" archivos,
but archivos enlaceed via the "<a href="#album_prop_keyword_start">�lbum keyword</a>"
option as well, the number of enlaceed archivos will be displayed
separately like this "3 archivos, last one added on Oct 07, 2004<em>, 3 enlaceed archivos, 6 archivos total</em>".</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_album_enlaceed_archivos_end"></a>
<a name="admin_album_list_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_thumbnail_view"></a>
<h3>4.12.5 Thumbnail view</h3>
<a name="admin_thumbnail_columns"></a>
<h4>Number of columns on p�gina de miniaturas</h4>
<p>Default value is 4 this means that each row will show 4 thumbnails.</p>
<a name="admin_thumbnail_columns_end"></a>
<a name="admin_thumbnail_rows"></a>
<h4>Number of rows on p�gina de miniaturas</h4>
<p>Default value is 3.</p>
<a name="admin_thumbnail_rows_end"></a>
<a name="admin_thumbnail_tabs"></a>
<h4>Maximum number of tabs to display</h4>
<p>When the thumbnails spread over multiple p�ginas, tabs are displayed
at the bottom of the p�gina. This value define how many tabs will be
displayed.</p>
<a name="admin_thumbnail_tabs_end"></a>
<a name="admin_thumbnail_display_caption"></a>
<h4>Display archivo caption (in addition to title) below the thumbnail </h4>
<p>Toggles whether the archivo caption is displayed below each thumbnail while user is in (regular) thumbnail view.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_thumbnail_display_caption_end"></a>
<a name="admin_thumbnail_display_views"></a>
<h4>Display number of views below the thumbnail</h4>
<p>Toggles whether the number of views is displayed below each thumbnail while user is in thumbnail view.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_thumbnail_display_views_end"></a>
<a name="admin_thumbnail_display_comments"></a>
<h4>Display number of comments below the thumbnail</h4>
<p>Toggles the display of the number of comments for below each thumbnail.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_thumbnail_display_comments_end"></a>
<a name="admin_thumbnail_display_uploader"></a>
<h4>Display uploader name below the thumbnail</h4>
<p>Toggles the display of the name of non-admin uploaders below each thumbnail.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_thumbnail_display_uploader_end"></a>
<a name="admin_thumbnail_display_admin_uploader"></a>
<h4>Display names of admin uploaders below the thumbnail</h4>
<p>Toggles the display of admin uploader names below each thumbnail for
users that have the administrators group set as thier default group.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_thumbnail_display_admin_uploader_end"></a>
<a name="admin_thumbnail_display_archivoname"></a>
<h4>Display the archivo name below the thumbnail</h4>
<p>Toggles the display of the archivo name below each thumbnail.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_thumbnail_display_archivoname_end"></a>
<a name="admin_thumbnail_display_description"></a>
<h4>Display �lbum description</h4>
<p>Toggles the display of the �lbum description below each �lbum thumbnail.</p>
<a name="admin_thumbnail_display_description_end"></a>
<a name="admin_thumbnail_default_sortorder"></a>
<h4>Default sort order for archivos</h4>
<p>This option determines the default order in which thumbnails should
be displayed. Your user can override this by selecting a custom sort
order from the sort buttons above the albumes.</p>
<a name="admin_thumbnail_default_sortorder_end"></a>
<a name="admin_thumbnail_minimum_votes"></a>
<h4>Minimum number of votes for a archivo to appear in the 'top-rated' list</h4>
<p>Used to determine how many votes a archivo must receive before
appearing as a "top-rated archivo." If a archivo has received less than
"this value" of votes, it will not be displayed in the "top-rated"
page. This value must be greater or equal to 1.</p>
<a name="admin_thumbnail_minimum_votes_end"></a>
<a name="admin_thumbnail_view_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_image_comment"></a>
<h3>4.12.6 Image view</h3>
<a name="admin_image_comment_table-width"></a>
<h4>Width of the table for picture display (pixels or %)</h4>
<p>The minimum width of the table that will be used to display the intermediate picture.</p>
<p>Examples:<br><tt class="code">600</tt> = The table around the pic
will be 600 pixels wide (if the pic has larger dimensions this table
will expand accordingly to fit the image).<br>
<tt class="code">100%</tt> = use all available space based on the horizontal dimension of the pic.</p>
<a name="admin_image_comment_table-width_end"></a>
<a name="admin_image_comment_info_visible"></a>
<h4>Archivo information are visible by default</h4>
<p>Define whether or not the archivo information block that appears
below the intermediate image should be visible by default (If turned
off, users can still view the info block by clicking on the ( i )
button..</p>
<a name="admin_image_comment_info_visible_end"></a>
<a name="admin_image_comment_descr_length"></a>
<h4>Max length for an image description</h4>
<p>Maximum number of characters that an image description may contain.</p>
<a name="admin_image_comment_descr_length_end"></a>
<a name="admin_image_comment_filmstrip_toggle"></a>
<h4>Show film strip</h4>
<p>Toggles display of a "film strip" showing thumbnails of prior and subsequent archivos in the �lbum.</p>
<p class="small">[cpg1.2.0 or better required]</p>
<a name="admin_image_comment_filmstrip_toggle_end"></a>
<a name="admin_image_comment_display_film_strip_archivoname"></a>
<h4>Display archivo name under film strip thumbnail</h4>
<p>Toggles the display of the archivo name below each thumbnail in the film strip.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_image_comment_display_film_strip_archivoname_end"></a>
<a name="admin_image_comment_filmstrip_number"></a>
<h4>Number of items in film strip</h4>
<p>Sets the number of thumbnails to display in film strip. The number
you can set here is dependent on your thumbnail size and monitor size.
If you do not want to inconvenience users with smaller monitors set
this value between 4-6.</p>
<p class="small">[cpg1.2.0 or better required]</p>
<a name="admin_image_comment_filmstrip_number_end"></a>
<a name="admin_image_comment_slideshow_interval"></a>
<h4>Slideshow interval in milliseconds</h4>
<p>This sets the time that each pic is to be displayed (transition
interval) when a user is viewing a slideshow (the next pic is being
loaded/cached while the current one is being displayed). This setting
must be in milliseconds (1 second = 1000 milliseconds).<br>Remember
that setting this to a very low value may not be in the best interest
for all of your users, especially those who are on dial-up connections,
or if you have large archivos (kb)that may take longer than the
allotted time to display.</p>
<a name="admin_image_comment_slideshow_interval_end"></a>
<a name="admin_image_comment_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_comment_start"></a>
<h3>4.12.7 Comment settings</h3>
<a name="admin_image_comment_bad_words"></a>
<h4>Filter bad words in comments</h4>
<p>Remove "bad words" from comments. The "bad words" list is in the
language archivo. NOTE: Not all language archivos may contain an
equivelent for this list.</p>
<a name="admin_image_comment_bad_words_end"></a>
<a name="admin_image_comment_smilies"></a>
<h4>Allow smilies in comments</h4>
<p>Toggle the use of smilies in comments.</p>
<a name="admin_image_comment_smilies_end"></a>
<a name="admin_image_comment_flood"></a>
<h4>Allow several consecutive comments for a specific pic/archivo from the same user</h4>
<p>This setting toggles flood protection for the comments option. When
set to YES, a user can post another comment, even though he already
posted a previous one. Some users may abuse this setting. The
recommended setting is: NO.</p>
<a name="admin_image_comment_flood_end"></a>
<a name="admin_image_comment_chars_per_word"></a>
<h4>Max number of characters in a word</h4>
<p>This is designed to prevent someone from breaking the flow of your
gallery layout by posting lengthy comments without using spaces between
words. With this default value, "words" that longer than 38 characters
are automatically censored.</p>
<a name="admin_image_comment_chars_per_word_end"></a>
<a name="admin_image_comment_lines"></a>
<h4>Max number of lines in a comment</h4>
<p>Prevent a comment for containing too many "new line" characters (enter key).</p>
<a name="admin_image_comment_lines_end"></a>
<a name="admin_image_comment_length"></a>
<h4>Maximum length of a comment</h4>
<p>Maximum number of characters that a comment may contain.</p>
<a name="admin_image_comment_length_end"></a>
<a name="admin_image_comment_admin_notify"></a>
<h4>Notify admin of comments by email</h4>
<p>Toggle if you want to receive an email each time a comment is being
posted. Warning: only enable this option on sites with very low user
traffic or you may soon find yourself flooded with notification emails.</p>
<a name="admin_image_comment_admin_notify_end"></a>
<a name="admin_comment_sort_start"></a>
<h4>Sort order of comments</h4>
<p>Changes the sorting order of comments made to a archivo.<br>
Ascending: latest comment at the bottom, oldest comment at the top<br>
Descending: latest comment at the top, oldest comment at the bottom</p>
<a name="admin_comment_sort_end"></a>
<a name="comments_anon_pfx"></a>
<h4>Prefix for anonymous comments authors</h4>
<p>If you allowed anonymous comments (permissions set on the <a href="#group_cp">groups</a>
control panel), this prefix will be used for comments left by
unregistered users. This can be helpful in preventing and identifing
unregistered users posing as other registered users (or even an
admininstrators) when leaving comments. Leave this blank if you do not
want a prefix for guest's comments.</p>
<a name="comments_anon_pfx_end"></a>
<a name="admin_comment_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_picture_thumbnail"></a>
<h3>4.12.8 Picture and thumbnail settings</h3>
<a name="admin_picture_thumbnail_jpeg_quality"></a>
<h4>Quality for JPEG archivos</h4>
<p>The quality used for JPEG compression when the script resizes an
image. Values can range from 0 (worst) to 100 (best). By default this
value is set to 80. This value can be set to 75 when using ImageMagick.<br>Do
not change this setting unless you really know what you're doing. Other
settings for thumbnail and intermediate pic (dimensions) may have a
significant and undesireable impact on archivosizes and image quality.</p>
<a name="admin_picture_thumbnail_jpeg_quality_end"></a>
<a name="admin_picture_thumbnail_max-dimension"></a><h4>Max dimension of a thumbnail</h4>
<p>Sets the maximum allowable size in pixels for the specified dimension of your thumbnails.</p><div class="important">When
changing this setting, only archivos that are added after the change
will be affected. Therefore, it is advisable that this setting not be
changed after photos have already been added to the gallery. You can,
however, apply the changes to the existing pictures with the "admin
tools (resize pictures)" utility from the admin menu.</div>
<a name="admin_picture_thumbnail_max-dimension_end"></a>
<a name="admin_picture_thumbnail_use-dimension"></a><h4>Use dimension ( width or height or Max aspect for thumbnail )</h4>
<p>Sets the dimension (height or width) on which the maximum pixel size limitation should apply to.</p><div class="important">When
changing this setting, only archivos that are added after the change
will be affected. Therefore, it is advisable that this setting not be
changed after photos have already been added to the gallery. You can,
however, apply the changes to the existing pictures with the "admin
tools (resize pictures)" utility from the admin menu.</div>
<a name="admin_picture_thumbnail_use-dimension_end"></a>
<a name="admin_picture_thumbnail_intermediate_toggle"></a>
<h4>Create intermediate pictures</h4>
<p>By default, whenever you upload a archivo, the script creates both a
thumbnail of the archivo (archivo name using "thumb_" as its prefix)
and an intermediate versi�n of the archivo(archivo name using "normal_"
as its prefix). If you set this option to NO, the intermediate archivo
will not be created.</p>
<a name="admin_picture_thumbnail_intermediate_toggle_end"></a>
<a name="admin_picture_thumbnail_intermediate_dimension"></a>
<h4>Max width or height of an intermediate picture</h4>
<p>The intermediate pictures are those that appears when you click on a
thumbnail. The default value is 400, it means that the intermediate
picture will be created to fit inside a square of 400x400 pixels. NOTE:
Currently, 33% of your users have monitors set at 800 pixels wide,
another 33% have their settings at 1024 pixels, the rest have settings
less than or greater than these two numbers. Therefore a setting of 600
or less would fit the screens of most users. Keep in mind,however, that
setting this size larger than 400 impacts the archivo size of your
intermediate pictures and the time it takes to download and display on
slower connections.</p>
<a name="admin_picture_thumbnail_intermediate_dimension_end"></a>
<a name="admin_picture_thumbnail_max_upload_size"></a>
<h4>Max size for uploaded archivos (KB)</h4>
<p>Any archivo with a archivo size larger than this value will be
rejected by the Coppermine script. Setting this option to a higher
value than what is actually supported by your webservidor will only
result in "funny" webservidor error messages in lieu of "regular"
Coppermine error messages. Therefore, it is recommended that you set
this value to a size that is slightly lower or equal to the max archivo
size that your servidor is set to handle. The actual size your servidor
can handle cannot be determined by Coppermine (or any PHP script) -
when in doubt, contact your proveedor de hosting.</p> <p>Prior to an
FTP upload of archivos, it is recommended that the admin use their
imaging software to resize (individually or by batch processing) larger
archivos to a more practical size. This will facilitate the FTP process
and the creation of intermediate pictures and thumbnails.</p>
<a name="admin_picture_thumbnail_max_upload_size_end"></a>
<a name="admin_picture_thumbnail_max_upload_dimension"></a>
<h4>Max width or height for uploaded pictures (pixels)</h4>
<p>Limits the height and width dimensions of the pictures that are
uploaded. Resizing large pictures requires a lot of memory and consumes
CPU resources. As a result, there are usually limitations that have
been set by your webservidor (host) regarding the maximum uploadable
archivo sizes - you cannot set this value to one that is higher than
what is actually supported by your webservidor. Contact your proveedor
de hosting/servidor if you are not sure about your site's archivo size
limitations. (Ideally, users will resize their pictures to a more
manageable size prior to attempting any uploads. Determine what you
would like the maximum size for a full size pic should be (dpi and
dimensions, while keeping in mind the screen size of your users) and
use that as a recommended standard for FTP and user HTTP uploads.
Inform your users of this recommended size constraints.)</p>
<a name="admin_picture_thumbnail_max_upload_dimension_end"></a>
<a name="admin_picture_thumbnail_auto-resize"></a><h4>Auto resize images that are larger than max width or height</h4>
<p>During the upload process, if images are larger than the maximum
width or height allowed they will automatically be resized to the
maximum allowable size. Users with especially large archivos should be
advised to resize their pictures outside of Coppermine before uploading
as this process also consumes considerable resources when processed
online.</p>
<p><strong>Note:</strong> How the image is resized (width/height/max aspect) is set in the admin option "<a href="#admin_picture_thumbnail_use-dimension">Use dimension (width or height or Max aspect for thumbnail)</a>"</p>
<p>There are three options:</p>
<ul><li>No - Disabled</li><li>Yes: Everyone - Enabled for all users, including the Admin during batch-add process.</li>
<li>Yes: User only - Enabled only for regular users</li></ul>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_picture_thumbnail_auto-resize_end"></a>
<a name="admin_picture_thumbnail_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_picture_thumb_advanced"></a>
<h3>4.12.9 Archivos and thumbnails advanced settings</h3>
<a name="admin_picture_thumb_advanced_private_toggle"></a>
<h4>Albums can be private</h4>
<p>If set to YES then your gallery can contain albumes that are visible
only to users that belong to a specified group. This is ideal for
creating albumes that contain archivos that you want accessible to only
a select group of people. You could also create a userID and password
and inform specific users/customers of the ID and password needed to
view these archivos. </p>
<p>If a user is a member of a group that can have its own gallery and
this option is turned on then this user will have the permission to
hide any of his/her albumes from other users.</p>
<p>This option does <strong>not</strong> determine whether users can have personal galleries at all, <strong>nor</strong> does it determine who is allowed to upload and who is not (these settings are accessible in the <a href="#group_cp">groups manager</a>). You should only set this option to NO if you really know what you're doing (by default, it is set to YES).</p>
<p class="important">Note: if you switch from 'yes' to 'no' all currently private albumes will become public!</p>
<a name="admin_picture_thumb_advanced_private_toggle_end"></a>
<a name="admin_picture_thumb_advanced_private_icon_show"></a>
<h4>Show private �lbum Icon to unlogged user </h4>
<p>Toggles the display of the private �lbum icons to unlogged users.<br>Set to 'NO', the �lbum is completely hidden from unauthorised users.<br>Set to 'YES', the �lbum name, description and statistics are shown, but not the thumbnails or archivos contained within.</p>
<a name="admin_picture_thumb_advanced_private_icon_show_end"></a>
<a name="admin_picture_thumb_advanced_archivoname_forbidden_chars"></a>
<h4>Characters forbidden in archivonames</h4>
<p>When the archivoname of a archivo that is uploaded contains any one
or more of these characters, the characters will be replaced with an
underscore.</p>
<p>Don't change this unless you know exactly what you are doing.</p>
<a name="admin_picture_thumb_advanced_archivoname_forbidden_chars_end"></a>
<a name="admin_picture_thumb_advanced_pic_extensions"></a>
<h4>Allowed image types</h4>
<p>"<em>ALL</em>" will result in all allowed image archivo types that
your image library (GD or ImageMagick) is capable of handling to be
allowed as uploads and content in your gallery. If you want to restrict
the allowed archivo types to certain types only, enter a
slash-separated list of extensions, e.g. <tt class="code">jpg/bmp/tif</tt></p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_picture_thumb_advanced_pic_extensions_end"></a>
<a name="admin_thumbs_advanced_movie"></a>
<h4>Allowed movie types</h4>
<p>"<em>ALL</em>" will result in all allowed movie archivo types to be
uploaded. If you want to restrict the allowable archivo types to
certain extensions only, enter a slash-separated list of extensions,
e.g. <tt class="code">wmv/avi/mov</tt>.</p>
<p>Note that being able to display a movie requires that the cpg-user
have the necessary codecs properly configured on their computers to
display the movie archivo, e.g. if you allow the archivo type <tt class="faq">mov</tt>, the user who wishes to view the archivo will need to have Apple's Quick-Time plug-in installed. Also note that <tt class="code">avi</tt>
is just a container for different codecs - this means that a computer
which is capable of playing movie1.avi may not be capable of playing
movie2.avi if those archivos have been encoded with different 'avi'
codecs.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_thumbs_advanced_movie_end"></a>
<a name="admin_movie_autoplay"></a>
<h4>Movie Playback Autostart</h4>
<p>If set to YES, movies will instantly start playing when loaded (has
no affect on0 flash archivos, however). Nothing will happen if the user
does not have the necessary codecs installed on their computer.</p>
<a name="admin_movie_autoplay_end"></a>
<a name="admin_picture_thumb_advanced_audio_extensions"></a>
<h4>Allowed audio types</h4>
<p>"<em>ALL</em>" will result in all allowable audio archivo types to
be uploaded. If you want to restrict the allowed archivo types to
certain extensions only, enter a slash-separated list of extensions,
e.g. <tt class="code">wav/mp3/wma</tt>.</p>
<p>Note that being able to listen to an audio archivo requires that the
cpg-user have the necessary codecs properly configured on their
computers to hear these archivos, e.g. if you allow the archivo type <tt class="code">mp3</tt>,
users who wish to listen to the archivo will need to have a media
player installed on their computer that can handle mp3 archivos.</p>
<p class="important">Warning: if your webservidor is not hardened
against an exploit of a vulnerability in the apache webservidor setup,
then it might be a security risk to allow the upload of <tt class="code">ram</tt>, <tt class="code">ra</tt> and <tt class="code">rm</tt>-archivos. If you're not sure, do not allow this archivo types.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_picture_thumb_advanced_audio_extensions_end"></a>
<a name="admin_picture_thumb_advanced_doc_extensions"></a>
<h4>Allowed document types</h4>
<p>"<em>ALL</em>" will result in all allowable document archivo types
to be uploaded. If you want to restrict the allowable archivo types to
certain extensions only, enter a slash-separated list of extensions,
e.g. <tt class="code">txt/pdf</tt>.</p>
<p>Note that being able to browse a document archivo requires the
cpg-user to have a compatible software installed and configured
properly on their computer that is capable of displaying the type of
document in question, e.g. if you allow the archivo type <tt class="code">xls</tt>,
users who wish to browse the archivo will need to have an application
installed on their computer that can display MS-Excel sheets. Be
extremely careful with document that are known to be vulnerable to
virus contamination, embedded or as macros. This is especially true if
you plan to allow users the capability of uploading documents without
admin approval.</p>
<p class="important">Warning: if your webservidor is not hardened
against an exploit of a vulnerability in the apache webservidor setup,
then it might be a security risk to allow the upload of <tt class="code">rar</tt>-archivos. If you're not sure, do not allow this archivo type.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_picture_thumb_advanced_doc_extensions_end"></a>
<a name="admin_picture_thumb_advanced_resize_method"></a>
<h4>Method for resizing images</h4>
<p>Set this to the type of image library you have on your servidor
(must be either GD1, GD2 or ImageMagick). GD2 is the recommended
setting.</p>
<p>If you are using GD 1.x and the colors of your thumbnails or
intermediate image do not display properly, then, chances are, you
actually have GD2 on your servidor - switch this option to GD 2.x</p>
<p>More recent distributions of PHP come pre-packaged with GD - if
you're not sure what you have, set this option to GD2. You can also
look at your PHP settings by pointing your browser to the phpinfo.php
archivo in your gallery. eg, <strong>http://www.yourgallery.com/your_cpg_directorio/phpinfo.php</strong>. For more information on using PHP click on this enlace: <a href="http://www.php.net/phpinfo" rel="external" class="external">phpinfo</a>.</p>
<a name="admin_picture_thumb_advanced_resize_method_end"></a>
<a name="admin_picture_thumb_advanced_im_path"></a>
<h4>Path to ImageMagick 'convert' utility (example /usr/bin/X11/) </h4>
<p>If you intend using ImageMagick convert utility to resize you picture, you must enter the name of the <u>directorio</u> where the convert program is located in this line. Don't forget the trailing "<tt class="code">/</tt>" to close the path. This path must only indicate the <strong>directorio</strong> where the convert utility is located, it should not point directly to the convert utility.</p>
<p>If your servidor is running under Windows, use / and not \ to
separate components of the path (eg. use C:/ImageMagick/ and not
C:\ImageMagick\). This path must not contain any spaces under Windows
so that it will not put ImageMagick in the "Program archivos"
directorio.</p>
<p><strong>ImageMagick will not work properly if PHP on your servidor
is running in SAFE mode and it is a real challenge to get it running
under Windows. Please consider using GD in these cases and don't waste
your time asking for support in the forum with ImageMagick installation
questions. There are just too many things that can prevent ImageMagick
from work properly and without physical access to your servidor it is
extremely difficult to guess what is wrong.</strong></p>
<a name="admin_picture_thumb_advanced_im_path_end"></a>
<a name="admin_picture_thumb_advanced_allowed_imagetypes"></a>
<h4>Allowed image types (only valid for ImageMagick)</h4>
<p>This is the list of image types that the script will accept when
using ImageMagick. Image type detection is performed by reading the
header of the archivo and not by looking at its archivo extension.</p>
<a name="admin_picture_thumb_advanced_allowed_imagetypes_end"></a>
<a name="admin_picture_thumb_advanced_im_commandline"></a>
<h4>Command line options for ImageMagick</h4>
<p>Here you can add options that will be appended to the command line
when executing ImageMagick. Read the ImageMagick Convert manual to see
what is available.</p>
<a name="admin_picture_thumb_advanced_im_commandline_end"></a>
<a name="admin_picture_thumb_advanced_exif"></a>
<h4>Read EXIF data in JPEG archivos</h4>
<p>With this option turned on, the script will read the EXIF data
stored by digicams in JPEG archivos. For cpg1.x to cpg1.2.1, this
option will work only if PHP was compiled with the EXIF extension.
Coppermine 1.3.0 (or better) comes with built-in EXIF support even if
the webservidor itself doesn't have EXIF support, as it uses a <a href="http://www.offsky.com/software/exif/index.php" class="external">separate EXIF class</a>.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_picture_thumb_advanced_exif_end"></a>
<a name="admin_picture_thumb_advanced_iptc"></a>
<h4>Read IPTC data in JPEG archivos</h4>
<p>With this option turned on, the script will read the <a href="http://www.iptc.org/" class="external">IPTC</a> data stored by digicams in picture archivos.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_picture_thumb_advanced_iptc_end"></a>
<a name="admin_picture_thumb_advanced_albumes_dir"></a>
<h4>The �lbum directorio</h4>
<p>This is the base directorio for your "Image Store". The path is relative to the main directorio of the script. </p>
<p>You can use ../ in the path to move-up one level in the directorio tree.</p>
<p>You can <strong>not</strong> use an absolute path there ("/var/my_images/" will not work) and the �lbum directorio must be visible by your web servidor.</p>
<p>This setting mustn't be changed if you already have archivos in your
base de datos. If you do so, all references to your existing archivos
will break.</p>
<a name="admin_picture_thumb_advanced_albumes_dir_end"></a>
<a name="admin_picture_thumb_advanced_userpics_dir"></a>
<h4>The directorio for user archivos</h4>
<p>This is the directorio where archivos uploaded using the web
interface (URL/URI) are stored. This directorio is a subdirectorio of
the �lbum directorio. It's recommended that you leave this setting as
is. Should you decide to change it, keep in mind that the directorio
must exist within the albumes directorio and the path should be
relative to it.</p>
<p>The same remarks as above apply.</p>
<p>When you upload archivos by FTP, store them in a subdirectorio
(directorio) of the "�lbum directorio" and not inside the "directorio
for user archivos". </p>
<p>This setting mustn't be changed if you already have archivos in your
base de datos. If you do, all reference to previously existing archivos
will no longer be valid.</p>
<a name="admin_picture_thumb_advanced_userpics_dir_end"></a>
<a name="admin_picture_thumb_advanced_intermediate_prefix"></a>
<h4>The prefix for intermediate pictures</h4>
<p>This prefix is added to the archivo name of created pictures.</p>
<p>These setting mustn't be changed if you already have archivos in
your base de datos. If you do, all reference to your existing archivos
will become invalid.</p>
<a name="admin_picture_thumb_advanced_intermediate_prefix_end"></a>
<a name="admin_picture_thumb_advanced_thumbs_prefix"></a>
<h4>The prefix for thumbnails</h4>
<p>This prefix is added to the archivo name of created intermediate thumbnails.</p>
<p>These setting mustn't be changed if you already have archivos in
your base de datos. If you do, all reference to your existing archivos
will become invalid.</p>
<a name="admin_picture_thumb_advanced_thumbs_prefix_end"></a>
<a name="admin_picture_thumb_advanced_chmod_directorio"></a>
<h4>Default mode for directories</h4>
<p>If, and only if, during the archivo upload or batch add process, the
installer complains about the directorio not having the right
permissions, try setting this to <strong>0777</strong> . Failure to do
so may prevent you from being able to delete directories created by the
script with your FTP client should you ever decide it necessary to
uninstall the Coppermine script.</p>
<p><span class="important">Note</span>: setting this option doesn't
CHMOD the archivos or directorios that are being uploaded. Instead, the
setting is used when Coppermine, itself, creates <strong>new</strong>
directorios for user uploads (within the userpics directorio). If you
experienced problems during the initial Coppermine setup related to
permissions, this option is <strong>not</strong> what you have been looking for nor should it be changed ( for more information regarding CHMOD, see the <a href="http://www.f64foto.com.ar/CPG/faq.htm">FAQ.htm</a> document located in the DOCS directorio of this installation package ).</p>
<a name="admin_picture_thumb_advanced_chmod_directorio_end"></a>
<a name="admin_picture_thumb_advanced_chmod_archivos"></a>
<h4>Default mode for archivos</h4>
<p>If, and only if, during the archivo upload or batch add process, the
installer complains about the directorio not having the right
permissions, try setting this to <strong>0666</strong>.</p>
<p><span class="important">Note</span>: setting this option doesn't
CHMOD the archivos or directorios that are being uploaded. Instead, the
setting is used when Coppermine, itself, creates <strong>new</strong>
directorios for user uploads (within the userpics directorio). If you
experienced problems during the initial Coppermine setup related to
permissions, this option is <strong>not</strong> what you have been looking for nor should it be changed ( for more information regarding CHMOD, see the <a href="http://www.f64foto.com.ar/CPG/faq.htm">FAQ.htm</a> document located in the DOCS directorio of this installation package ).</p>
<a name="admin_picture_thumb_advanced_chmod_archivos_end"></a>
<a name="admin_picture_thumb_advanced_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_user"></a>
<h3>4.12.10 User settings</h3>
<a name="admin_allow_registration"></a>
<h4>Allow new user registrations</h4>
<p>Defines whether new users can self-register or not. If you set this
to NO, only the admin can create new users and the "register" enlace
won't be displayed in the navigation.</p>
<a name="admin_allow_unlogged_access"></a>
<h4>Allow unlogged users (guest or anonymous) access</h4>
<p>When set to "No", unlogged users (i.e. guests or anonymous users)
can not access anything in your gallery except the login screen (and
the registration screen, if you allow registrations). Completely
disabling anonymous access will probably decrease your site's
popularity. Use this option only if you need your gallery to be
absolutely private. The recommended setting is to leave anonymous
access enabled and use the more specific permissions by groups and
albumes settings instead.</p>
<a name="admin_allow_unlogged_access_end"></a>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_allow_registration_end"></a>
<a name="admin_registration_verify"></a>
<h4>User registration requires email verification</h4>
<p>If set to YES an email will be sent to the user that will contain a
code to activate his account. If set to NO, user accounts become
immediately active.</p>
<a name="admin_registration_verify_end"></a>
<a name="admin_registration_notify"></a>
<h4>Notify admin of user registration by email</h4>
<p>If set to YES an email will be sent to the gallery admin when a new user registers.</p>
<a name="admin_registration_notify_end"></a>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_activation"></a><h4>Admin Activation</h4>
<p>Enable admin activation. When set to yes, a gallery administrator
must first activate the new registration before the user can log-in and
take advantage of any registered user privileges.</p>
<p>By default, it is set to no, so users would activate their own accounts upon registering.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_activation_end"></a>
<a name="admin_allow_duplicate_emails_addr"></a>
<h4>Allow two users to have the same email address</h4>
<p>Allow or prevent two users from registering with the same email
address. Recommended setting is NO. As most internet users today have
more than one email address, this option is being considered as
deprecated and will possibly be removed in future versi�ns of
Coppermine.</p>
<a name="admin_allow_duplicate_emails_addr_end"></a>
<a name="admin_approval_notify"></a>
<h4>Notify admin of user upload awaiting approval</h4>
<p>When enabled, the gallery admin receives an email notification of
all pics that await for his/her approval (depends on the approval
settings in "<a href="#group_cp">groups</a>"). The email is sent to the address specified in "<a href="#admin_general">General settings</a>".</p><p>This option is only recommended for websites with low or medium traffic (where users only upload every now and then).</p>
<a name="admin_approval_notify_end"></a>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_user_memberlist"></a>
<h4>Allow logged in users to view memberlist</h4>
<p>When enabled, an additional menu item "Memberlist" is displayed in
the Coppermine main menu if a user is logged in, to let him see a list
of all users, with stats on their last visits, uploads and quota usage.</p><p>This is a new feature since cpg1.3.0 (user contribution by <a href="#contributors">Jason</a>) - it's available as <a href="http://sourceforge.net/project/showarchivos.php?group_id=89658&package_id=98542">mod</a> (not in the regular Coppermine package) for older versi�ns than cpg1.3.0.</p>
<a name="admin_user_memberlist_end"></a>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_user_allow_email_change"></a><h4>Allow users to change their email address in proarchivo</h4>
<p>This option impacts the user's profile page, it determines whether or not the user can change his/her own email address.<br>Use
this option wisely, as the old email address of a user is not preserved
after a change: if you allow users to change their email address,
abusers may change it to a non-existing email address (e.g. after
uploading some pics that go against your gallery's rules) - you would
have no chance of tracking this user.</p>
<p>This option only applies if you use Coppermine as a standalone
application; if you run Coppermine integrated with a bbs, this option
will be deferred to the user proarchivo from your bbs to manage each
user's proarchivo.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_user_allow_email_change_end"></a>
<a name="admin_user_editpics_public_start"></a><h4>Allow users to retain control over their pics in public galleries</h4>
<p>When enabled, both the admin and the uploading user can edit and
delete archivos that were uploaded to a public gallery. Of course the
user must have permissions to upload to the public gallery in the first
place (see the <a href="#group_cp">groups control panel</a>) before this option will have any effect.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_user_editpics_public_end"></a>
<a name="admin_user_login_start"></a>
<a name="admin_user_login_threshold_start"></a>
<h4>Number of failed login attempts until temporary ban (to avoid brute force attacks)</h4>
<p>To make brute force attacks (where a hostile script tries to log
into Coppermine as admin by running through all possible combinations
of username and password automatically) less effective Coppermine
temporarily bans the IP address of a possible attacker after a certain
amount of failed logins. This way, the brute force attack would need
way too long to try all possible combinations.</p>
<p>With this setting you specify the maximum number of failed log-in
attempts before the IP address of the user is temporarily banned.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_user_login_threshold_end"></a>
<a name="admin_user_login_expiry_start"></a>
<h4>Duration of a temporary ban after failed logins</h4>
<p>This value specifies the duration of the temporary ban (in minutes) after the number of failed log-in attempts specified with <a href="#admin_user_login_threshold_start">Number of failed login attempts until temporary ban</a>.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_user_login_expiry_end"></a>
<a name="admin_user_login_end"></a>
<a name="admin_user_enable_report"></a><h4>Enable reports</h4>
<p>Enable reports. When set to "yes," this feature will allow users to report on uploaded archivos or comments to the site admin.</p>
<p>This setting is dependant on e-cards being enabled. Only users who
have permission to send e-cards in the 'groups' settings are able to
send reports. The report icon is hidden from those not allowed to do so.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_user_enable_report_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_custom"></a>
<h4>4.12.11 Custom fields for user proarchivo (leave blank if unused). Use Proarchivo 6 for long entries, such as biographies </h4>
<p>These fields are displayed within the "user proarchivo" area. They
will appear only if you assign a name to the field. As instructed in
the heading, use field 6 for long entries, such as biographies, or if
you want to include the use of bb code.</p>
<p>You can also use field 6 for avatars. To show an avatar in the
proarchivo, it should be entered in bbcode, for example to show
'avatar.gif', which is located in your images directorio, use the code
[img]http://www.yoursite.com/images/avatar.gif[/img]</p>
<a name="admin_custom_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_custom_image"></a>
<h4>4.12.12 Custom fields for image description (leave blank if unused)</h4>
<p>These fields are displayed within the "archivo information" area. They will appear only if you give them a name.</p>
<a name="admin_custom_image_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_cookie"></a>
<h4>4.12.13 Cookie settings</h4>
<a name="admin_cookie_name"></a>
<h4>Name of the cookie used by Coppermine</h4>
<p>Default value is "cpg140". Even if you have multiple instances of
the script running on the same servidor you can keep the default value.</p><p><span class="important">When using bbs integration, aseg�rese it <strong>differs</strong> from the bbs's cookie name</span></p>
<a name="admin_cookie_name_end"></a>
<a name="admin_cookie_path"></a>
<h4>Path of the cookie used by the script</h4>
<p>Default value is "/". Don't change this unless you know what you are doing. This may prevent you from logging in.</p>
<p>If you have broken your gallery by modifying this value, use
phpMyAdmin to edit the xxxx_config table in your base de datos and
restore the default value. </p>
<p>When using bbs integration into Coppermine, aseg�rese to use <strong>different</strong>
cookie names for Coppermine and your bbs! The paths in both
applications have to be set so Coppermine is able to read both. Usually
the default value "<tt class="code">/</tt>" should be set as path both for Coppermine install and the BBS app you bridge with.</p>
<a name="admin_cookie_path_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_email"></a>
<h4>4.12.14 Email settings</h4>
<p>Usually nothing has to be changed here; leave all fields blank when
not sure. Only if you run into problems (e.g. if ecards, registration
info or notifications don't get sent) you should change these settings.
Coppermine itself doesn't come with an engine to send mails, it relies
on a webservidor being able to do so (using the built-in mechanisms of
PHP). If you're not sure what to enter, ask your proveedor de hosting
for support.</p>
<h4>SMTP Host</h4>
<p>The hostname of the <acronym title="Simple Mail Transfer Protocol">SMTP</acronym> servidor<br>
If you leave this blank, sendmail (or a surrogate) will be used to send
emails from your servidor. Sendmail exists on most Unix/Linux
webservidors. If you specify a SMTP hostname, Coppermine will try to
send emails using SMTP (this usually is needed on Windows webservidors).</p>
<p class="small">[cpg1.4.0 or better required]</p>
<h4>SMTP Username</h4>
<p>The username needed to authenticate on the SMTP servidor (this is <strong>not</strong> your Coppermine admin username).</p>
<p class="small">[cpg1.4.0 or better required]</p>
<h4>SMTP Password</h4>
<p>The password that goes with above mentioned username (<strong>not</strong> identical to your Coppermine admin password).</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_email_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_logging"></a>
<h3>4.12.15 Logging & statistics</h3>
<p>Like all logs (that record data that would get dropped if logging
was disabled), the logging features of Coppermine will have a slight
performance impact as well as an impact on webspace and base de datos
usage. You should make up your mind if you actually will need the logs
before enabling the feature. A log is only helpful if the admin
actually looks into it.</p>
<a name="admin_logging_log_mode"></a><h4>Logging mode</h4>
<p>Set, what kind of logging you want to enable. This feature records
all changes that are done in Coppermine's base de datos, which is
especially helpful if you're trying to debug or if there are various
admins on a gallery.<br>
All log archivos are written in english</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="admin_logging_log_mode_end"></a>
<a name="admin_general_log_ecards"></a><h4>Log ecards</h4>
<p>When enabled, all ecards that are being sent are as well written
into the base de datos, where the Coppermine admin can view them.
Before switching this option on, aseg�rese that logging is legal in
your country. It is also advisable to notify your users that all ecards
are being logged (preferrably on the registration screen).</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_general_log_ecards_end"></a>
<a name="admin_logging_votedetails"></a><h4>Keep detailed vote statistics</h4>
<p>
Enabling this option records:</p>
<ol>
<li>Each vote separately</li>
<li>IP Address</li>
<li>Referer</li>
<li>Browser</li>
<li>Operating System</li>
</ol>
<p>of the voter.</p>
<p>As
the statistics are being kept per archivo, the enlace to the stats can
be accessed on the individual archivo's page (displayimage.php) by
clicking the enlace in the archivo info section to open the stats
pop-up.</p>
<p>
<span class="important">Note: The total votes may not match if you enable details and do not reset the earlier votes.</span></p>
<a name="admin_logging_votedetails_end"></a>
<a name="admin_logging_hitdetails"></a><h4>Keep detailed hit statistics</h4>
<p>
Enabling this option records:</p>
<ol>
<li>Each vote separately</li>
<li>IP Address</li>
<li>Search Keyword, if the referer is Google, Yahoo! or Lycos search engines</li>
<li>Referer</li>
<li>Browser</li>
<li>Operating System</li>
</ol>
<p>of the visitor.</p>
<p>As
the statistics are being kept per archivo, the enlace to the stats can
be accessed on the individual archivo's page (displayimage.php) by
clicking the enlace in the archivo info section to open the stats
pop-up.</p>
<p>
<span class="important">Note: The total hits may not match if you enable details and do not reset the earlier hits.</span></p>
<a name="admin_logging_hitdetails_end"></a>
<a name="admin_logging_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="admin_misc"></a>
<h3>4.12.16 Miscellaneous settings</h3>
<a name="debug_mode"></a><h4>Enable debug mode</h4>
<p>CPG will show error messages which are normally suppressed. This is
helpful in troubleshooting problems with your gallery or when asking
for help on the <a href="http://coppermine.sourceforge.net/board/">CPG Support Forums</a>. Turn this feature off if you don't experience problems.</p>
<p>Turn it on (option "Everyone") if you are requesting help on the <a href="http://coppermine.sourceforge.net/board/">Coppermine support board</a>,
so the supporters can have a look at the debug output as well. Choose
the option "Admin only" when troubleshooting on your own - debug output
will be only visible when you're logged in as admin, regular users or
guests won't see the debug output.</p>
<a name="admin_misc_debug_notices"></a><h4>Display notices in debug mode</h4>
<p>May be helpful to troubleshoot problems with your Coppermine install
- only recommended if you know a little PHP and you can understand the
additional error messages this option shows. This option only applies
if debug mode is enabled.</p>
<a name="admin_misc_debug_notices_end"></a>
<a name="debug_mode_end"></a>
<a name="admin_general_offline"></a><h4>Gallery is offline</h4>
<p>If you have to do maintenance work on your gallery, switch it to
offline mode. Only members of the admin group will be able to log in,
all other users will only see "Gallery is offline". Remember to switch
this option off once your maintenance work is done.</p>
<p class="small">[cpg1.3.0 or better required]</p>
<a name="admin_general_offline_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="exif"></a>
<h2>4.13 EXIF data</h2>
<p>The "Exchangeable image archivo" format (Exif) is a specification
for the image archivo format used by digital cameras with the addition
of specific metadata tags. The meta data are written by the camera and
can be post-processed using certain desktop applications. Coppermine is
capable of displaying some of the EXIF data within the pic info
section, like date and time information, camera settings, location
information, descriptions and copyright information.<br>
<img src="pics/es_exif_data_cpg1.gif" alt="Exif data in pic info section" border="0" height="341" width="717"></p>
<a name="exif_manager"></a>
<h3>4.13.1 EXIF manager</h3>
<p>CPG1.4.x (or better) comes with an EXIF manager that let's the
Coppermine admin decide what EXIF data should be displayed within
Coppermine. Please note: if the exif data don't exist within a
particular image, Coppermine will of course not be able to display
them. Coppermine is not an editor for exif data - it just displays the
exif data that exists in your pics.<br>
To access the exif manager, go to Coppermine's config and click within the section <a href="#admin_picture_thumb_advanced">Archivos and thumbnails advanced settings</a> at "Manage exif display" next to the line "<a href="#admin_picture_thumb_advanced_exif">Read EXIF data in JPEG archivos</a>".
Alternatively, you can directly enter
http://yoursite.tld/your_Coppermine_directorio/exifmgr.php into your
browser's address bar.</p>
<p>Tick the checkboxes in the exif manager that you want to show up in
Coppermine's pic info section (if the image archivo actually holds this
particular set of information).</p>
<p><img src="pics/es_exifmanager_cpg1.gif" alt="" align="right" border="0" height="549" width="950"></p>
<br clear="all">
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="plugin_start"></a>
<a name="plugin"></a>
<h2>4.14 Plugins</h2>
<p>Included in your Coppermine setup are two basic plugins:</p>
<ul>
<li>Sample plugin: meant for plugin-writers as an example only</li>
<li>SEF_URLS plugin: enables "Search-engine-friendly URLs" - this is an experimental plugin and should be used with caution.</li>
</ul>
<p>You can find more plugins on the Coppermine Support Forum, both from Coppermine developers and from user contributions.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="plugin_definition"></a>
<h3>4.14.1 What is a plugin?</h3>
<p>Starting from cpg1.4.0, Coppermine comes with a plugin <acronym title="Application Programming Interface">API</acronym>
that enables plugin authors to modify Coppermine features without
hacking the core code, making upgrading easier, as modifications don't
have to be re-applied every time you upgrade your Coppermine versi�n.
It's recommended to use plugins instead of code modifications that
require hacking the core code.</p>
<a name="plugin_definition_end"></a>
<a name="plugin_api"></a>
<h3>4.14.2 The Plugin API</h3>
<p>The plugin API consists of several "hooks" all over the core code of
Coppermine that allows plugin authors to interact with Coppermine
functions, overriding or adding features. There are limitations to what
can be done using a plugin, as the number of hooks is limited. As a
result, not every change of Coppermine behaviour that could be
accomplished by hacking the core code is possible to achieve using the
plugin API. However, using a plugin is more elegant and usually much
easier to install and get running (at least for the end user) than a
crude core code hack. Installing and configuring a plugin doesn't
require the Coppermine admin to mess with the source code - you simply
upload the plugin, install it, configure it and you're done. If the
plugin has been coded as suggested and is mature enough, it should come
with a configuration screen that makes editing source code irrelevant.<br>
Unfortunately, there is no API documentation available yet.</p>
<a name="plugin_api_end"></a>
<a name="plugin_manager"></a>
<h3>4.14.3 The Plugin Manager</h3>
<p>The plugin manager is the central place from where you upload,
install, configure and remove plugins. It can be acceessed in two ways:</p>
<ul>
<li><strong>Using Coppermine's navigation:</strong><br> Log in
as admin, go to Coppermine's config, expand the "General settings"
section, on click "Manage plugins" next to "Enable plugins" (aseg�rese
that you have set "Enable plugins" to "Yes") if you plan using plugins.</li>
<li><strong>Directly accessing the plugin manager</strong><br>
aseg�rese that you are logged in as admin, then directly enter the
plugin manager's url in the address bar of your browser, e.g.
http://yoursite.tld/your_Coppermine_directorio/pluginmgr.php</li>
</ul>
<p>The plugin manager organizes the plugins you have in your Coppermine
directorio. It is important to understand the difference between
uploading plugins and installing plugins. When you copy a plugin to the
Coppermine plugins directorio (using the Upload button on the plugin
manager or via FTP), you have merely uploaded the plugin archivos. The
plugin is not installed yet. When you install a plugin, Coppermine runs
the plugin's installation routine to configure and activate the plugin
so that it will be executed when people use your gallery. To clearly
show which plugins are running and which are not, the plugin manager is
separated into two sections (see screen capture below):</p>
<ul>
<li>the plugins that are installed and running (upper section)</li>
<li>the
plugins that exist within the plugins directorio of your servidor's
hard drive but have not been installed and therefore are not running in
your Coppermine gallery (lower section)</li>
</ul>
<p><img src="pics/plugin_manager.gif" alt="Coppermine Plugin Manager" border="0" height="234" width="716"></p>
<p>By default, Coppermine comes with some sample or code plugins (none
of them are enabled by default though), additional plugins can be found
on the corresponding section of Coppermine's forum.</p>
<a name="plugin_manager_upload"></a>
<h4>4.14.3.1 Uploading a plugin</h4>
<p>Unless you're going to code your own plugins, they usually come
packaged up already, compressed into a zip archivo. There are two
options how to upload a plugin:</p>
<ul>
<li>Method 1: <strong>Using the upload interface on Coppermine's plugin manager page</strong><br>
<ul>
<li>Download the plugin you need from the internet (usually the <a href="http://coppermine-gallery.net/">Coppermine p�gina</a>) to your local hard drive</li>
<li>Click the "browse" button on the plugin manager page</li>
<li>Navigate to the plugin zip archivo you just have downloaded to your local PC's hard drive</li>
<li>Click "upload"</li>
</ul>
This is the more elegant and easier method - you just use the upload
control on the plugin manager page and the zip archivo you uploaded
gets extracted from the archive and stored on the servidor within the
proper directorio. There are two pre-requisites though: <ul>
<li>PHP running on your webservidor needs zip support - not all webservidor have zip support enabled.</li>
<li>the script needs write permissions within the plugins directorio.</li>
</ul>
If you fail to fullfil those two pre-requisites, this simple method
(upload interface) won't work for you (i.e. you will get error messages
when trying, or the plugin will even simply fail to work without an
error message at all). If this is the case for you, it's recommended
not to mess with servidor setup (unless you're an expert and the
servidor is yours to administer), but just to use the second upload
method described below.</li>
<li>Method 2: <strong>Uploading the unzipped plugin archivos using your FTP app</strong><br>
<ul>
<li>Download the plugin you need from the internet to your local hard drive (same step as above)</li>
<li>Unpack the zip archivo into a directorio on your hard drive (preserving the directorio structure of the plugin)</li>
<li>Use
your FTP app to upload the unpacked plugin archivos into the plugin
directorio of your Coppermine install on your servidor, preserving the
structure of the zip archive. For example: if the plugin contained the
directorio "foobar", which held the actual plugin archivos, you upload
the whole directorio "foobar" and all of its contents into the plugins
directorio. The resulting directorio structure on your servidor should
be something like <tt class="code">/your_Coppermine_directorio/plugins/foobar/</tt></li>
</ul>
</li>
</ul>
<p>After uploading the archivos (you may need to refresh the plugin
manager page), the plugin you just uploaded should show in the list
"Plugins Not Installed". If it does, you can continue to the next step
and <a href="#plugin_manager_install">install</a> the plugin.</p>
<a name="plugin_manager_upload_end"></a>
<a name="plugin_manager_install"></a>
<h4>4.14.3.2 Installing a plugin</h4>
<p>Installing a plugin is fairly straightforward - just click on the <img src="../images/info.gif" alt="" border="0" height="16" width="16">-icon
next to the plugin. The install will enable the plugin to be executed
when Coppermine is being run (depending on the plugin's purpose). Some
plugins come with a configuration screen that will be executed right
after the install - if this is the case, configure it accordingly.</p>
<a name="plugin_manager_install_end"></a>
<a name="plugin_manager_configuration"></a>
<h4>4.14.3.3 Plugin Configuration</h4>
<p>Some plugins may need to be configured during install, others may
have a separate p�gina de configuraci�n that can be accessed at any
time. This depends on how the plugin author wrote the plugin, so we
can't give any recommendations within this documentation. Some plugins
may even need to be configured before actually being uploaded
(especially plugins in alpha or beta stage - these may come without a
browser-driven p�gina de configuraci�n and require you to modify the
plugin's code to configure the plugin). If unsure, take a look in the
unzipped plugin archive on your hard-drive - usually, plugins that
require you to edit or configure anything come with a README archivo
that tells you how to do so.</p>
<a name="plugin_manager_configuration_end"></a>
<a name="plugin_manager_uninstall"></a>
<h4>4.14.3.4 Uninstalling a plugin</h4>
<p>Executing a plugin might be consuming resources or not work as
expected, so you might want to uninstall a plugin at some time (maybe
because you just tried it out and it doesn't work as expected for you).
It's recommended not to just delete the plugin's subdirectorio using
your FTP app (because the plugin might have applied base de datos
changes that need to be undone). Instead, you should go to the plugin
manager and click on the <img src="../images/delete.gif" alt="" border="0" height="16" width="16">-icon
next to an active (installed) plugin. The plugin then should get
uninstalled and turn up in the list "Plugins Not installed". It's safe
to leave the sources of an unneeded plugin on the servidor, so there
should be no need to delete the plugin right after uninstall, however
you may as well delete it, especially if you're short on webspace and
the plugin eats up a lot of space.</p>
<p>To finally delete an inactive plugin from your servidor's plugin directorio, click the <img src="../images/delete.gif" alt="" border="0" height="16" width="16">-icon
next to a plugin that is in the list "Plugins Not installed". If the
script fails to delete a plugin this way (because of lacking
permissions to do so on archivo/directorio level), you can use your FTP
app to delete the particular plugin's sub-directorio within
Coppermine's "plugins" directorio (deleting manually). As with all
delete operations, you should make a local backup before deleting if
you're not absolutely sure what you're doing.</p>
<a name="plugin_manager_uninstall_end"></a>
<a name="plugin_manager_end"></a>
<a name="plugin_writing"></a>
<h3>4.14.4 Writing plugins</h3>
<p>As suggested above, there's no documentation available yet for
plugin authors, so the only method to learn how plugins work is by
looking at the source code. Examine the code of the plugins that come
with Coppermine, or take a look at some that are available for download
from the plugin contributions sub-board on the Coppermine web p�gina.</p>
<p>If you accomplished writing a plugin, we ask you to share it with
the Coppermine community by posting it on the appropriate board (this
is of course not mandatory, but we'd appreciate to see your
contribution). We would welcome a user-contributed API documentation or
a list of hooks as well, or other related documentation.</p>
<a name="plugin_writing_end"></a>
<a name="plugin_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="integrating"></a>
<h1>5. Integrating the script with your bulletin board</h1>
<a name="integrating_bridge_start"></a>
<h2>5.1 Available bridge archivos</h2>
<p>Coppermine can be integrated with the following bulletin boards (eg. Coppermine
and your bulletin board will share the same user base de datos).</p>
<ul>
<li>Invision Power Board</li>
<li>Mambo</li>
<li>MyBB</li>
<li>Phorum</li>
<li>phpBB 2</li>
<li>PunBB</li>
<li>SMF</li>
<li>vBulletin</li>
<li>XMB</li>
<li>Xoops2</li>
</ul>
<a name="integrating_bridge_end"></a>
<a name="integrating_prerequisites_start"></a>
<h2>5.2 Pre-requistes</h2>
<a name="integrating_cookie_start"></a>
<h3>5.2.1 Authentication by cookie</h3>
<p>The login integration uses your bulletin board cookies, therefore it
won't work if your board cookies are not visible by Coppermine. So
unless you are an expert, keep things simple and install Coppermine and
your bulletin board on the same domain. Examples :</p>
<table class="border1" border="0" cellpadding="5" cellspacing="5">
<tbody><tr>
<td>Esto <strong>s�</strong> funcionar�:</td>
<td>Esto <strong class="important">no</strong> funcionar�:</td>
</tr>
<tr>
<td class="code">Foro: http://sudominio.com/foro/<br>
Coppermine: http://sudominio.com/galer�a/</td>
<td class="code">Foro: http://foro.sudominio.com/<br>
Coppermine: http://galer�a.sudominio.com/</td>
</tr>
</tbody></table>
<p>The cookie path in the forum's configuration should be set to '/' where this option is available.</p>
<p><span class="important">Important</span>: the cookie names of your bbs and Coppermine must <strong>not</strong> be the same - they <strong>must</strong> differ!</p>
<a name="integrating_cookie_end"></a>
<a name="integrating_standalone_start"></a>
<h3>5.2.2 Standalone versi�n first</h3>
<p>To avoid confusion, aseg�rese to set up both Coppermine and your bbs
as standalone first. aseg�rese they both run correctly without
integration. Test all features of Coppermine (like upload, registration
etc.) when Coppermine is installed, before you even start integration.</p>
<a name="integrating_standalone_end"></a>
<a name="integrating_users_start"></a>
<h3>5.2.3 Coppermine users, groups and pics uploaded by users are lost when integrating</h3>
<p><span class="important">Warning:</span> If you already have users
and custom groups in your Coppermine base de datos when you enable bbs
integration, be aware that they will be lost. If your Coppermine users
have already created private albumes and uploaded pics to them, they
will be lost as well!</p>
<a name="integrating_users_end"></a>
<a name="integrating_backup_start"></a>
<h3>5.2.4 Backup</h3>
<p><span class="important">Backup</span>: it is very advisable to
backup both your Coppermine base de datos and your archivos before
enabling bbs integration, so you can safely go back if the integration
fails.</p>
<p>In fact you're encouraged to backup your base de datos on a regular base, and especially before applying code changes.</p>
<a name="integrating_backup_end"></a>
<a name="integrating_prerequisites_end"></a>
<a name="integrating_steps_start"></a>
<h2>5.3 Integration steps</h2>
<p>From cpg1.4.x on you can use the <a href="#bridge_manager_start">Bridge Manager</a> that will provide a wizard-like interface to enable/disable bridging.</p>
<a name="bridge_manager_start"></a>
<h3>5.3.1 Using the bridge manager</h3>
<p>The bridge manager is a new feature in cpg1.4, it is not available
in older versi�ns. Instead of manually editing Coppermine code
archivos, you can enable/disable bridging in your browser, using a
wizard-like user interface. To start the bridge manager, log in as
admin, choose "Admin Tools" from the navigation and the "bridge manager"</p>
<p><img src="pics/es_bridge_01_start.gif" alt="" align="right" border="0" height="95" width="670">If
you run the bridge manager for the first time, there will only be one
button that let's you actually start the wizard (if you return to the
bridge manager later, you will also find a switch to enable/disable
bridging) click it.</p>
<p class="important">Note: with each step in the wizard, some
information is being written to the Coppermine base de datos. Unlike
other wizards (mostly on your local machine), the bridge manager
doesn't have a ""cancel"-button! Once you have enabled bridging and
everything is working fine, you shouldn't change any values just out of
curiosity, as they will get written to the base de datos, which might
result in a bridging that used to work not working any more after
"playing" with it.<br clear="all"></p>
<p><img src="pics/es_bridge_02_app.gif" alt="" align="right" border="0" height="487" width="745">In
the first actual step of the wizard "choose application to bridge
Coppermine with", you have to choose the application you actually want
to Coppermine with. Note that you <strong>must</strong> have this
application already installed on your webservidor, it has to be
properly configured and must be up-and-running. Don't use the bridge
manager yet if you only <em>plan</em> to integrate Coppermine with another application later.</p>
<p>If you have a custom-made bridge archivo that is not available in
the wizard, choose the radio button in front of the text field and
enter the name of your bridge archivo there, without the extension
".inc.php" (the bridge archivo must reside in the Coppermine
sub-directorio "bridge").<br>
Click "next"</p>
<p>The next steps depend on the application you have chosen to bridge with: some applications need <acronym title="Uniform Resource Locator">URL</acronym>s
to be entered, or paths. Some need mySQL table information or cookie
data to be entered, others don't. The point of the wizard is that it
will only "ask" you the relevant settings for your application - if one
or more items of the following description doesn't turn up for your
application, there's no need to worry - just keep filling in the
mandatory information and then hit "next". However, you have to
understand that Coppermine can proof-check only some of your input -
some input goes unvalidated.</p>
<p>If a reset button is being displayed next to an input field, the field value doesn't have
the default value. It can be perfectly OK to have a non-default value
in a field, however you should keep in mind that if you have "played"
with the bridge manager before, previous settings might exist in a
field that are not correct - do not light-heartedly skip a step without
paying attention to it. Use the reset button to revert to the default
value (not necessarily "quor" default value though).<br clear="all"></p>
<a name="bridge_manager_app_start"></a>
<h4>5.3.1.1 choose application to bridge Coppermine with</h4>
<ul>
<ul>
<li>Invision Power Board</li>
<li>Mambo</li>
<li>MyBB</li>
<li>phpBB 2</li>
<li>Phorum</li>
<li>PunBB</li>
<li>SMF</li>
<li>vBulletin</li>
<li>XMB</li>
<li>Xoops2</li>
</ul>
</ul>
<a name="bridge_manager_app_end"></a>
<a name="bridge_manager_path_start"></a>
<h4>5.3.1.2 path(s) used by your BBS app</h4>
<ul>
<li><strong>Forum URL</strong><br>
Full URL of your BBS app (including the leading http:// bit, e.g. http://www.yourdomain.tld/forum/)</li>
<li><strong>Relative forum path</strong><br>
Relative path to your BBS app from the webroot (Example: if your BBS is
at http://www.yourdomain.tld/forum/, enter "/forum/" into this field)</li>
<li><strong>Relative path to your BBS's config archivo</strong><br>
Relative path to your BBS, seen from your Coppermine directorio (e.g.
"../forum/" if your BBS is at http://www.yourdomain.tld/forum/ and
Coppermine at http://www.yourdomain.tld/gallery/)</li>
</ul>
<a name="bridge_manager_path_end"></a>
<a name="bridge_manager_specific_start"></a>
<h4>5.3.1.3 BBS-specific settings</h4>
<ul>
<li><strong>Use post-based groups?</strong><br>
Should Coppermine import the special groups that exist in the forum ?
If you select no, then Coppermine will use the standard groups
(Administrator, Registered and Anonymous) which makes administration
easier and is recommended. You can change this setting later as well.</li>
</ul>
<a name="bridge_manager_specific_end"></a>
<a name="bridge_manager_enable_start"></a>
<h4>5.3.1.4 enable/disable BBS integration</h4>
<p>This is the last step of the bridge manager - it summarizes up the
settings you have made in previous steps - you can enable or disable
integration here. By default, integration is set to "disabled" after
the bridge manager has been run for the first time. You should only
enable integration if you're sure your BBS app is set up correctly.
Click the "Finish" button in any case to finally write to the base de
datos, even if you choose to keep the current settings (leaving
integration "disabled").</p>
<ul>
<li><strong>Enable integration/bridging with XXX</strong></li>
</ul>
<a name="bridge_manager_enable_end"></a>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="bridge_manager_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="bridge_manager_recover_start"></a>
<h3>5.3.2 Recover from failed bridging</h3>
<p>If you have provided improper settings using the bridge manager,
your integration might fail, resulting (in the worst case) in a
stituation where bridging is enabled, but you can not log in as admin
to switch it off again (e.g. if you provided improper cookie settings
that stops authentication from working). For this situation a recovery
setting was built into the bridge manager: if you are not logged in as
Coppermine admin (in fact: not logged in at all) and you access the URL
of your bridge manager
(http://yourdomain.tld/your_Coppermine_directorio/bridgemgr.php) by
entering it manually into the address bar of your browser, you are
prompted to enter your admin account details - use the admin account
you used to install Coppermine with in the first place (the standalone
admin account). This will not log you in, but switch integration off,
so you can fix improper bridging settings then. To avoid others trying
to guess your admin account details, there's a login treshold that
rises every time you enter wrong credentials, so enter your admin
account details with care.</p>
<p class="small">[cpg1.4.0 or better required]</p>
<a name="bridge_manager_recover_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="integrating_steps_sync_start"></a>
<h3>5.3.3 Synchronising the bbs groups with Coppermine's groups</h3>
<p>Login using the admin account of your board. Go to the gallery,
enter admin mode and click on the "Groups" button. This will
synchronize Coppermine groups with those of your board. The permission
you will see for each group will be completely messy, so take some time
to set them properly.</p>
<p>Each time you add or delete a group in your board you will need to
do the operation above in order to keep the synchronisation of the
groups.</p>
<p>When you will try to login / logout or manage users from Coppermine,
you will be redirected to the corresponding p�gina of your bulletin
board. Once the login or logout is performed you won't be redirected
automatically to the gallery because your board does not have any
function for that. It's up to you to add a enlace on your board to get
you back to the gallery.</p>
<p class="important">It's mandatory that you (as admin) go to the
p�gina de grupos directly after bridging or whenever you change
anything in your bridging configuration or if you change anything in
your groups settings on your bbs, as you need to trigger the re-sync.</p>
<a name="integrating_steps_sync_end"></a>
<a name="integrating_steps_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="integrating_support_start"></a>
<h2>5.4 Bridging support</h2>
<p>With the explanations given above you should be able to bridge your
(BBS) application with Coppermine. However, if things don't work as
expected, you're welcome to look for help using the <a href="http://coppermine-gallery.net/forum/">Coppermine support board</a>. When asking for support, please keep in mind that the supporters will need some information to enable them to help you:</p>
<ul>
<li>Search the board before posting - maybe somebody had similar issues to yours that have been solved already</li>
<li>Post
on the board that deals with your versi�n - bridging mechanisms have
changed from versi�n to versi�n, that's why it's important to post on
the board that actually corresponds to your Coppermine versi�n</li>
<li>Don't hijack threads - when looking for bridging support, start your own thread</li>
<li>Read the sticky threads before posting</li>
<li>aseg�rese
you are using the latest versi�ns of the bridging archivos, they are
kept up to date between formal Coppermine releases. Download the
relevant archivos from the <a href="http://svn.sourceforge.net/viewvc/Coppermine/trunk/stable/">SVN</a>.
Update udb_base.inc.php and the archivo that corresponds to the bridge
you are using and upload them into your bridge directorio, overwriting
the old ones. Of course you should aseg�rese to use the most recent
stable Coppermine release in the first place.</li>
<li>When
requesting bridge support, please post a enlace to your site, a test
user account, and what you have set in the bridge manager.<br>aseg�rese
that the test user account doesn't have admin privileges. When posting
parts of your bridge archivo, aseg�rese to replace passwords with
asterisks.<br> <br>This is how your posting should look like (with actual URLs instead of the dummy URLs given here as an example):<br>
<pre class="code">I have the following issue when trying to bridge Coppermine and XXX:
[error message here]
Coppermine install: http://mysite.tld/my_Coppermine_directorio/
Forum install: http://mysite.tld/my_forum_directorio/
Coppermine version: cpg1.4.x
Forum version: SuperDuper BBS app v0.8.15
Test user account: some_testuser_name / the_password_for_the_test_user_account
BridgeManager settings:
Forum URL: http://mysite.tld/test/foo_bar
Relative path to your BBS's config archivo: ../bla/
Use post-based groups?: 0 </pre></li>
</ul>
<a name="integrating_support_start"></a>
<a name="integrating_end"></a>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="translating"></a>
<h1>6. Translating Coppermine into other languages</h1>
<p>Coppermine has a separate language archivo that make the translation
of the script much more easy. The language archivos are stored in the <strong>lang </strong>directorio.</p>
<p>If you select an utf-8 language archivo as the default one, then the
script will be able to automatically select a language archivo based on
the visitor browser configuration. For instance if the default language
archivo is danish (utf-8) and an english visitor accesses your gallery,
the english language archivo will be used by the script.</p>
<p> If you have translated Coppermine into a language not already supported, please read the <a href="http://www.f64foto.com.ar/CPG/translation.htm">translator's guide</a> and visit the <a href="http://coppermine.sourceforge.net/board/index.php?topic=4623.0">Coppermine Web Site</a> and follow the instructions for submitting your language.</p>
<p></p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="known_issues"></a>
<h1>7. Known Issues</h1>
<p>The following slight quirks and tiny issues are known and will hopefully be fixed in future releases.</p>
<ul>
<li>The <a href="http://coppermine.sourceforge.net/board/index.php?topic=1866.0">arrows used for navigation</a> from one pic to the other display in the wrong order for rtl-languages</li>
<li>Keyword list returns incorrect result for asian characters</li>
<li>Browser bug: IE displays 100%-width values incorrectly</li>
<li>New batch-add interface doesn't work on all servidor setups. Users who have issues with it should use the classic interface instead.</li>
<li>Missing Query in debug output: the value for $CONFIG['debug_mode'] is not yet set before the first query to the config table</li>
<li>Page tabs in user manager don't behave in the same way as other tabs</li>
<li>Resizing gif/png with transparent background doesn't preserve alpha info</li>
<li>Weird characters on mouseover tooltips in other browsers than IE</li>
<li>Wrong charset in emails sent from Coppermine</li>
<li>Language fallback not working for util.php and faq.php</li>
<li>Hardcoded charset in xp_publisher.php</li>
<li>Thumbnail sizes over 120px causes edit fields to run over its edge</li>
<li>No �lbum thumbnails for albumes that contain only pics enlaceed by keyword</li>
<li>Possible stability issues with PHP5 and plugins</li>
<li>Crop/rotate doesn't work with GD1</li>
<li>Rotate causing distorted image for large archivos</li>
<li>Search Engine Friendly URLs plugin is not working flawlessly, it's still experimental</li>
<li><tt class="code"><object><param></param></object></tt> construct for multimedia archivos doesn't validate but is needed for backwards compatibility</li>
<li>Nuke check in installer needs improvement</li>
<li>EXIF and IPTC information are lost when rotating</li>
<li>Banned group doesn't work as expected</li>
<li>Album created using XP publisher despite upload failure</li>
<li>Hebrew translation still incomplete</li>
<li>No category thumbnail for user galleries and categories that don't contain albumes with pics in it, but only sub-categories</li>
<li>SEF plugin breaks custom sort order</li>
<li>Editpics and editOnePic allow users to move files from a personal gallery to a public album without approval where approval is required</li>
<li>Editpics and editOnePic allow users to move files from a personal gallery to a public album without notice where they might not be able to edit the file</li>
</ul>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="credits"></a>
<h1>8. Credits</h1>
<a name="developers"></a>
<h2>8.1 Coppermine team</h2>
<!-- Team Member sort order: GROUP BY 'status' ORDER BY 'position' IN THIS ORDER (Proj Mgr,Lead dev,Developer,Supporter,tester,other), 'username' ASC -->
<table border="0" cellpadding="4" cellspacing="6">
<tbody><tr>
<td><strong>Developer</strong></td>
<td><strong>Username</strong></td>
<td><strong>Role/Position</strong></td>
<td><strong>Status</strong></td>
</tr>
<tr>
<td>Joachim M�ller</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=2">gaugau</a></td>
<td>Project Manager</td>
<td>active</td>
</tr>
<tr>
<td>Dr Tarique Sani</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=4">tarique</a></td>
<td>Lead Developer</td>
<td>active</td>
</tr>
<tr>
<td>Abbas Ali</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=11737">abbas</a></td>
<td>Developer</td>
<td>active</td>
</tr>
<tr>
<td>Aditya Mooley</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=5957">Aditya</a></td>
<td>Developer</td>
<td>active</td>
</tr>
<tr>
<td>Donovan Bray</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=10059">donnoman</a></td>
<td>Developer</td>
<td>active</td>
</tr>
<tr>
<td>Tommy Atkinson</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=941">Nibbler</a></td>
<td>Developer</td>
<td>active</td>
</tr>
<tr>
<td>Dave Kazebeer</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=7">kegobeer</a></td>
<td>Supporter</td>
<td>active</td>
</tr>
<tr>
<td>Thomas Lange</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=14796">Stramm</a></td>
<td>Developer</td>
<td>active</td>
</tr>
<tr>
<td>Thu Tu</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=7792">TranzNDance</a></td>
<td>Supporter</td>
<td>active</td>
</tr>
<tr>
<td>Paul Van Rompay</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=23938">Paver</a></td>
<td>Developer</td>
<td>active</td>
</tr>
<tr>
<td>Amit Badkas</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=18262">Amit</a></td>
<td>Developer</td>
<td>active</td>
</tr>
<tr>
<td>Andreas Ellsel</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=898">Andi</a></td>
<td>Tester</td>
<td>active</td>
</tr>
<tr>
<td><strong>Developer</strong></td>
<td><strong>Username</strong></td>
<td><strong>Role/Position</strong></td>
<td><strong>Status</strong></td>
</tr>
<tr>
<td>Gr�gory Demar</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=259">Greg</a></td>
<td>Original creator of Coppermine</td>
<td>retired</td>
</tr>
<tr>
<td>Jack</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=6">datajack</a></td>
<td>Developer</td>
<td>retired</td>
</tr>
<tr>
<td>DJ Axion</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=9">djaxion</a></td>
<td>Developer</td>
<td>retired</td>
</tr>
<tr>
<td>Scott Gahres</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=66">gtroll</a></td>
<td>Developer</td>
<td>retired</td>
</tr>
<tr>
<td>Hyperion</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=125">hyperion01</a></td>
<td>Developer</td>
<td>retired</td>
</tr>
<tr>
<td>John Asendorf</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=30">jasendorf</a></td>
<td>Developer</td>
<td>retired</td>
</tr>
<tr>
<td>Jay Hao-En Liu</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=59">Oasis</a></td>
<td>Developer</td>
<td>retired</td>
</tr>
<tr>
<td>Christopher Brown-Floyd</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=1874">omniscientdeveloper</a></td>
<td>Developer</td>
<td>retired</td>
</tr>
<tr>
<td>Timothy</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=6949">skybax</a></td>
<td>Developer</td>
<td>retired</td>
</tr>
<tr>
<td>David Holm</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=14">wormie_dk</a></td>
<td>Developer</td>
<td>retired</td>
</tr>
<tr>
<td>Mark Zerr</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=11">zarsky99</a></td>
<td>Tester</td>
<td>retired</td>
</tr>
<tr>
<td>mitirapa</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=133">mitirapa</a></td>
<td>Porter (Cross Platform Devel.)</td>
<td>retired</td>
</tr>
<tr>
<td>Moorey</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=13">moorey</a></td>
<td>Web Designer</td>
<td>retired</td>
</tr>
<tr>
<td>Maarten Hagoort</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=404">DJ Maze</a></td>
<td>Developer (nuke team)</td>
<td>retired</td>
</tr>
<tr>
<td>Eyal Zvi</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=94">EZ</a></td>
<td>Developer</td>
<td>retired</td>
</tr>
<tr>
<td>Clive Leech</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=56">casper</a></td>
<td>Supporter</td>
<td>retired</td>
</tr>
<tr>
<td>Dennis Nakano</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=19311">madeinhawaii</a></td>
<td>Supporter</td>
<td>retired</td>
</tr>
<tr>
<td>Roberta</td>
<td><a href="http://coppermine-gallery.net/forum/index.php?action=proarchivo;u=24398">Blueiris</a></td>
<td>Supporter</td>
<td>retired</td>
</tr>
</tbody></table>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="contributors"></a>
<h2>8.2 Contributors</h2>
<table border="0" cellpadding="4" cellspacing="6">
<tbody><tr>
<td><a href="http://coppermine.sourceforge.net/board/index.php?action=proarchivo;u=101">DaMysterious</a></td>
<td>DaMysterious has created loads of fantastic temas for Coppermine</td>
</tr>
<tr>
<td><a href="http://coppermine.sourceforge.net/board/index.php?action=proarchivo;u=1399">Nanobot</a></td>
<td>Doug has done the vBulletin v3 bridge archivo</td>
</tr>
<tr>
<td><a href="http://www.sanisoft.com/aboutus.php3">Girish Nair</a></td>
<td>Girish has contributed to the film strip feature</td>
</tr>
<tr>
<td><a href="http://coppermine.sourceforge.net/board/index.php?action=proarchivo;u=378">Jason Kawaja</a></td>
<td>Jason did the <a href="http://coppermine.sourceforge.net/board/index.php?topic=1985.0">memberlist hack</a></td>
</tr>
</tbody></table>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="codebase"></a>
<h2>8.3 Coppermine uses code from the following free softwares :</h2>
<p><strong>phpBB</strong><br>
Author: phpBBGroup <br>
URL: <a href="http://www.phpbb.com/">http://www.phpbb.com/</a><br>
</p>
<p><strong>phpMyAdmin</strong><br>
Author: phpMyAdmin devel team<br>
URL: <a href="http://www.phpmyadmin.net/">http://www.phpmyadmin.net/</a><br>
</p>
<p><strong>phpPhotoAlbum</strong><br>
Author: Henning St�verud<br>
E-mail: henning AT stoverud DOT com<br>
URL: <a href="http://www.stoverud.com/PHPhotoalbum/">http://www.stoverud.com/PHPhotoalbum/</a><br>
</p>
<p><strong>DOM Tooltip 0.6.0</strong><br>
Author: Dan Allen<br>
E-mail: dan AT mojavelinux DOT com<br>
URL: <a href="http://www.mojavelinux.com/forum/viewtopic.php?t=127">http://www.mojavelinux.com/forum/viewtopic.php?t=127</a><br>
Note: DOM Tooltip, which is being used with the tema "styleguide" only, is released under <a href="http://www.gnu.org/copyleft/lesser.html">LGPL</a><br>
</p>
<p><strong>TAR/GZIP/ZIP Archive Classes</strong><br>
Author: Devin Doucette<br>
E-mail: darksnoopy AT shaw DOT ca<br>
</p>
<p><strong>Exifixer</strong><br>
Author: Jake Olefsky<br>
URL: <a href="http://www.offsky.com/software/exif/index.php">http://www.offsky.com/software/exif/index.php</a><br>
</p>
<p><strong>Codelifter Slideshow</strong><br>
URL: <a href="http://www.codelifter.com/">http://www.codelifter.com</a><br>
</p>
<p><strong>PHPMailer</strong><br>
Author: <a href="http://sourceforge.net/project/memberlist.php?group_id=26031">PHPMailer Team</a><br>
URL: <a href="http://phpmailer.sourceforge.net/">http://phpmailer.sourceforge.net/</a><br>
</p>
<p><strong>PHP Calendar Class Version 1.4</strong><br>
Author: David Wilkinson<br>
E-mail: davidw AT cascade DOT org DOT uk<br>
URL: <a href="http://www.cascade.org.uk/software/php/calendar/">http://www.cascade.org.uk/software/php/calendar/</a><br>
</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr>
<a name="copyright"></a>
<h2>8.4 Copyright and disclaimer</h2>
<p>This application is opensource software released under the <a href="http://www.gnu.org/copyleft/gpl.html">GPL</a>.</p>
<p>Because the program is licensed free of charge, there is no warranty
for the program, to the extent permitted by applicable law. Except when
otherwise stated in writing the copyright holders and/or other parties
provide the program "as is" without warranty of any kind, either
expressed or implied, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose. The
entire risk as to the quality and performance of the program is with
you. Should the program prove defective, you assume the cost of all
necessary servicing, repair or correction. </p>
<p>Coppermine Photo Gallery is Copyright � 2002 - 2006 Gr�gory DEMAR and the Coppermine Dev Team, All Rights Reserved.<br>
</p>
<p><a class="back" href="#top">Volver arriba</a></p><hr> </td></tr></tbody></table>
</body></html>