Administrator s Guide Version Released June 18, 2009

Transcription

1 Administrator s Guide Version Released June 18, 2009

2 Table of Contents 1. Welcome...5 What is new?...6 How Gallery Server Pro works...6 Requirements...6 Product key...7 Known issues Installing Gallery Server Pro...8 Installation overview...8 Upgrading from Gallery Server Pro Performing a new installation of Gallery Server Pro, SQLite Performing a new installation of Gallery Server Pro, SQL Server Uninstalling Gallery Server Pro Running Gallery Server Pro Running Gallery Server Pro for the first time Adding your media library to Gallery Server Pro Working with Albums Overview of albums Creating an album Edit album information Delete an album Move or copy an album Assign album thumbnail object Synchronize an album Album Ownership Gallery Server Pro 2.3 Administrator s Guide Page 2 of 238

3 User Albums Hiding Albums Working with Media Objects Overview of media objects Adding media objects Edit captions Download media objects Delete objects Delete high-resolution version of images Move or copy media objects and albums Rearrange objects Rotate objects Watermarking Image metadata Searching Rendering media objects in the browser Microsoft Silverlight User Management and Security Overview Require everyone to log on Users Roles Self Registration Site Administration Overview Gallery Server Pro 2.3 Administrator s Guide Page 3 of 238

4 Site Settings General Site Settings Site Settings Backup and Restore Data General Error Log Membership - User Settings Membership Users Membership Roles Albums General Media Objects General Media Objects Media Object Types Media Objects Images Media Objects Video / Audio / Other Configuration Settings in galleryserverpro.config Working with Galleries Overview SQLite users SQL Server users Creating a read-only gallery Membership Configuration Membership overview New membership in current SQL database Use existing membership schema in current SQL database Use existing membership schema in different SQL database Integrate Gallery Server Pro with Active Directory Data Provider Gallery Server Pro 2.3 Administrator s Guide Page 4 of 238

5 About the data provider model Moving data between SQL Server and SQLite Behind the scenes: how the data provider is specified in the config files Create a custom data provider Customizing Gallery Server Pro Overview Styling Multi-language support Integrate into an ASP.NET web application Integrate into non-asp.net web sites (iframe Method) Using Internet Information Services (IIS) Manager IIS IIS 7 and IIS Configuring NTFS Permissions In Microsoft Windows Management Tools for SQLite and SQL Server Overview SQL Server SQLite Glossary Welcome Gallery Server Pro is a free, open source web application for sharing photos, video, audio, documents and other files. It s like having your own personal YouTube or Flickr site. It is intended for users who want to share large collections of media objects on their own web site while maintaining a high degree of control. Gallery Server Pro 2.3 Administrator s Guide Page 5 of 238

6 What is new? View the Release History page to see full details of each release. How Gallery Server Pro works Gallery Server Pro is a web application you install on your web server or your web hosting company's server. Add your media library by synchronizing your directory containing photos, videos and other media objects with the Gallery Server Pro database. You can also ZIP up your files and upload them. Gallery Server Pro automatically creates a thumbnail image to represent each media object. If you upload a high resolution image, a bandwidth-friendly, compressed version is created. EXIF, IPTC and other types of metadata are extracted and stored in the database. Media object files are stored on the local hard drive or a UNC-accessible location such as a NAS device or network share. Metadata about these files, such as width, height, caption, etc. are stored in the database. When web users browse your albums and media objects, Gallery Server Pro queries the database for the necessary information, and dynamically renders a custom web page. If watermarking is enabled, the watermark is applied to the image before it is sent. Requirements Server Requirements: Microsoft.NET Framework 2.0 or higher Microsoft AJAX Extensions 1.0 (not required if.net Framework 3.5 or higher is installed) Internet Information Services (IIS) 5.0 or higher or a compatible web server such as UltiDev Cassini Web Server Optional: SQL Server 2000 or higher, including the free Express versions. It does not have to be installed on your server, but it must be available on the network. Optional: Microsoft.NET Framework 3.0 or higher. If present, Gallery Server Pro extracts additional image metadata not accessible to version 2.0 (primarily titles and keywords). Optional: SMTP server (required for functionality). The use of the SQLite database engine requires the web application to run under Full Trust or that System.Data.SQLite.dll be in the server's Global Assembly Cache (GAC). If these are not possible, SQL Server is supported in reduced trust environments. Client Requirements: Any modern web browser (IE 5+, Netscape 6+, Firefox, Opera, Safari, Chrome) Gallery Server Pro 2.3 Administrator s Guide Page 6 of 238

7 Product key Gallery Server Pro is fully functional for the first 30 days. At the end of the trial period, a watermark appears on each image and the Site admin area becomes read-only. Enter a product key to restore full functionality. The key is free and easily obtained from the Product Key Wizard at The purpose of the product key is simple: to encourage you to return to the web site after a trial period to give you an opportunity to provide financial support. Gallery Server Pro is supported entirely by your donations. Without them, I must look for work elsewhere, and that takes away from the time I can spend on it. You can help make Gallery Server Pro a success and prove that the open source model works by providing a donation when you request the product key. To get your product key, go to the Product Key Wizard at If you provide a donation, the wizard will temporarily transfer you to PayPal where you can make a secure donation by credit card or through your bank. Whether or not you provide a donation, you will receive a valid product key at the end of the wizard. BONUS: I periodically offer free thank you gifts to donors. If a promotion is active, it will be offered in the Product Key Wizard. Known issues Internet Explorer does not support the rounded corners CSS style, so objects appear with square corners. (Upgrading from a previous version) The upgrade wizard imports some, but not all, settings in your current web.config and galleryserverpro.config files. If you edited either of these files with a text editor you may find those settings are not imported. In this case they must be manually migrated. All settings that are configurable through the UI are imported. (SQL Server, after upgrading from ) You may receive the error "EXECUTE permission was denied on the object 'gs_getversion'". This can occur when using a SQL login that was created during the original installation. This can be resolved by executing the following in SQL Management Studio: GRANT EXECUTE ON [dbo].[gs_getversion] TO [gs_galleryserverprorole] Restoring data to a SQL Server 2000 database using the built-in restore function is not supported. Restoring data to SQL Server using the Restore function requires SQL permissions equivalent to that provided in the db_ddladmin or db_owner roles. You may have to manually configure the SQL user using a tool such as SQL Management Studio to provide this permission prior to using the Restore feature. If an upload is aborted because it violates the size limitation set by the administrator, the user cannot upload another file until the page is refreshed. This is a limitation with the ComponentArt Upload control, which is used in IE and Firefox in Full Trust environments. Gallery Server Pro 2.3 Administrator s Guide Page 7 of 238

8 IIS 7: If the.divx MIME type has been previously configured in IIS, the web site will not render correctly. Either remove the MIME type using IIS Manager or delete the following section in web.config: <staticcontent><mimemap fileextension=".divx" mimetype="video/divx" /></staticcontent> IIS 6: IIS will not serve.divx files unless you specify the.divx MIME type in IIS Manager. 2. Installing Gallery Server Pro Installation overview There are three versions of Gallery Server Pro available for download: Gallery Server Pro web application (pre-compiled, 32-bit) Gallery Server Pro web application (pre-compiled, 64-bit) Gallery Server Pro source code (Visual Studio format) Most users will want the 32-bit or 64-bit pre-compiled web application. Download the source code version if you are interested in viewing or modifying the code. The source code version must be compiled prior to deployment. It is packaged as a Visual Studio solution and can be opened in either Visual Studio 2005 or Visual Studio 2008, including the freely available Visual Web Developer 2008 Express SP1, downloadable from Microsoft. If you are using VS 2005, use the solution file named TIS.GSP (Visual Studio 2005).sln. Note: The only difference between the 32-bit and 64-bit downloads is the SQLite provider located in System.Data.SQLite.dll. Gallery Server Pro uses a web-based installer to configure the database and initialize the data. The setup process is largely the same whether you are installing it locally or using a hosting provider. The basic steps are: 1. Extract the files from the ZIP and convert the root directory to a web application in IIS. 2. Use your browser to run the web-based installer and step through the wizard. 3. You re done! Step by step instructions are later, but first let's touch on few topics that may affect your installation: Upgrading previous versions Choosing a data provider Reduced trust installation Integrating with an existing web site Gallery Server Pro 2.3 Administrator s Guide Page 8 of 238

9 .NET Framework 3.5 What to do if you get an error Upgrading previous versions You can upgrade from previous versions and keep all your captions and other data. To upgrade from Gallery Server Pro Follow the steps in the section Performing a new installation of Gallery Server Pro, SQL Server. The install wizard will detect the 1.0 data and offer to automatically import the data into the 2.X tables. To upgrade from Gallery Server Pro Upgrading follows these basic steps (detailed instructions are below): 1. (2.0 users only) Run one or two SQL scripts to update the database structure. 2. Temporarily save your web.config, galleryserverpro.config and galleryserverpro_data.sqlite files. 3. Replace the files in the web application directory with the new ones (but don't delete your media object files). 4. Run the upgrade wizard. For detailed, step by step upgrade instructions, go to the section Upgrading from Gallery Server Pro Choosing a data provider There are two types of data managed by Gallery Server Pro: Media files - These are your images, videos, audio files, and documents. The default storage location is the gs\mediaobjects directory in the Gallery Server Pro web application, but you can specify any location on the web server's hard drive or any UNC-accessible location. Gallery data - Information about the media files, such as captions, width, height, and the album to which they belong, are stored in either a SQLite or SQL Server database. The web-based installer will ask you to choose whether to store data in SQLite or SQL Server. SQLite ( is a self-contained, serverless, zero-configuration, transactional, mostly ACID compliant SQL database engine. It is embedded in various Adobe products, Mozilla Firefox, and even in the Apple, Solaris, and Symbian operating systems. The data reside in a file named galleryserverpro_data.sqlite in the App_Data directory of your web application. Microsoft SQL Server ( is an enterprise class client-server database engine. It is in use by many companies and supported by a large number of web hosting providers. Most users should choose SQLite due to its ease of management, high performance, and potentially lower hosting costs. You may want to use SQL Server if any of the following are true: Gallery Server Pro 2.3 Administrator s Guide Page 9 of 238

10 You are comfortable with SQL Server. You are already using SQL Server and want to keep all your data in one place. You are forced to run Gallery Server Pro in a Medium Trust environment and are not able to install System.Data.SQLite.dll in the Global Assembly Cache (GAC). You require the gallery to continue working during Synchronize operations. (No other user can write to the database during a synchronization in SQLite, but SQL Server does not have this limitation.) Your installation of Gallery Server Pro is mission-critical and you don t want to take any chances with your data. Since SQLite is file-based, there are rare circumstances where the hard drive reports to the database engine that the data is written to disk, when in fact it has not yet completed the operation. If, at this moment, your PC loses power, SQLite will think the data is safely stored, but it is not. You are already using ASP.NET membership and have your users in SQL Server. For example, you may have DotNetNuke installed and want GSP to use the existing user accounts in your SQL Server DotNetNuke database. You have other applications besides the Gallery Server Pro web application interacting with the data file. You may encounter file locking issues and slowed performance as multiple threads wrestle for access to the file. This is a situation where a traditional client-server database such as SQL Server is superior. Reduced trust installation Some hosting providers force.net applications to run at Medium Trust. Gallery Server Pro runs well in this environment, albeit with a few caveats: The SQLite data provider requires either Full Trust or that the System.Data.SQLite.dll assembly be installed in the Global Assembly Cache (GAC) on the web server. If you are running Gallery Server Pro in a reduced trust environment (such as GoDaddy), then SQL Server is your only option, unless you can convince the web administrator to install System.Data.SQLite.dll in the GAC. Instructions for installing an assembly into the GAC can be found in the document Assembly Cache Viewer. The directory containing the media object files must reside within the web application. The real-time feedback provided by the ComponentArt File Upload control requires Full Trust. In reduced trust environments, Gallery Server Pro automatically replaces the ComponentArt control with the standard ASP.NET FileUpload control. It still lets you upload files to the server, but it doesn't give the fancy real-time feedback to inform you of the upload progress. Installing Gallery Server Pro in Medium Trust using SQL Server If SQLite is not an option because you are running in a reduced trust environment and you cannot install System.Data.SQLite.dll in the GAC, then you can install Gallery Server Pro using the SQL Server database engine. Before you run the installer, you must remove all references to SQLite from the application: Gallery Server Pro 2.3 Administrator s Guide Page 10 of 238

11 1. Replace the contents of web.config with the contents of web_sqlserver.config. You will find web_sqlserver.config in the root of the Gallery Server Pro web application. (If you are running on a.net 3.5 server, then use web_sqlserver_3.5.config.) 2. Delete the file System.Data.SQLite.dll from the bin directory. 3. Open gs\config\galleryserverpro.config in a text editor. Find this section: <dataprovider defaultprovider="sqlitegalleryserverproprovider"> Change it to this: <dataprovider defaultprovider="sqlservergalleryserverproprovider"> After you make these changes, follow the installation instructions below. Integrating with an existing web site The easiest way to install Gallery Server Pro is as a stand-alone web application living in its own directory. But you can integrate it with an existing web site using one of two techniques: (ASP.NET sites only) Add the Gallery Server Pro user control to a page (.aspx) or user control (.ascx) in your web appliction Install Gallery Server Pro as a stand-alone application on an ASP.NET-compatible server. Then add an iframe to your existing site that points to this location. Read more in the section Customizing Gallery Server Pro..NET Framework 3.5 You do not need Microsoft AJAX Extensions 1.0 if you have.net Framework 3.5 or higher installed. However, you do need to replace the web.config file with one that is configured for 3.5. The download includes two versions of web.config that are pre-configured for.net 3.5. They are in the same directory as web.config, and are named: web_3.5.config web_sqlserver_3.5.config Replace the web.config file in your web application with one of these. Most users, including ALL SQLite users, will use web_3.5.config. If you are running in a reduced trust environment, then you may need to use web_sqlserver_3.5.config instead. (This version has all references to SQLite removed from it.) Gallery Server Pro 2.3 Administrator s Guide Page 11 of 238

12 What to do if you get an error As a security measure Gallery Server Pro does not display detailed information if an error occurs. However, you can enabled detailed error messages on the Site Settings - General page in the Site admin area. The option is called Display detailed error message when an exception occurs. If the error is preventing the application from starting, you won't be able to get to the Site admin area. In this case, you can turn on detailed error messages by editing the configuration file galleryserverpro.config. Open the file - located at \gs\config\galleryserverpro.config - in any text editor and set showerrordetails="true". Hopefully the detailed message will help you discover the cause. If you cannot figure it out and want to post a question to the support forum, please copy ALL the text and include it in your post. Remember to search this document and the forum before posting your question. Once you get a detailed error message, search the Gallery Server Pro forums and/or the internet for more information. If you cannot resolve it on your own, post a message in the forum. Upgrading from Gallery Server Pro Attention Developers: If you wrote custom code that interacts with the column OwnedBy in the gs_album table, be aware of an important change. This column is cleared of any data during the upgrade. Previous versions of Gallery Server Pro put the username who created the album in this field, but it was never used. This field is now critical to the new album ownership feature and for it to work correctly, this field must be initially blank. This only affects you if you customized Gallery Server Pro to use this field for some purpose. Attention 2.0 Users If you are upgrading from 2.0, you must update the database to the schema. You can do this by manually executing one or two SQL scripts against your database. Note that you do not need upgrade the web application to ; only the database structure through the SQL scripts described below. Update the database before running the upgrade wizard. Backup your database before executing the SQL scripts as a safety precaution. If you are upgrading from : Run the following SQL scripts: GS_ _to_ _upgrade.sql and then GS_ _to_ _upgrade.sql. They can be found in the installer\sql directory of these downloads: Gallery Server Pro and Gallery Server Pro , , or : Run the SQL script GS_ _to_ _upgrade.sql. It can be found in the installer\sql directory of this download: Gallery Server Pro Follow these detailed instructions for upgrading to the latest version. Gallery Server Pro 2.3 Administrator s Guide Page 12 of 238

13 1. Download the ZIP file containing the Gallery Server Pro web application from 2. Make a backup of web.config (in the root directory of the Gallery Server Pro web application) and galleryserverpro.config (in the config directory). The upgrade wizard will ask for these files so it can import your settings. Attention 2.0 Users: Open web.config in a text editor such as Notepad. Search for all instances of the text GalleryServerDbConnection and replace it with SqlServerDbConnection. You are doing this because the name of the SQL Server connection string changed beginning with 2.1 If you skip this step the Upgrade Wizard will not import your connection string. 3. (SQLite users only) Make a backup of galleryserverpro_data.sqlite (in the App_Data directory). 4. Delete all the web application directories and files in your Gallery Server Pro web directory EXCEPT your mediaobjects directory. If you store your media objects outside this web directory, you can safely delete the mediaobjects directory. 5. Extract the contents of the Gallery Server Pro ZIP file to the web directory. Note: If you downloaded the source code, you must compile it before copying the files. 6. Use Windows Explorer to give the IIS application pool identity modify permission to the web application directory (ex: C:\inetpub\wwwroot\galleryserverpro\). Note: If you are not sure how to do this step, read the section Configuring NTFS Permissions In Microsoft Windows. Note: Technically, Gallery Server Pro requires modify permission only to the following directories: App_Data, config, and mediaobjects. If desired, you can assign modify permission to each of these directories instead of applying them to the parent directory. Note: This step is not necessary if the directories already contain the required permissions. Note: If you are using a hosting provider, follow the process provided by them for performing the above steps. Again, this step is often not necessary. 7. If.NET 3.5 is installed, replace the web.config file in the root of the web application with either web_3.5.config or web_sqlserver_3.5.config. Note: For more information about the difference between the two 3.5 versions of web.config, refer to the.net Framework 3.5 section. 8. (SQLite users only) Copy your backup of galleryserverpro_data.sqlite over the file in the App_Data directory. 9. Use a web browser to navigate to the web upgrade wizard. The URL is in this form: default.aspx?g=upgrade. For example, if you installed to then the upgrade wizard is at Gallery Server Pro 2.3 Administrator s Guide Page 13 of 238

14 10. Follow the instructions to complete the upgrade. The wizard will import common settings from your old web.config and galleryserverpro.config files. Note: Some settings are not imported from the original files. This is intentional as some values, such as HTML templates in galleryserverpro.config, may have been updated and should not be overwritten. If you have manually edited either of these files, there is the possibility those changes will not be imported by the wizard. In this case, manually update the file. 11. When the upgrade is complete, you will see a confirmation message. Congratulations! Click the link to go to your upgraded Gallery Server Pro site. Attention SQL Server users upgrading from 2.0, 2.1, or 2.2 Version 2.3 requires a new table and some other changes to the data schema. Gallery Server Pro checks the version of your database schema during the first page load after running the upgrade wizard. If your schema is out of date, as it will be after upgrading the web application, Gallery Server Pro automatically runs a SQL script to update the data schema. You may get a SQL error if your SQL logon does not have permission to create or alter database objects. If this happens, temporarily update your connection string in web.config to specify a user with elevated permissions. You can revert to the original connection string once the SQL script has completed. Another option is to manually run the SQL upgrade script. You will find it in the source code download, in the TIS.GSP.Data.SqlServer project. The file is named SqlUpgrade_2_1_3162_to_2_3_3421_SqlServer2005.sql. If you are using SQL Server 2000, use the file named SqlUpgrade_2_1_3162_to_2_3_3421_SqlServer2000.sql IMPORTANT! When you are finished, it is strongly recommended that you disable the install and upgrade wizards to prevent unauthorized access to your server. To disable, change the value of the ENABLE_SETUP hidden field to FALSE in install.ascx and upgrade.ascx (in the gs\pages directory) or delete the files. Troubleshooting Your Upgrade If, after upgrading, you cannot log in or your gallery appears empty, it is possible that one or more settings from your old config files were not migrated to the new ones. Open your old and new copies of web.config and galleryserverpro.config and inspect the following sections: web.config: <connectionstrings> web.config: <membership>, <rolemanager>, and <profile>, especially the defaultprovider and applicationname attributes. galleryserverpro.config: <dataprovider> Gallery Server Pro 2.3 Administrator s Guide Page 14 of 238

15 Each of the sections above should be the same between the old and new versions. If you discover that you must manually update something, this is a bug, so please report it. If using SQLite, verify that you copied your.sqlite data file over the empty one in the App_Data directory. If you receive a generic error like "I am sorry, but Gallery Server Pro encountered an error", enable detailed reporting as described above. Performing a new installation of Gallery Server Pro, SQLite Follow these instructions to install Gallery Server Pro using SQLite as the data store. Set up the web application 1. Download the ZIP file containing the Gallery Server Pro web application from 2. Extract the contents of the zip file to a directory on your web server. For example, C:\inetpub\wwwroot\galleryserverpro\. 3. (.NET 3.5 users only) Replace web.config with the 3.5 version. See the.net Framework 3.5 section for more information. 4. Use Internet Information Services (IIS) Manager to configure this directory as a web application. (Click Start Run and then type inetmgr to start IIS Manager.) 5. (IIS 5 and 6 only) Use IIS Manager to make sure the application is running under ASP.NET 2.0 and that the default document is default.aspx. Note: For more information on using IIS Manager, refer to Using Internet Information Services (IIS) Manager. 6. Use Windows Explorer to give the user account IIS is running under modify permission to the web application directory (ex: C:\inetpub\wwwroot\galleryserverpro\). Note: If you are not sure how to do this step, read the section Configuring NTFS Permissions In Microsoft Windows. Note: Technically, Gallery Server Pro requires modify permission only to the following directories: App_Data, config, and mediaobjects. If desired, you can assign this permission to each of these directories instead of applying them to the parent directory. Note: Depending on your system and where you install the files, this step may not be needed. You can skip this step for now and come back to it if you receive permission-related errors. Note: If you are using a hosting provider, follow the process provided by them for performing the above steps. This step is not necessary for some hosting companies, so you can try skipping it for now and only come back to it if you receive an error. Gallery Server Pro 2.3 Administrator s Guide Page 15 of 238

16 Running the web-based installer 1. Start the Install Wizard located at default.aspx?g=install. For example, if you installed to then enter The screen should look like this: Note: You may receive the following error: Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Could not load file or assembly 'System.Web.Extensions, Version= , Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. Gallery Server Pro 2.3 Administrator s Guide Page 16 of 238

17 If you get this message, you do not have Microsoft ASP.NET 1.0 AJAX installed. Get it here: 6 Or you can upgrade to.net Framework 3.5, which includes Ajax functionality. If you do this, read the section.net Framework 3.5 for more information. 2. Click next. Review the license agreement. If you agree to the terms, select the checkbox and click Next. 3. The following screen appears. Select the SQLite database engine. If you want to use the SQL Server engine, then follow the instructions in the section Performing a new installation of Gallery Server Pro, SQL Server. Gallery Server Pro 2.3 Administrator s Guide Page 17 of 238

18 4. The next step requests the username, password, and address you would like to use for the administrator account of your new Gallery Server Pro site. You will use this account to log on to Gallery Server Pro to perform administrative tasks. Fill in the fields and click Next. Gallery Server Pro 2.3 Administrator s Guide Page 18 of 238

19 5. The final step indicates that all required information has been gathered and it is ready to perform the installation. Click Next. Gallery Server Pro 2.3 Administrator s Guide Page 19 of 238

20 6. If the installation was successful, you will see a confirmation message. This page may also specify additional steps you must take to complete the installation. Follow the instructions given. For example, in the screen shot below, the galleryserverpro.config file must be manually updated. Be sure to update the file before clicking the link to go to your gallery. Note: You must manually update web.config and/or galleryserverpro.config when the IIS application pool identity does not have modify permission to the directory containing these files. Gallery Server Pro 2.3 Administrator s Guide Page 20 of 238

21 7. Congratulations! Click the link to go to your new Gallery Server Pro site. IMPORTANT! When you are finished, it is strongly recommended that you disable the install and upgrade wizards to prevent unauthorized access to your server. To disable, change the value of the ENABLE_SETUP hidden field to FALSE in install.ascx and upgrade.ascx (in the gs\pages directory) or delete the files. All the files in the directory \gs\pages\installer\ may be deleted as well. Performing a new installation of Gallery Server Pro, SQL Server Follow these instructions to install Gallery Server Pro using SQL Server as the data store. Note: Users upgrading from Gallery Server Pro 1.0 should also follow these steps. Make sure you choose SQL Server from the Select Data Provider step and select your existing database from the Select Database Instance step. Set up the web application 1. Download the ZIP file containing the Gallery Server Pro web application from Gallery Server Pro 2.3 Administrator s Guide Page 21 of 238

22 2. Extract the contents of the zip file to a directory on your web server. For example, C:\inetpub\wwwroot\galleryserverpro\. 3. (.NET 3.5 users only) Replace web.config with the 3.5 version. See the.net Framework 3.5 section for more information. 4. Use Internet Information Services (IIS) Manager to configure this directory as a web application. (Click Start Run and then type inetmgr to start IIS Manager.) 5. (IIS 5 and 6 only) Use IIS Manager to make sure the application is running under ASP.NET 2.0 and that the default document is default.aspx. Note: For more information on using IIS Manager, refer to Using Internet Information Services (IIS) Manager. 6. Use Windows Explorer to give the user account IIS is running under modify permission to the web application directory (ex: C:\inetpub\wwwroot\galleryserverpro\). Note: If you are not sure how to do this step, read the section Configuring NTFS Permissions In Microsoft Windows. Note: Technically, Gallery Server Pro requires modify permission only to the following directories: App_Data, config, and mediaobjects. If desired, you can assign this permission to each of these directories instead of applying them to the parent directory. Note: Depending on your system and where you install the files, this step may not be needed. You can skip this step for now and come back to it if you receive permission-related errors. Note: If you are using a hosting provider, follow the process provided by them for performing the above steps. This step is not necessary for some hosting companies, so you can try skipping it for now and only come back to it if you receive an error. 7. Use your SQL management tool such as SQL Management Studio to create a new, empty database. Note: You can optionally install Gallery Server Pro into an existing database that contains other applications. The only requirement is that there must not be any name conflicts. All database objects in Gallery Server Pro are prefixed with gs_, so there is a good chance the tables and stored procedures used by Gallery Server Pro will be unique. Running the web-based installer 1. Start the Install Wizard located at default.aspx?g=install. For example, if you installed to then enter The screen should look like this: Gallery Server Pro 2.3 Administrator s Guide Page 22 of 238

23 Note: You may receive the following error: Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Could not load file or assembly 'System.Web.Extensions, Version= , Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. If you get this message, you do not have Microsoft ASP.NET 1.0 AJAX installed. Get it here: 6 Or you can upgrade to.net Framework 3.5, which includes Ajax functionality. If you do this, read the section.net Framework 3.5 for more information. 2. Click next. Review the license agreement. If you agree to the terms, select the checkbox and click Next. Gallery Server Pro 2.3 Administrator s Guide Page 23 of 238

24 3. The following screen appears. Select the SQL Server database engine. If you want to use the SQLite engine, then follow the instructions in the section Performing a new installation of Gallery Server Pro, SQLite. Gallery Server Pro 2.3 Administrator s Guide Page 24 of 238

25 4. On the next screen, specify the desired SQL Server instance and the security credentials the Installer should use to configure the database. The credentials must have permission to create database objects and, if you request a new login be created (see step 7), must be able to create a new login as well. Note: These credentials are used only by the installer and are discarded once the installation is complete. A later step in the wizard will request the connection setting used for normal operation. Note: The SQL Server database engine does not have to be installed on the web server. As long as the web server can see the database, it doesn t matter where it is. If you are connecting to a local installation, specify (local), , or the name of the server. Include the SQL Server instance name if necessary, such as when using SQL Express or when there is more than one instance of SQL Server. The instance name of a default installation of SQL Express on the local server is.\sqlexpress (replace the period with the server name or IP address if it is on another machine, such as MYSERVER\SQLExpress or \SQLExpress). Gallery Server Pro 2.3 Administrator s Guide Page 25 of 238

26 5. When you click Next, the installer will attempt to connect. If it is successful, you will see a drop-down list with your database as one of the options. Select your database and click Next. Gallery Server Pro 2.3 Administrator s Guide Page 26 of 238

27 6. When you select the database, the web installer will check to see if it contains any data from Gallery Server Pro 1.0. If it finds data, it will give you the option to import the data from version 1.0 into the version 2.3 tables. 7. Specify the account Gallery Server Pro will use to communicate with the database during normal operation. This can be the same account specified earlier, an existing login, or a new SQL login. The credential entered here will be used for the runtime connection string and written into the web.config file in the root of the web application. Note: If you specify a login that does not exist or is not a member of the database you selected, the wizard will attempt to create it during installation. Gallery Server Pro 2.3 Administrator s Guide Page 27 of 238

28 8. The next screen provides installation options. Leave the option Script ASP.NET Membership checked unless the database already has the ASP.NET Membership installed or you want to configure Gallery Server Pro to communicate with an external Membership data store. Note: For more information on configuring the membership, see the Membership Configuration section below. Gallery Server Pro 2.3 Administrator s Guide Page 28 of 238

29 9. The next step requests the username, password, and address you would like to use for the administrator account of your new Gallery Server Pro site. You will use this account to log on to Gallery Server Pro to perform administrative tasks. Fill in the fields and click Next. Gallery Server Pro 2.3 Administrator s Guide Page 29 of 238

30 10. The final step indicates that all required information has been gathered and it is ready to perform the installation. Click Next. Gallery Server Pro 2.3 Administrator s Guide Page 30 of 238

31 11. If the installation was successful, you will see a confirmation message. This page may also specify additional steps you must take to complete the installation. Follow the instructions given. For example, in the screen shot below, the web.config and galleryserverpro.config files must be manually updated. Be sure to update these files before clicking the link to go to your gallery. Note: You must manually update web.config and/or galleryserverpro.config when the IIS account that the installer is running under does not have modify permission to the directory containing these files. Gallery Server Pro 2.3 Administrator s Guide Page 31 of 238

32 12. Congratulations! Click the link to go to your new Gallery Server Pro site. IMPORTANT! When you are finished, it is strongly recommended that you disable the install and upgrade wizards to prevent unauthorized access to your server. To disable, change the value of the ENABLE_SETUP hidden field to FALSE in install.ascx and upgrade.ascx (in the \gs\pages\ directory) or delete the files. All the files in the directory \gs\pages\installer\ may be deleted as well. Uninstalling Gallery Server Pro To uninstall Gallery Server Pro, delete the web application files and the data store. Gallery Server Pro does not use any other location such as the registry or the Program Files directory. To delete the files and directories in the web application, navigate to the directory using a file utility such as Windows Explorer. Delete the root application directory. For example, if you installed Gallery Server Pro to C:\inetpub\wwwroot\galleryserverpro\, then delete C:\inetpub\wwwroot\galleryserverpro\. Note: Use caution when deleting the mediaobjects directory, since it may contain media files that you want to keep! If using SQL Server as the data store, then use Enterprise Manager (SQL 2000) or Management Studio (SQL 2005/2008) to delete the database containing Gallery Server Pro. Gallery Server Pro 2.3 Administrator s Guide Page 32 of 238

33 Note: If you are using the database to store more than just Gallery Server Pro data, then obviously you do not want to delete the entire database. You can delete just the Gallery Server Pro objects. All Gallery Server Pro objects have the prefix gs_, so they are easy to identify. There are several tables, stored procedures, and one user-defined function. If you are storing users and roles in the database, and they are not needed for any other application, they can be deleted by deleting the tables and stored procedures that begin with aspnet_ and views that begin with vw_aspnet_. 3. Running Gallery Server Pro Running Gallery Server Pro for the first time The first time you run Gallery Server Pro, a screen similar to the one shown below is displayed. Log in with the administrator account you specified during the installation. An Actions menu appears to the left of the album breadcrumb menu. This menu gives you access to most of the functionality in Gallery Server Pro. Any function the logged on user does not have permission to execute is disabled. Gallery Server Pro 2.3 Administrator s Guide Page 33 of 238

34 The installer adds an album named Samples and one photo. Click the album to see a thumbnail of the photo. Click the thumbnail of the photo to see a larger version, as shown below. Download objects in ZIP Show image metadata Start/pause slideshow Delete media object Download media file Get permalink Rotate image Copy to another album Move to another album Gallery Server Pro 2.3 Administrator s Guide Page 34 of 238

35 Notice the toolbar that appears above the photo. Individual buttons are shown or hidden based on the authorization of the current user and whether certain features are enabled. Below is a table that describes the toolbar buttons. Toolbar button Show image metadata Download media file Toggle hi-res image Get permalink Start/pause slideshow Move to another album Copy to another album Rotate image Delete media object Description Displays a resizable, movable popup window with metadata, such as EXIF and IPTC, from the image. Does not apply to non-image media objects. Download the media file to the user s computer. Shows or hides the original, high resolution version of an image, if it exists. This button is hidden when no high resolution image exists or the user does not have permission to view it. Displays a hyperlink that can be used to link directly to the current media object. This is useful because the Next/Previous buttons use AJAX callbacks to load the media object, which does not update the URL in the browser s address bar. Starts or pauses a slide show of images in the current album. Slide shows only display images; any video, audio, or documents in the album are skipped. Transfers the current media object to another album. The user is redirected to another page where the destination album can be selected. Not shown if the user does not have permission to move media objects. Copies the current media object to another album. The user is redirected to another page where the destination album can be selected. Not shown if the user does not have permission to copy media objects. Redirects the user to another page where the image can be rotated. Applies only to images. Not shown if the user does not have permission to edit media objects. Deletes the current media object, including the thumbnail, compressed version (for images), and original media file. Adding your media library to Gallery Server Pro This section helps you add your existing media library to Gallery Server Pro. See the section Working with Media Objects for additional options and more detailed information. Let s say you have thousands of photos and video clips on your hard drive at C:\MyPicsAndVideo\. Follow these steps to add them to Gallery Server Pro. Gallery Server Pro 2.3 Administrator s Guide Page 35 of 238

36 1. Copy your media files from C:\MyPicsAndVideo\ to the mediaobjects directory in the Gallery Server Pro web application. For example, if you installed Gallery Server Pro at C:\inetpub\wwwroot\galleryserverpro\, then copy the files to C:\inetpub\wwwroot\galleryserverpro\mediaobjects\. Note: By default, Gallery Server Pro uses the mediaobjects directory to store and manage the media files, but you can specify any UNC-accessible location. Refer to the section Media Objects - General for more information. 2. Configure Gallery Server Pro to accept the types of media files in your collection. For example, your collection may consist of JPG, GIF, WMV, and AVI files. Use your browser to log on as an administrator, then click Site admin on the Actions menu. In the menu that appears, click Media Object Types. A list with more than 100 file types appears. By default, only JPG and JPEG files are enabled. Select those file types that exist in your collection and click Save changes. 3. Select Synchronize from the Actions menu. The Synchronize page appears. Select the option Include child directories (recursive). Click Synchronize. A popup window appears showing the progress of the synchronization as Gallery Server Pro analyzes each of your files. Click Close when finished. 4. You are done! Browse your media collection by clicking the root album from the album breadcrumb menu (default name is All albums). 4. Working with Albums Overview of albums Gallery Server Pro stores media objects in albums, and each album holds zero or more media objects and/or child albums. This is similar to how Windows stores directories and files. In fact, Gallery Server Pro stores albums as directories in the file system, and media objects are stored as files (which makes sense, since they are files.) Gallery Server Pro starts with one album that serves as a container for all other albums. This top-level album is called the root album and by default is named All albums. This album can never be deleted. Media objects and albums are added to the root album. In turn, each child album can store additional media objects and/or child albums. There is no limit to the number of media objects and albums one can store, except the limit presented by hard drive space limitations and the operating system for maximum file path length. That is, since some versions of Windows have a maximum file path length of 260 characters, the full path to the album (directory) must be less than this limit. You must be logged on to perform any action in Gallery Server Pro that modifies albums or media objects. Once logged on, the Actions menu (shown below) is displayed. Gallery Server Pro 2.3 Administrator s Guide Page 36 of 238

37 Note: If the Actions menu does not appear when you are logged on, that means you do not have permission for any of its menu items. In this case, Gallery Server Pro does not render the menu. Only those menu items that are valid for the current album, and for which the current user has permission, are enabled. For example, if the logged on user does not have Add album permission, the Create album menu item will be disabled. Creating an album An album is a container that holds one or more media objects and/or child albums. Upon installation Gallery Server Pro has one album named All albums. To create a new album select Create album from the Actions menu. The following page appears. Gallery Server Pro 2.3 Administrator s Guide Page 37 of 238

38 Step 1: Type the desired name of the album in the Album name field. The album name is limited to 200 characters. To make the album private, check the box labeled Private album. Learn more about private albums in the Hiding Albums section. Step 2: Specify the album to contain the new album. The existing albums are displayed in a tree view. A check box appears next to all albums for which the current user has Add album permission. By default, the album you were viewing when you chose Create album from the Actions menu, is selected. Note: Only those albums the user has permission to add an album to are shown. After clicking Create album, the album is created and a screen showing its contents is displayed, as below. It is, of course, empty. Gallery Server Pro 2.3 Administrator s Guide Page 38 of 238

39 Edit album information To edit the information for the albums, select Edit album info from the Actions menu or double click the rectangular area in which the Album s name, summary and begin and end dates appear, as shown below. Double click to edit Note: If nothing happens when you double click in the album area, then you are not logged on or you do not have Edit album permission. The Edit album box appears as shown below. Gallery Server Pro 2.3 Administrator s Guide Page 39 of 238

40 Fill in the text boxes as desired. Note character maximums for the text boxes and the necessary format for the date fields. All fields are optional. To learn more about private albums see the section Hiding albums. Click Save to return to the album view with the newly entered information displayed. Note: Learn more about album ownership in the Album Ownership section. The begin and end date is not used by Gallery Server Pro and is intended only convey to the viewer the dates associated with the contents of the album. When not specified, the date label is hidden. It will re-appear if a date is entered. * Behind the Scenes * Album information is saved to the web server through an AJAX callback. How album titles correspond to the directory names on the hard disk Recall that each album in Gallery Server Pro has a matching directory in the media objects folder. When an album s title is changed, Gallery Server Pro modifies the name of the directory for that album to match the title. In the example above, the album title is Photos and the corresponding directory in the media objects folder is also named Photos. If the title is changed to My Favorite Photos, Gallery Server Pro will modify the directory name to My Favorite Photos. This is all well and good, but we have a problem. Most (all?) Windows operating systems cannot handle a directory path longer than 255 characters. Since a title in Gallery Server Pro can be up to 200 characters, one could reach this limitation pretty easily. To help prevent this, Gallery Server Pro only uses the first twenty-five characters of the title for the directory name. As a result, you will notice an album with the title This is a long title for an album has a directory with the name This is a long title for. Gallery Server Pro 2.3 Administrator s Guide Page 40 of 238

41 Note: When a gallery is configured as read-only, Gallery Server Pro never changes the files or directory names. You might want to change this behavior. For example, you may have all your photos in a directory structure with lots of long names, and you don t want Gallery Server Pro truncating them when you edit the album s title. There are two configuration settings in galleryserverpro.config available to modify this behavior: defaultalbumdirectorynamelength Gallery Server Pro will truncate directory names longer than this value. The default value is 25, but it can be any value from 1 to 255. synchalbumtitleanddirectoryname Indicates whether to update the directory name corresponding to an album when the album's title is changed. The default value is true. Setting it to false tells Gallery Server Pro to never alter the directory name. The only exception to this is when Gallery Server Pro has to slightly tweak the name of a directory to prevent a naming conflict. For example, this may happen if you move or copy an album into a directory containing another album with the same name. When this setting is false, the configuration setting defaultalbumdirectorynamelength has no effect. This setting can be changed on the Media Objects - General page in the Site admin area. Delete an album To delete an album, first navigate to album to be deleted. Choose Delete this album from the Actions menu. The following confirmation page appears. If you are sure you want to delete the album, click Delete album. The album, all child albums, and all media objects in the album(s) are permanently deleted. There is no undo function, so use caution! Gallery Server Pro 2.3 Administrator s Guide Page 41 of 238

42 Note: For media objects, both the records in the data store and the media files on the hard drive are permanently deleted. Note: The current user must have Delete child album permission for the parent album of the album being deleted. If the album contains media objects, they are also deleted, even if the user does not have Delete media object permission. Performance tip: ASP.NET automatically restarts the web application when a directory within the application hierarchy is deleted. This causes a noticeable delay when deleting albums and may cause errors for other users who are synchronizing, uploading files, or performing other tasks. This, unfortunately, is a "feature" of ASP.NET 2.0 that occurs when a directory is deleted within the web application. The easiest solution is to put the media objects directory the web application (for example, D:\my_media_objects). Read the section Media Objects General for more information about changing the media objects directory. Another solution is to create a directory junction. Move or copy an album Albums are copied in the same way that media objects are copied. See Move or copy media objects and albums for instructions. Assign album thumbnail object Each album has an album thumbnail image. This image is shown whenever an icon representing an album is displayed on a web page. In the screen shot below, there are two albums and two images. The images shown for the two albums are the thumbnail images for that album. Gallery Server Pro 2.3 Administrator s Guide Page 42 of 238

43 Album thumbnail images By default, the first media object added to an album is used as the thumbnail image for the album. However, you can choose any media object in the album. To designate an album s thumbnail image, choose Assign thumbnail from the Actions menu. The media objects are then displayed each with a radio button underneath, as below. Gallery Server Pro 2.3 Administrator s Guide Page 43 of 238

44 Select the image you would like to use as the thumbnail image for the album. When you click Assign thumbnail, the image you selected is now set to be displayed whenever an icon view of the album is shown. NOTE: You must select an image from the current album. If the image currently set as the thumbnail image for an album is moved or deleted, Gallery Server Pro automatically selects the next media object in the album as the thumbnail image. If no image is available (because the album is empty), a default image is used. The format and text displayed on the default image can be specified on the Albums General page in the Site administration console. Synchronize an album Gallery Server Pro maintains two related sets of data the media files stored in directories on the web server s hard drive and metadata about those files and albums in the database. If the two sets of data ever Gallery Server Pro 2.3 Administrator s Guide Page 44 of 238

45 get out of synch, you can synchronize the database with the media files on the hard drive to restore data integrity. When should you synchronize? You might want to synchronize when: You just installed Gallery Server Pro and you want to load the database with your entire media library. You just extracted a bunch of photos or videos from your digital camera and you want to quickly add them to Gallery Server Pro. You could ZIP them up and use the Add objects menu command, but some people find it easier to copy the media files to the web server and then synchronize. You have a read-only gallery and want to add or remove media objects and albums. You prefer using FTP to transfer files to the web server. FTP is generally more reliable when dealing with large files. You added, moved, copied, or deleted images using Windows Explorer instead of the Gallery Server Pro interface, causing the database to become out of synch with the media files on the web server's hard drive. You used a third party program like PhotoShop to alter one or more images, and you want Gallery Server Pro to recreate the thumbnail and compressed images. In simple terms, the synchronization procedure updates the Gallery Server database with information about the media files on the web server s hard drive and makes sure the media files have valid thumbnail and compressed versions. Remember that the files themselves are not stored in the database; only metadata about them (size, width, height, etc ) Synchronizing also ensures the album has a valid album thumbnail image. See the section about setting the album thumbnail image to learn more about what this is. You can synchronize an album, an album and all child albums, or the entire gallery. To synchronize an album, navigate to the album you want to synchronize. Then click the Synchronize command from the Actions menu. The following screen appears. Note: The current user must have Synchrnoize permission for the album being synchronized. Gallery Server Pro 2.3 Administrator s Guide Page 45 of 238

46 There are four options you can check. They are: Include child directories (recursive) When checked, any albums within this album are also synchronized. Recently added directories are added to the gallery as new albums. If the current album does not contain any child albums, this setting has no effect. Overwrite existing thumbnail images When checked, new thumbnail images are created when you synchronize the database, even if it means overwriting existing thumbnails. The thumbnails are created from the original media object. If unchecked, a new thumbnail is created only if it doesn't exist. Synchronizing the database will run faster if you leave this option unchecked. Overwrite existing compressed images When checked, new compressed images are created when you synchronize the database, even if it means overwriting existing compressed images. The compressed images are created from the original image. If unchecked, a new compressed image is created only if doesn't exist. This setting applies only to images in the gallery. Synchronizing the database will run faster if you leave this option unchecked. NOTE: Compressed versions of images will exist only for images whose file size is larger than the Compression limit or whose length is larger than the Compressed image length. More information about these settings can be found in the Media Objects Images section. Gallery Server Pro 2.3 Administrator s Guide Page 46 of 238

47 Re-import metadata for existing images When checked, metadata that was extracted from images when they were first added to Gallery Server Pro are replaced with the current metadata in the original image file. Metadata includes items such as camera model, shutter speed, title, and keywords. Gallery Server Pro supports the following formats: EXIF, XMP, text, IFD, and IPTC. For example, this is useful if you used a program like Vista Photo Gallery to add keywords to the image files and you want Gallery Server Pro to retrieve this information to aid in searching. This setting has no effect on non-image media objects. More information about image metadata is in the Image metadata section. Note: Metadata that may exist in the original image files are not replicated to the thumbnail and compressed versions. If you delete the original versions of photos using the Delete high-res images command, that means there is no metadata to extract during subsequent synchronizations. The consequence of this is that checking this option after you have deleted the original images will cause you to lose the metadata that was extracted from the original files. Therefore, it is recommended to leave this option unchecked when you synchronize an album whose original, high resolution photos have been deleted. When you have selected the desired options, click Synchronize. A popup window like that shown below provides real-time status of the task. Gallery Server Pro 2.3 Administrator s Guide Page 47 of 238

48 A message will indicate when the task is complete, and a Close button will appear on the popup window. Click Close to close the popup window. NOTE: You can click Cancel to stop a synchronization, but be aware this can cause the database to become out of synch with the media files on the hard drive. If you discover issues after cancelling, start another synchronization and allow it to finish. Some additional points to remember about synchronizing: Note: The properties mentioned below in bold can be found on the Media Objects General page in the Site administration console (i.e. Original file storage location, Thumbnail image storage location, and Compressed image storage location) Gallery Server Pro will ignore any file whose type is not enabled on the Media Object Types page in the Site administration console. It also ignores hidden files, even if they are an enabled file type. Gallery Server Pro 2.3 Administrator s Guide Page 48 of 238

49 Gallery Server Pro NEVER modifies or deletes the original media files during synchronizing. (Rotating is the only function in Gallery Server Pro that modifies the original media file, and that applies only to images.) Gallery Server Pro searches for media files only in the directory corresponding to the specified album. If the Include child directories option is enabled, then all files below the specified directory will also be synchronized. Gallery Server Pro never searches for or adds media files from outside the Original file storage location. Thumbnail images are stored in the Thumbnail image storage location. By default, all thumbnail images begin with the prefix zthumb_. If desired, this can be changed on the Media Objects - General page in the Site admin area. Compressed images are stored in the Compressed image storage location. By default, all compressed images begin with the prefix zopt_. If desired, this can be changed on the Media Objects - General page in the Site admin area. If the thumbnail or compressed images are ever deleted, they can be recreated by performing a synchronization. Depending on your web server, Gallery Server Pro typically synchronizes from one to one hundred images per second. Keep in mind that if you have thousands of images, it may take a long time. Gallery Server Pro does its best to preserve captions and other information you enter about a media object. For example, if you use Windows Explorer to move a media file from one directory to another, and then synchronize the database, Gallery Server Pro will re-link the file with the existing database record, thus preserving the information. (This is done by creating a hash code of the file based on its name and creation date and searching for a matching hash code.) However, Gallery Server Pro does not preserve album information (e.g. the summary and begin/end dates) if you move a directory to another directory outside of the Gallery Server Pro user interface. In general, you should use the Gallery Server Pro web interface when you add, move, copy, and delete media objects and albums. You can modify any Gallery Server Pro media object in a third party program like PhotoShop without losing the caption or other data you entered, as long as you don t change the file name or the file s created date/time stamp. * Behind the Scenes * During a synchronization, database records are inserted, updated and deleted, and compressed and thumbnail versions of media objects are created and/or overwritten on the hard drive. Specifically, synchronizing performs these steps: 1. A table named gs_synchronize exists in the database to manage the synchronization process. When a synchronization is started, this table is updated so that other users cannot begin a second synchronization until the first one is complete. 2. Starting with the first file Gallery Server Pro finds in the directory representing the specified album, Gallery Server Pro checks its file type to determine if it should be managed by Gallery Server Pro. If it is, it tries to find the corresponding record in its database, based on a hash of the file name and the date/time stamp of when the file was created. Gallery Server Pro 2.3 Administrator s Guide Page 49 of 238

50 3. If a record is found, it is updated with current information about the file, such as its size and the album to which it belongs. 4. If a record isn t found, a new media object is created. 5. Gallery Server Pro checks to make sure a thumbnail image exists to represent this media object. If the media object is an image, it verifies a compressed image exists. If not, one is created. If the option Overwrite existing thumbnail image or Overwrite existing compressed image is checked, then new versions are always created, even if it means overwriting an existing compressed or thumbnail image. 6. Gallery Server Pro continues processing each file it finds. If the Include child directories option is checked, then all the album s subdirectories are recursively processed. 7. If any album or media object records in the data store weren t updated during this synchronization, then they must not have corresponding media files on the hard disk, and the records are deleted from the data store. Album Ownership An album owner can add, edit, and delete objects within the album. Think of it as being an administrator of an album. The permissions an owner has propagate to all child albums and cannot be revoked at a lower level. For example, if an owner can create child albums, he or she can create child albums on those child albums, and so on. This is consistent with the overall security pattern in Gallery Server Pro that permissions always propagate downward. Only administrators (that is, users in a role with Allow Administer Site permission) can assign a user as the owner of an album. Owners cannot re-assign ownership to another user (unless the owner is an administrator, of course). Assign the owner of an album on the Edit album info dialog window. The window appears when you select Edit album info from the Actions menu or double click the album title and summary area. The dialog appears as seen here: Gallery Server Pro 2.3 Administrator s Guide Page 50 of 238

51 By default, the owner of an album can add, edit, and delete objects within the album. The permissions given to owners are defined in a role named _Album Owner Template and can be easily changed using the Manage Roles page in the Site Admin area. If a user who is the owner of an album is deleted, the album is updated to no longer have an owner. Multiple ownership for simplified management Only one user at a time can be assigned as the owner of an album. However, child albums can be given a different owner. Since albums always inherit permissions from their parent albums, this has the effect of allowing multiple owners. For example, above we see that Albin is the owner of an album called Photos. If that album contained a child album Summer Vacation and we brought up the Edit album info dialog, it would look like this: Gallery Server Pro 2.3 Administrator s Guide Page 51 of 238

52 Notice the note about Albin being an inherited owner. If an administrator assigns another user - say, Sam - as the owner of this child album, both Sam and Albin have owner rights to the Summer Vacation album, but only Albin has owner rights to the containing Photos album. This multiple-owner feature can be used to simplify certain management scenarios. Imagine a gallery configured in a corporate intranet. The system administrator in IT assigns the manager of the marketing department as the owner of the album Marketing Photos. This album has a child album for each employee in the marketing department. Each employee is assigned as the owner of one of the albums. The manager has full editing permission on all albums in the Marketing Photos album, but each employee can only edit the objects in their album. Note: A very similar feature - user albums - provides an album for each user and assigns that user as the owner of the album. Using user albums may be a better approach depending on your requirements. * Behind the Scenes * When a user is assigned as the owner of an album, a new role is created with the user as the sole member. The permissions in the role are copied from the _Album Owner Template role. Note that if the template role is assigned to one or more albums, those albums are also applied to the new role. Gallery Server Pro 2.3 Administrator s Guide Page 52 of 238

53 The name of the role follows this pattern: Album Owner - {UserName} - {Album Title} (album {album ID}) For example: "Album Owner - Albin - Photos (album 3)" You can view these roles on the Manage Roles page by selecting the checkbox labeled Show roles that support the album ownership and user album features. The ownership feature (and the user album feature) is an abstraction of the underlying security model of using roles to limit access to albums. Both of these features manipulate roles behind the scenes to manage the desired level of access for a user. User Albums Overview Gallery Server Pro can be used in community scenarios where users automatically receive a personal album they manage. A variety of configuration options are available to satisfy the majority of needs. For example, the following are possible: User albums are publicly available for everyone to view, even anonymous users Users can add photos to their album, but not other file types such as videos, nor can they create child albums. Only logged on users can view albums User albums are private and viewable only to each user Many more possibilities By default, users can perform any function within their album, such as adding and deleting media objects and child albums, rearranging objects, and synchronizing. These permissions can be adjusted by editing the role named _Album Owner Template. Note: If you don't see the role _Album Owner Template on the Manage Roles page, it may not exist. This role is automatically created the first time it is needed. You can trigger its creation by assigning a user as an owner of an album or enabling user albums and navigating to your album. When user albums are enabled, a user can jump to their personal album by clicking the icon at the top right of every page: Gallery Server Pro 2.3 Administrator s Guide Page 53 of 238

54 The user album starts out empty. Only the user who owns the album (and administrators, of course) is able to add, edit, and delete objects, unless the administrator has configured a gallery that gives multiple users editing permission to the album that contains the user albums. Enabling user albums User albums are enabled on the User Settings page in the Site admin area. This is the relevant portion of that page: There are several configuration options available. Gallery Server Pro 2.3 Administrator s Guide Page 54 of 238

55 Always redirect to user's album after logging on - When enabled, the user's personal album is displayed each time the user logs on. If the user has disabled the album on their account page, the top level album is displayed. Album name template - Specifies the template to use for naming the album that is created for new users. The placeholder string {UserName}, if present, is replaced by the user's account name. No other placeholder strings are supported. Album summary template - Specifies the template to use for the album summary of a newly created user album. No placeholder strings are supported. User album container album - Specifies the album in which user albums are created. If a different album is selected, existing user albums are not automatically moved. To move them to another album, use the standard functionality for moving albums. When user albums are enabled, an album is automatically created when a user is created or, if necessary, when a user logs on. If you have configured Gallery Server Pro to connect to an existing membership system, each user's user album will be created on they fly when they log on, so no special migration or setup procedure is necessary. Configuring the visibility of albums Whether or not any album, including user albums, are visible to a person depend on two key settings: 1. Anonymous users: Visible only when the setting Allow anonymous browsing is enabled (setting is on the General page in the Site admin area). 2. Logged on users: Visible when a user belongs to a role with view permission to an album. The first option is straight forward. When anonymous browsing is enabled (the default), users who are not logged on can view all objects in the gallery except ones marked as private. Disable this option to require users to log on to view objects. The second setting - roles - is a little more complex. The roles to which a user belongs can be controlled in several ways: An administrator manually adds a user to a role. Self-registration is enabled, and an administrator has specified new users to be automatically assigned to one or more roles. An administrator has assigned a user as the owner of an album, which creates a role behind the scene to manage the security access. For a full discussion of roles, read the Roles section. Gallery Server Pro 2.3 Administrator s Guide Page 55 of 238

56 Enabling user albums on demand User albums can be configured so that a user album is not created for a user until the user requests it. This can be useful when the user album feature may only be used by a subset of users, and you do not want a bunch of empty albums sitting in the user album gallery. Follow these steps to enable the on-demand feature of user albums. 1. Enable user albums on a system-wide level as described in the Enabling user albums section above. 2. Open the web.config file in the root of the web application in a text editor. Look for this line: <add name="enableuseralbum" defaultvalue="true" type="string" allowanonymous="false"/> 3. Set defaultvalue to false: <add name="enableuseralbum" defaultvalue="false" type="string" allowanonymous="false"/> 4. Save the file and close it. After this change, user albums are no longer automatically created for users. If a user album already exists, it is not deleted. When a user wants to enable their personal album, he or she clicks the My account link in the top right of the page. Their account page has a section where the user album can be enabled: Gallery Server Pro 2.3 Administrator s Guide Page 56 of 238

57 When the user checks this box and saves the page, an album is created during the next page viewing. Warning: When a user disables their album, it is permanently deleted and cannot be recovered. Read the next section about deleting user albums for more information. Deleting user albums It is important to understand what happens to user albums in various circumstances. Deleting a user When an administrator deletes a user or the user deletes their own account on the account page, the user album is also deleted, including any media objects and child albums it contains. The items are not recoverable. Disabling user albums at the user level When a user disables their personal album on the account page, all media objects and child albums in their album are deleted. The items are not recoverable. Disabling user albums at the system level When an administrator disables user albums on the User Settings page in the Site admin area, user albums are not deleted, but they are no longer treated as user albums by the gallery - they are just regular albums. If desired, the administrator can delete them through the delete album or delete objects page. Deleting an album that is a user album If the delete album or delete objects task on the Actions menu is used to delete a user album, Gallery Server Pro will allow it to be deleted, but the album will be automatically re-created the next time the user's owner logs on. Because of this "my album keeps coming back" behavior, this is not the recommended way to get rid of a user album. To delete an individual user album, the user can disable their user album on their account page. To delete all user albums, the administrator can disable user albums at the system level and then manually delete them. Hiding Albums An album can be hidden from anonymous and logged on users so that, from the user s perspective, the album and any child albums and media objects do not exist. They don t appear in the browser, cannot be navigated to via URL, and don t appear in any task pages. However, you can configure individual users to have full access to these albums. Gallery Server Pro 2.3 Administrator s Guide Page 57 of 238

58 SECURITY WARNING: If your media objects directory is within the web application (which is the default), then users can bypass security by guessing the URLs to the media object (e.g. If you wish to prevent this, move the directory outside the web application so that IIS will not serve requests to the objects. Information about changing the media objects directory is in the Media object storage section. Hiding albums from anonymous users To hide all albums from users who are not logged on (anonymous users), disable anonymous browsing for the entire gallery. This is described in the Require everyone to log on section. To hide an individual album from anonymous users, mark an album as private. This is done in the Edit album popup, which is shown when selecting Edit album info from the Actions menu or double clicking the album title/summary/date area. The Edit album popup appears below. When an album is private, a small lock icon appears next to the album name, as shown below. Gallery Server Pro 2.3 Administrator s Guide Page 58 of 238

59 Private albums have the following features: They are never shown to anonymous users (users who are not logged on). The privacy setting of an album applies to all child albums and media objects. You cannot make a child album visible if its parent is hidden. The privacy setting of an album has no effect for logged on users. Hiding an album from a logged on user Each user in Gallery Server Pro is a member of one or more roles. Roles are assigned permissions such as View albums / objects, Add albums, and Delete media object. To make an album invisible to a user, ensure the user does not belong to any roles with View albums / objects permission for the album. Gallery Server Pro 2.3 Administrator s Guide Page 59 of 238

60 5. Working with Media Objects Overview of media objects A media object is any file managed by Gallery Server Pro. Typically these are photos, video, audio, and documents, but they can be any file type. The default installation enables JPG and JPEG files. To enable additional types, use the Media Object Types page in the Site administration console. A media object can also be raw HTML text. This is called an external media object, and can be used to: Link to media objects on other servers such as YouTube videos. Display custom snippets of HTML. Link to other web pages by embedding other web pages in an iframe HTML tag. All media objects can be rearranged, moved or copied to another album, deleted and have their captions edited. Additional features are available for images. Gallery Server Pro extracts metadata such as camera model, shutter speed, and more from images and displays it in a popup window. Gallery Server Pro also provides the ability to apply a watermark to images, run a slide show, and rotate images. The available functions also depend on the authorization of the logged on user. A user with Administer site permission has unrestricted access to all functions for all albums. A user with restricted access, however, will find particular functions disabled in the Actions menu or toolbar items will be missing from the media object view page. Any media object - except external media objects - can be downloaded by clicking the Download toolbar item on the media object view page. Media files are rendered to the browser using HTML defined in templates in the configuration file \gs\config\galleryserverpro.config. For example, QuickTime files are rendered in an <object>; PDF files are rendered in an inline frame (iframe), and Silverlight-compatible files (.wmv,.wma,.mp3,.asf, and.asx) are rendered using the Microsoft Silverlight plug-in. This behavior is fully customizable - you can even vary the HTML by browser. See the section Rendering media objects in the browser for more information. Adding media objects There are several ways to add media objects to the gallery. Each of these is discussed below. 1. Use a web browser to upload individual files. 2. Use a web browser to add external media objects. 3. Use a web browser to upload a ZIP file containing multiple files. 4. Configure Gallery Server Pro to change the media objects directory to an existing directory containing media objects, then use a web browser to synchronize Gallery Server Pro with the files. Gallery Server Pro 2.3 Administrator s Guide Page 60 of 238

61 5. Manually copy files into the Gallery Server Pro media objects directory, then use a web browser to synchronize Gallery Server Pro with the files. Upload individual files using a web browser You can add individual media objects to a single album with this technique. 1. Log on to Gallery Server Pro with an account that has permission to add media objects. 2. Navigate to the album to which you want to add media objects. 3. Choose Add objects from the Actions menu. A page similar to one of the following screen shots appears. Note: If you do not see the Actions menu, either you are not logged on or the account under which you are logged on does not have permission to execute any of its commands. Add objects page for Internet Explorer and Firefox users, server running at Full Trust (screen shot taken from Firefox on Windows): Gallery Server Pro 2.3 Administrator s Guide Page 61 of 238

62 Add objects page for other browsers and when the server is running at less than Full Trust (screen shot taken from Safari on Windows): 4. Click the Browse button and select a file. To add more than one file, click the Add File button. 5. Optionally select one of the options near the bottom: Discard original file - After the file is uploaded and a thumbnail and compressed version is created, delete the original file. This can help preserve disk space usage. Applies only to images. Administrators can force this option to be always selected through a configuration option on the Media Objects - Images page in the Site admin area. Treat ZIP file as media object - When checked, Gallery Server Pro will not extract the contents of any ZIP files that are uploaded. Instead, the ZIP file will be preserved and treated as its own Gallery Server Pro 2.3 Administrator s Guide Page 62 of 238

63 media object. This option will be disabled when the ZIP file extension is disabled on the Media Object Types page in the Site admin area. 6. Click Upload. The Upload Status progress bar will indicate the progress of the upload. Note: The Upload Status progress bar is shown only to Internet Explorer and Firefox browsers and only when the application is running at Full Trust. Note: The caption for each object defaults to the file name. For images, if the title metadata item has been specified, that value is used for the caption instead of the file name. 7. The files are transferred to the web server and added to the Gallery Server Pro database. When the upload is complete, you will see thumbnail-sized objects representing the object(s) you have just uploaded on the album view page. Gallery Server Pro 2.3 Administrator s Guide Page 63 of 238

64 Add external media objects Note: As a security precaution, a default installation does not allow external media objects to contain HTML. Read the section Security considerations when allowing HTML and javascript in user-entered input to learn how to safely allow HTML to be entered. You can add media objects that refer to objects hosted elsewhere, such as another web site on your intranet or even the internet. These objects are called external media objects and are really nothing more than HTML text that contain anything you want. Typical uses: Link to media objects provided as embed code on other servers (e.g. YouTube). Display custom snippets of HTML. Link to other web pages by embedding other web pages in an iframe HTML tag. For example, you might upload your videos files to Silverlight Streaming and then add links to those videos within Gallery Server Pro. Since the videos are streamed straight from the external web site, you save on disk storage and bandwidth costs. Any web site that offers embed code can be used. A few common ones are YouTube, MSNBC, CNN, Comedy Central's Daily Show, and metacafe. For example, below is a screenshot of a video on YouTube. Notice, at center right, the embed code. This code can be added to any web site to refer to the original video. Copy this code and paste into Gallery Server Pro to add the video. Although it appears within the Gallery Server Pro gallery and can be browsed, moved, copied, and deleted, the video is actually stored on - and served from - the YouTube web site. Gallery Server Pro 2.3 Administrator s Guide Page 64 of 238

65 Follow these instructions to add an external media object: 1. Log on to Gallery Server Pro with an account that has permission to add media objects. 2. Navigate to the album to which you want to add media objects. 3. Select the Add objects link from the Actions menu. Click the External Content tab. The screen shown below appears. Note: If you do not see the Actions menu, either you are not logged on or the account under which you are logged on does not have permission to execute any of its commands. Gallery Server Pro 2.3 Administrator s Guide Page 65 of 238

66 4. Select the type of media object you are adding (audio, image, video, or other). This is used to determine an appropriate thumbnail image for the object. 5. Enter a title. 6. Paste the HTML text into the HTML Fragment / Embed Code textbox. 7. Click Add media object. The media object will be created and shown, as seen here: Gallery Server Pro 2.3 Administrator s Guide Page 66 of 238

67 8. When you click on the thumbnail image, the object will appear: Gallery Server Pro 2.3 Administrator s Guide Page 67 of 238

68 Note: External media objects do not respect the setting for automatically playing video and audio on the Media Objects - Video / Audio / Other page in the Site admin area. That setting applies only to media files that are uploaded or synchronized in Gallery Server Pro. Security considerations when allowing HTML and javascript in user-entered input In a default installation, Gallery Server Pro does not allow HTML or javascript to be entered by the user in any textbox. This is the safest way to run your gallery, but it effectively prevents you from creating external media objects. You can enable HTML input on the Membership - User Settings page in the Site admin area, as seen here: Gallery Server Pro 2.3 Administrator s Guide Page 68 of 238

69 You can also specify the allowed HTML tags and attributes. The default list does not allow dangerous tags such as <script> and event handlers such as onclick. There are no known security vulnerabilities when HTML is enabled with the default list. When you add embed code for an external media object, you may receive a message like this: This message is saying you cannot add the object because it contains the HTML tags object, param and embed, and it contains the attributes width, height, value, type, allowscriptaccess, allowfullscreen. Go to the Membership - User Settings page and add these tags and attributes; then you will be able to add this object. Use caution when adding HTML tags and attributes to the allowed lists, especially event attributes such as onclick, onmouseover, etc. Consider the following HTML snippet, which sends the logged-on user's cookie to a remote web site and is a common technique used in session hijacking attacks to impersonate another user: <p onclick="document.location=' + document.cookie">click me</p> In a default installation, this text cannot be entered as an external media object (or an album or media object title, for that matter) because it contains HTML. If you enable HTML, the text is still not valid because it contains the onclick attribute which is not in the list of allowed HTML attributes. However, if you add onclick to the list, this text can be entered, even if you have the javascript option disabled. Gallery Server Pro 2.3 Administrator s Guide Page 69 of 238

70 This is because javascript is very difficult to accurately detect. As shown in the screen shot above, there is a configuration option to prevent javascript, but this setting only looks for the presence of the <script> tag and the string "javascript:", and neither of these are present in the HTML example above. Sure, Gallery Server Pro could search for document.cookie, but if it does that it needs to search for all the possible javascript statements, which is cumbersome and error-prone. Note that the following sample does not work and is therefore not a security risk: <a href="document.location=' + document.cookie">click me</a> Even though the a tag and href attribute are in the list of allowed HTML, hyperlinks require the use of the string "javascript:" like this: <a href="javascript:document.location=' + document.cookie">click me</a> All of the allowed attributes in a default Gallery Server Pro installation require the use of the string "javascript:", so as long as you are restricting javascript input, you are protected. A tip for adding external media objects that use script or banned tags Some web sites include javascript or banned tags in their embed code, so you may find a legitimate reason to add HTML content that includes the <script> tag or the string "javascript:". For example, here is a snippet of video from CNN.com: <script src=" 6/02/bpr.plane.debris.found.cnn" type="text/javascript"></script><noscript>embedded video from <a href=" Video</a></noscript> The only way to add this to the gallery is to do three things: (1) enable javascript; (2) add the HTML tag script to the list of allowed tags; (3) add the HTML attribute type to the list of allowed attributes. Doing this makes you vulnerable to an XSS attack, so I do not recommend you use these settings on a long-term basis. However, you can change the settings just long enough to add the code. Then go back to Site admin and revert to the previous settings. The snippet will continue to work, synchronizing won't break it, and your site is still safe. Forcing the menu to appear above media objects Certain plug-ins, in certain browsers, will render in the browser as the top level object, preventing other objects from displaying above them. For example, in Safari, when you add a YouTube video, the menu appears behind the video, like this: Gallery Server Pro 2.3 Administrator s Guide Page 70 of 238

71 In some cases you can prevent this issue by tweaking the embed code provided by the web site. For example, the default embed code from YouTube looks similar to this: <object width="425" height="344"> <param name="movie" value=" <param name="allowfullscreen" value="true"></param> <embed src=" type="application/x-shockwave-flash" allowfullscreen="true" width="425" height="344"> </embed> </object> Gallery Server Pro 2.3 Administrator s Guide Page 71 of 238

72 This code instructs the browser to use the Flash plug-in to play the video. If you know a little about Flash, then you know that you can get a little better behavior by adding a <param > element and a wmode attribute to the <embed > tag, like this: <object width="425" height="344"> <param name="movie" value=" <param name="allowfullscreen" value="true"></param> <param name="wmode" value="opaque"></param> <embed src=" type="application/x-shockwave-flash" allowfullscreen="true" width="425" height="344" wmode="opaque"> </embed> </object> When you add a media object with this modified embed code, the menu now appears on top of the Flash plug-in: Gallery Server Pro 2.3 Administrator s Guide Page 72 of 238

73 Although this trick works for Flash, other plug-ins behave differently. For example, while I was able to get the menu to render correctly for locally hosted files played in the Silverlight plug-in, I don't know of a technique for tweaking the embed code for objects hosted at Silverlight Streaming. At this moment, the menu hides behind the plug-in for Firefox users (IE works correctly). Please contact me if you find a solution. Note: It is not currently possible to edit the HTML fragment of an existing external media object. Gallery Server Pro 2.3 Administrator s Guide Page 73 of 238

74 Upload a ZIP file containing multiple files This is a flexible technique allowing you to efficiently add a virtually unlimited number of media objects very quickly. First prepare a ZIP file containing the files you wish to add to Gallery Server Pro, then upload the ZIP file using the Add objects menu option. Refer to the previous section for uploading a file. When you select a file to upload, choose the ZIP file you prepared. Note: If the ZIP file contains multiple directories, even nested ones, then those directories are converted to albums. Use this to your advantage! For example, the first time you use Gallery Server Pro, you may have dozens, hundreds, or even thousands of photos you want to add. Put them all into a ZIP file with the desired directory hierarchy, and upload it to Gallery Server Pro. Configure Gallery Server Pro to point to an existing directory containing media objects, then use a web browser to synchronize Gallery Server Pro with the files. By default, Gallery Server Pro stores all media object files in a subdirectory named mediaobjects. This can be changed to any location on the web server s hard drive. To change this location, follow these steps: 1. Log on to Gallery Server Pro with an account that has Administer site permission. 2. Click the Actions menu and go to Site admin. 3. In the left menu, navigate to Media Objects General. At the top of the page is a section called Media object storage. It allows you to specify the storage location for media objects, the thumbnail that represent the media objects, and the optimized (compressed) versions of images. 4. You can enter a path relative to the web application, or a full physical path to any UNC-accessible location. Examples: C:\my_media, gs\mediaobjects, \\server1\media, \\mynas\media 5. Click Save changes. If successful, you will see a confirmation message. A label below each text box shows the full physical path to the directory you specified. This helps confirm the directory location is where you intend it when you enter a relative path. Note: Changing the location does not move media objects to the new location. For example, if you choose a new location for thumbnail images, you should immediately synchronize the database to generate new thumbnails in the new location (or you can use Windows Explorer to manually copy the files). If you change the media objects path and then synchronize the database, the files in the new location will replace all database entries for the previous media objects. Use care so you do not inadvertently delete objects. Follow the steps in the Synchronize an Album section to synchronize the media object files on the hard disk with the Gallery Server Pro database. Manually copy files into the Gallery Server Pro media objects directory, then synchronize By default, Gallery Server Pro stores all media object files in the directory gs\mediaobjects in the web aplication. You can copy files to this directory and then synchronize the files with the Gallery Server Pro database. If you copy directories into this folder, they will be converted into albums in Gallery Server Pro. Gallery Server Pro 2.3 Administrator s Guide Page 74 of 238

75 You can copy the files using any technique such as FTP or Windows Explorer. Once you have finished, follow the steps in the Synchronize an Album section to synchronize the media object files on the hard disk with the Gallery Server Pro database. Edit captions Each media object has a caption associated with it. You can edit all captions for an entire album at once, or edit a caption for a single media object. Both techniques are described below. Note: The maximum length for a caption is 1000 characters. If you enter a caption longer than this, it is automatically truncated to 1000 characters. Note: HTML and javascript are not allowed unless explicitly enabled on the Membership - User Settings page in the Site admin area. Editing multiple captions at once When viewing multiple objects within a single album, captions can be edited by choosing Edit captions from the Actions menu. When the images are displayed with text boxes beneath them, edit the contents of the scroll bar to read the desired captions, and choose Save captions. Below is a screenshot of the Edit captions page. Gallery Server Pro 2.3 Administrator s Guide Page 75 of 238

76 Edit the caption for a single media object When viewing a single object on the media object view page, its caption can be edited by double clicking the existing caption beneath the object, as seen here: Gallery Server Pro 2.3 Administrator s Guide Page 76 of 238

77 A text box appears as shown below. Edit the text and choose Save changes. Gallery Server Pro 2.3 Administrator s Guide Page 77 of 238

78 Download media objects Users can download a media object one at a time or by using the built-in ZIP download functionality. Users are allowed to download only those objects they have permission to view. If watermarking is enabled, the downloaded images will contain a watermark. You can disable the download functionality on the Media Objects - General page in the Site admin area. While this prevents users from using the built-in functionality to download the media files, note that the fundamental nature of HTML means that if a user can view a media object, they have access to the file. The only way around this limitation is to use DRM, and it is not supported in Gallery Server Pro. When viewing a media object, there is a download icon in the toolbar above the object. Clicking this button downloads the file to your browser: Gallery Server Pro 2.3 Administrator s Guide Page 78 of 238

79 To download several items in a convenient ZIP archive, select the download ZIP archive button: Gallery Server Pro 2.3 Administrator s Guide Page 79 of 238

80 The Download media objects page appears: Gallery Server Pro 2.3 Administrator s Guide Page 80 of 238

81 Choose the items to download and select the Download button. The selected items will be packaged into a ZIP archive file and sent to you, where you can open or save the file: Gallery Server Pro 2.3 Administrator s Guide Page 81 of 238

82 A few important points about downloading objects: When downloading images, you can choose to download the thumbnail, compressed, or original images. Only users who have permission to view the original files are able to download them. When an album is selected, all of its contents, including child albums, are packaged into the ZIP archive. If this is done on an album with thousands of items, it may take a long time to process and use a lot of bandwidth to send the file to the user. When videos, audio files, and other non-images are selected, the original file is packaged into the ZIP archive. These media types do not have a compressed image and it doesn't really make sense to download the thumbnails for them. The Download media objects page can also be opened from two additional places in Gallery Server Pro. There is an item on the Actions menu: Gallery Server Pro 2.3 Administrator s Guide Page 82 of 238

83 And there is an icon in the album header area: Gallery Server Pro 2.3 Administrator s Guide Page 83 of 238

84 Delete objects Deleting a media object removes information about it from the data store and permanently deletes the media file from the hard drive. Also deleted is the thumbnail image and compressed image (if it exists). For external media objects such as YouTube videos, only the database record and locally stored thumbnail image is deleted. The object that is being referred to (such as the video stored at is not affected. You can delete several media objects at once using the Delete objects command, or delete a single media object using the Delete toolbar button. Both techniques are described below. Note: Deleting an object is permanent! There is no undo command, and once an object is deleted, there is no way to retrieve it. Delete multiple media objects To delete multiple objects in an album, navigate to the album containing the objects you wish to delete. Choose Delete Objects from the Actions menu and the following page appears. Gallery Server Pro 2.3 Administrator s Guide Page 84 of 238

85 Select one or more albums or media objects to delete by checking the associated checkbox. To quickly check or uncheck all objects within the album, use the checkbox next to Check/Uncheck all. Individual items can then be unchecked or checked as desired. When you are finished, click Delete selected objects. The objects you selected are permanently deleted. Note: If you delete an album, all of its contents are also deleted. Delete individual media object To delete a single media object, navigate to a page showing the media object in media object view. Choose the red X toolbar button above the media object. A popup window asks for confirmation that the object should be deleted, as shown below. Choose OK and the object is permanently deleted. Gallery Server Pro 2.3 Administrator s Guide Page 85 of 238

86 Note: If the current user does not have permission to delete the media object, the Delete toolbar button does not appear. Delete high-resolution version of images When you add images whose file size is large, Gallery Server Pro automatically creates a compressed version that is bandwidth-friendly and takes up less hard drive space. However, the original is not deleted and is still available through the Show/hide the original, high-resolution image toolbar button. You can save significant amounts of hard drive space by deleting the original high resolution versions of images, keeping only the compressed and thumbnail versions. Note: This function applies only to images. Navigate to the album containing the images for which you want to delete one or more high resolution images. Click the Delete hi-res images command in the Actions menu. The following screen appears. Gallery Server Pro 2.3 Administrator s Guide Page 86 of 238

87 The images and albums in the current album are displayed with associated checkboxes. If an image does not have a high resolution image, it will not have a checkbox and the message "No high-res image" appears on the thumbnail. Gallery Server Pro calculates and displays the hard drive space that would be saved if all items were selected. Check the checkboxes of the items for which you would like to delete the corresponding high resolution image. The thumbnail and compressed versions will not be deleted. Gallery Server Pro 2.3 Administrator s Guide Page 87 of 238

88 NOTE: The high resolution images will be permanently deleted from the web server! If these images are important, make sure you have a copy safely stored elsewhere. Move or copy media objects and albums Media objects and albums can be moved or copied to other albums. When a copy of a media object is made, a copy of the media file is saved to the destination album. The original file remains in the source album. When an album is copied, the directory and its contents are copied. Note: This section applies to moving or copying media objects within a single gallery. To transfer objects to another gallery (that is, another web application), back up the gallery and then restore it at the destination. See the Backup / Restore section for more information. An example: copying several objects Let s look at an example. Say we have an album called Photos that contains a couple child albums and several photos. We want to copy one of its albums and a photo to another album called My favorites. We start by navigating to the Photos album. Then we click Copy objects from the Actions menu. A screen like this will appear: Gallery Server Pro 2.3 Administrator s Guide Page 88 of 238

89 Select the items to copy. In this example, I am choosing to copy the Nature album and a photo of lily pads. When I click Choose these objects, a screen like this appears: Gallery Server Pro 2.3 Administrator s Guide Page 89 of 238

90 Note: Only those albums the user has permission to add objects to are shown. Since I want to move these objects into the My favorites album, I select that album. Then I click Copy objects. The photos are copied and I am redirected to the My favorites album where I can see that yes the items were indeed copied. An example: moving a single object As you browse your media objects, imagine you come across one that you want to move to your My favorites album. The page might look like this: Gallery Server Pro 2.3 Administrator s Guide Page 90 of 238

91 Move object button Copy object button Click the toolbar button labeled Transfer this object to another album. The following screen appears. Gallery Server Pro 2.3 Administrator s Guide Page 91 of 238

92 Select the My favorites album, and click Move object. The photo will be moved to the album. Note: To copy the object instead of move it, click the toolbar button labeled Copy this object to another album. Rearrange objects To change the order in which Gallery Server Pro displays objects on a web page, choose Rearrange objects from the Actions menu. The media objects in the current album are displayed as shown below. Gallery Server Pro 2.3 Administrator s Guide Page 92 of 238

93 Drag the media object to the desired location. Note: The Rearrange objects command on the Actions menu is only enabled when the logged on user has Edit album permission for the current album. To change the sequence of an object, drag it to the desired location. A rectangular area near the top and bottom of the screen scrolls the window up or down when the mouse hovers over it. Use these areas to drag objects above or below the visible portion of the window. When the user clicks Save changes, the objects will be displayed in album view, again in the right-to-left, then top-to-bottom format. * Behind the Scenes * Rearranging objects modifies the Sequence field in the database table gs_mediaobject (for media objects) and gs_album (for albums). Gallery Server Pro 2.3 Administrator s Guide Page 93 of 238

94 Rotate objects Images can be rotated in intervals of 90 degrees in any direction. You can rotate all the images in an entire album at once, or rotate just a single image. Both techniques are described below. Note: Only images can be rotated. Gallery Server Pro does not support rotating videos or other types of objects. Rotate more than one image To rotate more than one image in the current album, choose Rotate images from the Actions menu. The thumbnails in the current album are displayed with selectable arrow boxes on each of the images four sides, as below. For each image that needs to be rotated, click on the arrow on the side that should be on top. Click Rotate images and thumbnail image, original image, and compressed image (if it exists) for each image you selected will all be rotated as specified. Note: After the images are rotated, your browser may display the previous image from its cache rather than the newly rotated image. To get the latest version, refresh the page in your browser (pressing F5 or CTRL-F5 works in most browsers). Note: Rotating is the only function in Gallery Server Pro that modifies the original image file. In some cases, repeatedly rotating an image will degrade the original, so use this function with caution. Gallery Server Pro 2.3 Administrator s Guide Page 94 of 238

95 Rotating a single image To rotate a single image from the media object view page, select the Rotate this image toolbar button from the toolbar above the image, as shown below. A selectable arrow box is added to all four sides of the image, as below. Gallery Server Pro 2.3 Administrator s Guide Page 95 of 238

96 Click on the arrow box on the side that should be on top. Click Rotate image and the image will be rotated as requested. Gallery Server Pro 2.3 Administrator s Guide Page 96 of 238

97 Note: After the image is rotated, your browser may display the previous image from its cache rather than the newly rotated image. To get the latest version, refresh the page in your browser (pressing F5 or CTRL-F5 works in most browsers). Watermarking The watermark feature is a powerful tool to help protect images from unwanted duplication or to communicate the source of the image. Watermarks are rendered dynamically on the image when it is requested by the browser. The original image files are not modified, and no files are stored on the web server with watermarks applied to them. If a user downloads an image using the Download toolbar button above an image, the downloaded image has the same watermark as the image rendered in the browser. Below is an example of a photo with an image and text watermark. Gallery Server Pro supports two kinds of watermarks: A custom image that is applied to each image. For example, the Gallery Server Pro logo in the image above. Custom text that is applied to each image. For example, the copyright message in the image above. You can configure one or both of these watermarking techniques. Furthermore, you can control the following attributes of each watermark: The source of the watermark image. Use your own image file. If you specify a.gif or.png with transparent pixels, those pixels will remain transparent when rendered on the image surface. Gallery Server Pro 2.3 Administrator s Guide Page 97 of 238

98 The location to apply the watermark on the image. Choose from nine locations, such as TopLeft, MiddleCenter, etc. The size of the watermark. The size can be relative to the size of the image, such as 50% of the width of the image. For a text watermark, you can optionally specify the font size. The opacity, from transparent to completely opaque. For text watermarks, specify the font name and size. Note: The watermark image and/or text applies to the entire application. It is not possible to specify different watermarks for different albums or media objects. Although you cannot specify different watermarks within the application, you can specify that certain users do not get the watermark. See the section Configure role-based watermarking below. Enable watermarking Watermark functionality is configured on the Media Objects - Images page in the Site admin area. Refer to the Media Objects Images section for detailed information on the various configuration options. Configuring role-based watermarking Certain users can be configured to not receive the watermark. This is useful for, say, professional photographers who want to allow users to browse all photos in the gallery. A watermark can be applied to users by default, but paying customers can be placed in a role where watermarks are not rendered on the images. This can be specified at the album level so that certain albums render watermarks for a given user while others do not. To configure Gallery Server Pro so that all users receive a watermark except for a certain user account, follow these steps. 1. Enable the watermark functionality. This is done on the Media Objects - Images page in the Site admin area. 2. Configure a role with Do not show watermark on image permission for at least one album. 3. Add a user to this role. (Make sure the user has view access to the desired media objects. Add view permission if necessary to the role you configured in step 2.) Note: Browsers often cache images, so you may need to refresh the browser in order to see the non-watermarked version of an image that previously had a watermark. Gallery Server Pro 2.3 Administrator s Guide Page 98 of 238

99 Examples of watermarks Below is a text watermark with the letters TIS set to 100% of the image width. Opacity is set to 20%. (TIS stands for Tech Info Systems.) Here is an example where a custom image has been specified to be 50% of the width of the photo and located in the top left. Opacity is set to 40%. Gallery Server Pro 2.3 Administrator s Guide Page 99 of 238

100 Image metadata When images are added to Gallery Server Pro, any metadata embedded in the file is extracted and saved to the data store. Gallery Server Pro can extract data in any of the following formats: EXIF, XMP, text, IFD, and IPTC. Viewing image metadata When viewing an image, click the View information about this media object toolbar button that appears above the image, as shown below. A popup window shows all the metadata that has been extracted for an image. This is a read-only list and cannot be edited. Toggles image metadata Gallery Server Pro stores each user s preference for whether or not the Image metadata popup is shown. This preference is persisted across logon sessions. Bonus:.NET 3.0 metadata extraction Gallery Server Pro requires.net Framework 2.0, and most metadata can be extracted using the functionality contained within it. However,.NET Framework 3.0 and higher allows important new metadata items to be extracted. The most important of these are titles and keywords. Gallery Server Pro 2.3 Administrator s Guide Page 100 of 238

101 For example, one can use Windows Photo Gallery to add titles and keywords to images, and Gallery Server Pro will extract them, where they are then available for viewing and for the search function. If Gallery Server Pro detects that.net Framework 3.0 or higher is installed on the web server, and if the application is running under Full Trust, it automatically takes advantage of this additional functionality. Searching The search functionality in Gallery Server Pro allows one to find all objects that contain the search criteria. The following properties are included in the search: Album title and summary Media object caption and file name Media object metadata, such as camera model, shutter speed, title, etc. An object is considered a match if all search words match an album or media object. For example, if one searches for desert mountain, only those albums or media objects that contain both desert and mountain are returned. If the search words are contained in quotation marks, such as desert mountain, then the phrase must match exactly. The contents of documents such as PDF files are not searched. Only those objects for which the current user has authorization to view are returned in the search results. Since the search function includes the metadata extracted from images, you can perform some pretty powerful searches. For example, to see all your photos that were shot at -0.5 step compensation, search for -0.5 step. You may have to adjust the text depending on your camera. To begin a search, click the search icon in the top right of the page. Enter the search term and click the Search button. Note: If the search icon is not visible, it may have been disabled. The configuration setting is on the Site Settings - General page in the Site admin area. Gallery Server Pro 2.3 Administrator s Guide Page 101 of 238

102 A page with the search results appears. Click the thumbnail to view the item. Gallery Server Pro 2.3 Administrator s Guide Page 102 of 238

103 Rendering media objects in the browser Note: This section contains advanced information on customizing how Gallery Server Pro generates the HTML for media objects. You should be comfortable with HTML before attempting to modify the generated HTML. Browsers, by themselves, cannot play video, audio, or render many kinds of documents like Adobe PDF or Microsoft Word files. These types of objects require plug-ins which may or may not be installed in your users' browsers. Note: Support is slowly growing for native audio and video support through the user of the HTML 5 video and audio elements. For example, they are now supported in FIrefox 3.5. We will watch these developments and make sure Gallery Server Pro takes full advantage of native browser support when possible. Gallery Server Pro is flexible so that administrators can customize the HTML output rendered by Gallery Server. You, as the web site administrator, may feel comfortable having a dependence on a particular plug-in, such as Silverlight or Flash, while others may not. Also, some users might prefer that multimedia files are rendered with <object> tags in order to pass XHTML validation, while others might prefer <embed> Gallery Server Pro 2.3 Administrator s Guide Page 103 of 238

104 for maximum backward compatibility. Lastly, different browsers require different syntax, and new versions of browsers are frequently released, potentially breaking something that works today. Gallery Server Pro uses a combination of automatic browser sniffing and HTML templates stored in a configuration file. The configuration file galleryserverpro.config (stored in the gs/config directory) contains HTML templates for each major type of media object. For example, rendering the HTML for an image is pretty straightforward. Here is the relevant entry in galleryserverpro.config: <galleryobject> <mediaobjects> <mediaobject mimetype="image/*"> <browsers> <browser id="default" htmloutput="<div class="gsp_floatcontainer"><div class="op1"><div class="op2"><div class="sb"><div class="ib"><img id="mo_img" src="{mediaobjecturl}" class="{cssclass}" alt="{titlenohtml}" title="{titlenohtml}" style="height:{height}px;width:{width}px;" /></div></div></div></div></div>" /> </browsers> </mediaobject>... </mediaobjects> </galleryobject> The mediaobject tag specifies that the inner tags apply to the image/* MIME type. The asterisk (*) means that it will match all images, such as image/jpg, image/jpeg, and image/gif. Now, let s take a closer look at what is in the htmloutput attribute of the browser tag: <div class="gsp_floatcontainer"><div class="op1"><div class="op2"><div class="sb"><div class="ib"><img id="mo_img" src="{mediaobjecturl}" class="{cssclass}" alt="{titlenohtml}" title="{titlenohtml}" style="height:{height}px;width:{width}px;" /></div></div></div></div></div> If you convert the escaped characters to their actual characters, it is more readable: <div class="gsp_floatcontainer"> <div class="op1"> <div class="op2"> <div class="sb"> <div class="ib"> <img id="mo_img" src="{mediaobjecturl}" class="{cssclass}" alt="{titlenohtml}" title="{titlenohtml}" style="height:{height}px;width:{width}px;" /> Gallery Server Pro 2.3 Administrator s Guide Page 104 of 238

105 </div> </div> </div> </div> </div> Now that is starting to look a little more understandable, isn t it? The five <div> tags that wrap the <img> tag are there to support the drop shadow and border that appears around each image. But what is that stuff in the brackets, like {MediaObjectUrl}? Those are placeholders that are replaced with dynamically generated content at runtime. For example, {Height} is replaced with the height of the image. A full list and descriptions of these placeholders can be found below. When Gallery Server Pro uses the above template to render an image to the browser, it ends up looking something like this: <div class="gsp_floatcontainer"> <div class="op1"> <div class="op2"> <div class="sb"> <div class="ib"> <img src="/gs/handler/getmediaobject.ashx?p%2fcac3zs" alt="grand Canyon" style="width:86px;height:115px;" /> </div> </div> </div> </div> </div> If desired, one can tweak this template to change how <img> tags are rendered. For example, if you wanted to use the width and height attributes instead of a style, update the config file like this: <browser id="default" htmloutput="<div class="gsp_floatcontainer"><div class="op1"><div class="op2"><div class="sb"><div class="ib"><img src="{mediaobjecturl}" class="{cssclass}" alt="{titlenohtml}" title="{titlenohtml}" width="{width}" height="{height}" /></div></div></div></div> </div>" /> Note: If you are a little confused about how we can specify image/* as the MIME type when everyone knows that browsers can t render ALL the different image formats that exist, read on. Gallery Server Pro is hard wired to treat images a bit different than other media types. By default, Gallery Server Pro assumes that browsers can natively render images of these types: JPG, JPEG, GIF, and PNG. If a user uploads another type, such as TIFF, Gallery Server Pro will attempt to generate a JPEG version of the image and send that to the browser. If Gallery Server Pro cannot create a JPEG version from an image or the user is requesting the original TIFF image (by clicking the view original link), the user is shown a message saying the image cannot be rendered and suggests the user download the image using the Gallery Server Pro 2.3 Administrator s Guide Page 105 of 238

106 download link. Because of this logic, we can assume that only JPG, JPEG, GIF, and PNG images are sent to the browser in <img> tags, and it is therefore safe to specify the MIME type of image/* as shown above. The list of native image formats is stored in the configuration setting imagetypesstandardbrowserscandisplay in galleryserverpro.config. Image rendering is pretty straight forward. For video, let s look at the relevant section of galleryserverpro.config: <mediaobject mimetype="video/*"> <browsers> <browser id="default" htmloutput="<object type="{mimetype}" data="{mediaobjecturl}" style="width:{width}px;height:{height}px;" > <param name="src" value="{mediaobjecturl}" /> <param name="autostart" value="{autostartmediaobjectint}" /></object>" /> <browser id="ie" htmloutput="<object type="{mimetype}" data="{mediaobjecturl}" style="width:{width}px;height:{height}px;"> <param name="src" value="{mediaobjecturl}" /> <param name="autostart" value="{autostartmediaobjecttext}" /></object>" /> </browsers> </mediaobject> <mediaobject mimetype="video/quicktime"> <browsers> <browser id="default" htmloutput="<object type="{mimetype}" data="{mediaobjecturl}" style="width:{width}px;height:{height}px;"> <param name="autoplay" value="{autostartmediaobjecttext}" /> <param name="controller" value="true" /> <param name="pluginurl" value=" /></object>" /> <browser id="ie" htmloutput="<object classid="clsid:02bf25d5-8c17-4b23-bc80-d3488abddc6b" codebase=" style="width:{width}px;height:{height}px;"> <param name="src" value="{mediaobjecturl}" /> <param name="autoplay" value="{autostartmediaobjecttext}" /> <param name="controller" value="true" /> <param name="pluginspage" value=" /></object>" /> </browsers> </mediaobject> Gallery Server Pro 2.3 Administrator s Guide Page 106 of 238

107 Notice there are two mediaobject elements one that specifies the MIME type video/* and the other specifies video/quicktime. The HTML template under video/* handles all generic cases of rendering video. The second element handles the more specific case of QuickTime video, since that type requires different HTML. One could add additional mediaobject elements if, for example, AVI files required custom HTML. Look closer at the browser entries inside the video/* template: <browser id="default" htmloutput="<object type="{mimetype}" data="{mediaobjecturl}" style="width:{width}px;height:{height}px;" > <param name="src" value="{mediaobjecturl}" /> <param name="autostart" value="{autostartmediaobjectint}" /></object>" /> <browser id="ie" htmloutput="<object type="{mimetype}" data="{mediaobjecturl}" style="width:{width}px;height:{height}px;"> <param name="src" value="{mediaobjecturl}" /> <param name="autostart" value="{autostartmediaobjecttext}" /></object>" /> There are two browser elements here one with ID default and the other ie. The id attribute uniquely identifies the browser element, which must match the internal identifier of a browser as specified in the.net Framework's browser definition file. See for a hierarchical list of ids recognized by.net Framework 2.0. These two <browser> elements are specifying one HTML template for the default browser, and another for IE. If you look at the HTML templates closely, you will notice they are identical except one specifies AutoStartMediaObjectInt and the other AutoStartMediaObjectText. That s because IE requires the autostart parameter to be text, like true or false, while other browsers require a numerical value (1 for true, 0 for false). If, for example, you discovered that the Safari browser wasn t working quite right because of HTML incompatibilities, you could add a browser element with id= safari. Then add the HTML template using the syntax required by Safari, and you are finished. Gallery Server Pro and ASP.NET automatically detects the browser type and sends the correct HTML. The following is a list of all replacement parameters supported within the htmloutput attribute. Name {CssClass} {MimeType} Description A valid cascading style sheet class. The business logic determines which classes, if any, are inserted into this parameter. Example value: "msgsuccess", "msgsuccess indent" The mime type of the media object. The mime type is determined from the file extension of the media object. The Gallery Server Pro 2.3 Administrator s Guide Page 107 of 238

108 mapping between mime types and file extensions is in the mimetypes section of galleryserverpro.config. Example value: "video/quicktime", "image/jpeg" {MediaObjectUrl} {MediaObjectAbsoluteUrlNoHandler} The url to the media object. Example value: "handler/getmediaobject.ashx?moid=34&aid=8&mo=c%3a%5cg s%5cmypics%5cbirthday.jpeg&mtc=1&dt=1&isp=false" An url that points directly to the media object and bypasses the HTTP handler. Example value: /gallery/videos/birthdayvideo.wmv. The handler provides security checking and watermarking, so only use this parameter when necessary. For example, perhaps a video plug-in does not work unless the file is directly referenced. IMPORTANT: This parameter requires that the media objects directory be within the Gallery Server Pro web application directory. By default, media objects are stored in the mediaobjects directory within the application, so this requirement is satisfied unless you change it. If this requirement is not met, use the {MediaObjectRelativeUrlNoHandler} parameter. {MediaObjectRelativeUrlNoHandler} Provides an url that is relative to the media objects directory and which points directly to the media object. Example value: /videos/birthdayvideo.wmv). This parameter bypasses the HTTP handler that normally streams media objects to the browser. The handler provides security checking and watermarking, so only use this parameter when necessary. For example, perhaps a video plug-in does not work unless the file is directly referenced. Typically this parameter is used instead of {MediaObjectAbsoluteUrlNoHandler} when the media objects directory is outside of the web application. If the user wants to allow direct access to the media objects using this parameter, she must first configure the media objects directory as a virtual directory in IIS. Then the path to this virtual directory must be manually entered into one or more HTML templates in galleryserverpro.config, so that it prepends the relative url returned from this method. Example: If the media objects directory has been set to D:\media and a virtual directory named gallery has been configured in IIS that is accessible via then you can configure the HTML template like this: Gallery Server Pro 2.3 Administrator s Guide Page 108 of 238

109 htmloutput="<a href=" NoHandler}">Click to open</a>" {Width} The width, in pixels, of the media object. Example value: 640, 480 {Height} The height, in pixels, of the media object. Example value: 640, 480 {Title} {TitleNoHtml} {AutoStartMediaObjectText} {AutoStartMediaObjectInt} {GalleryPath} The title of the media object. May include HTML tags. Example value: Kayla 'sledding' down the <a href=" The title of the media object with HTML tags removed and apostrophes and quotation marks are replaced with " and &apos;. Example value: "Kayla sledding down the hill" Indicates whether to automatically start a video or audio object on the client. This value comes from the galleryserverpro/core/autostartmediaobject configuration element. Rendered as the text "true" or "false". Indicates whether to automatically start a video or audio object on the client. This value comes from the galleryserverpro/core/autostartmediaobject configuration element. Rendered as the value "1" (true) or "0" (false). The path, relative to the web site root, to the directory containing the Gallery Server Pro support files. Example: If GSP is installed at C:\inetpub\wwwroot\dev\gallery, where C:\inetpub\wwwroot\ is the parent web site, and the gallery support files are in the gsp directory, this property returns /dev/gallery/gsp. Used when referring to resources such as the.xaml skins for the Silverlight media player. {HostUrl} The URI scheme, DNS host name or IP address, and port number for the current application. Examples: Used for some plug-ins such as the DIVX Web Player that require a fully qualified path to the media object. Gallery Server Pro 2.3 Administrator s Guide Page 109 of 238

110 Reference for galleryobject element in galleryserverpro.config The following table contains definitions for each of the elements within the galleryobject element. Element name galleryobject mediaobjects mediaobject Description Contains a collection of mediaobject elements. Valid attributes: none. Valid child elements: mediaobjects. This is a collection of mediaobject elements. Valid attributes: none. Valid child elements: mediaobject. This is an element that contains information about how Gallery Server Pro should handle specific types of media objects. Each mediaobject is uniquely identified by the mimetype attribute. If a mimetype is specified more than once within the mediaobjects collection, only the first element is used (subsequent ones are ignored). An asterisk (*) can be used to represent all subtypes within a type (e.g. "video/*" matches all video objects). However, if another mediaobject element contains a more specific value, such as "video/quicktime", that element will override "video/*". The mimetype attribute must match one of the type attributes specified in the mimetype element (unless the mimetype attribute has an asterisk). Valid attributes: mimetype. Valid child elements: browsers. browsers browser This is a collection of browser elements. The collection must contain one browser element with id="default". It can optionally contain additional browser elements. Valid attributes: none. Valid child elements: browser. This is an element that contains information about how the media object should be rendered when the client is using this browser. It is uniquely identified by the id attribute, which must match the internal identifier of a browser as specified in the.net Framework's browser definition file. See for a hierarchical list of ids recognized by.net Framework 2.0. If an id is specified more than once within the browsers collection, only the first element is used (subsequent ones are ignored). The htmloutput attribute contains the HTML to be rendered to the client when the client is using this particular browser and is viewing the type of media object contained in the parent element. The scriptoutput attribute may contain javascript to be evaluated by the browser. For example, Silverlight requires a little javascript to initialize the plug-in. Valid attributes: id, htmloutput, scriptoutput. Valid child elements: none. If the client's browser matches multiple browser elements (e.g. "ie" and "default"), the most specific browser element is preferred (in this example "ie"). Thus you can specify a browser element with id="default" containing the default HTML for a Gallery Server Pro 2.3 Administrator s Guide Page 110 of 238

111 particular type of media object. Create additional browser elements to handle individual browsers as desired. Microsoft Silverlight Starting with version 2.1,.wmv,.wma,. mp3,.asf, and.asx files are rendered using the Microsoft Silverlight 1.0 plug-in (or later, if installed). If the user does not have Silverlight installed, a graphic will appear in place of the media object that says "Get Silverlight". When clicked, the user is stepped through the process of installing the plug-in. Using Silverlight rather than just sending a generic <object > tag to the browser offers better performance and a more predictable experience for your end users. Video and audio files start playing almost immediately rather than after downloading the entire file. Those users who do not have the Silverlight plug-in receive gentle hand holding for installing it. To accommodate the requirements of Silverlight, a new attribute named scriptoutput was added to the <browser > element in galleryserverpro.config. It is similar to htmloutput, except that it specifies javascript that must be executed in addition to the HTML. For example, the scriptoutput for the video/x-ms-wmv MIME type looks like this (after HTML decoding): Sys.UI.Silverlight.Control.createObject('mp1p', '<object type="application/x-silverlight" data="data:application/x-silverlight," id="mp1" style="height:{height}px;width:{width}px;"><param name="windowless" value="true" /><a href=" src=" alt="get Microsoft Silverlight" style="border-width:0;" /></a></object>');sys.application.initialize();sys.application.add_init(function() { $create(sys.ui.silverlight.mediaplayer, {"mediasource":"{mediaobjecturl}","scalemode":1,"source":"{gallerypath}/skins/mediaplayer/professional. xaml","autoplay":{autostartmediaobjecttext} }, null, null, $get("mp1p")); });Array.add(_mediaObjectsToDispose, "mp1"); There are several skins available for the Silverlight player. By default, audio files use the AudioGray.xaml skin and video files use Professional.xaml. You will find more skins in the gs\skins directory. Update the template as desired to change the media player skin. 6. User Management and Security Overview Gallery Server Pro uses a system of anonymous browsing, user accounts, and roles to provide a flexible security model that should satisfy most security needs. There is no limit to the number of users and roles. Gallery Server Pro 2.3 Administrator s Guide Page 111 of 238

112 By default, anonymous users - that is, those who are not logged on - can browse the albums and media objects, but they cannot perform tasks that modify data, such as adding albums, rotating an image, site administration, etc To perform a task, a user must belong to a role that has the appropriate permission. Roles can be configured with any of several permissions. Here we see a role named Read Only All Albums that provides viewing permission to all albums: A user in the Read Only All Albums role can view any album and media object in the gallery, but cannot perform any task. The power and flexibility of Gallery Server Pro becomes apparent when you add users to more than one role. For example, a separate role can be created that provides edit permission to a single album. A user belonging to both of these roles can view all objects in the gallery but can only edit the one album. Gallery Server Pro uses the ASP.NET Membership and Role provider model. By default, the users and roles are stored in the same database as the Gallery Server Pro data. You can optionally configure Gallery Server Pro to connect to an existing store of users. For example, you may want to integrate Gallery Server Gallery Server Pro 2.3 Administrator s Guide Page 112 of 238

113 Pro with your DotNetNuke users or you may want to use the existing accounts in Active Directory. Read more about configuring the membership provider in the Membership Configuration section. Require everyone to log on The default configuration allows users to anonymously browse the gallery, but they are prevented from any action that modifies the media objects. To require all users to log on, even to browse, disable the anonymous browsing feature on the Site Settings - General page in the Site admin area. As the screen shot shows, you can also prevent anonymous users from viewing the high resolution version of your photos. This can be helpful when you want to restrict access to your original photos. A special role permission named View original, high-res images can be used to give logged-on users access to these images. Remember - a user that doesn't belong to a role has no permission to view or edit objects. Be sure to include each user in at least one role to provide the desired level of access. Note: Gallery Server Pro cannot be configured to give anonymous users edit permission. Any action other than viewing requires that the user log in. Users Individuals access Gallery Server Pro anonymously or by logging on with user accounts. User accounts have access to albums and administrative tasks based on the roles to which the user belongs. Users are created and maintained on the Manage Users page in the Site administration console. Gallery Server Pro 2.3 Administrator s Guide Page 113 of 238

114 If you integrate Gallery Server Pro with an existing membership system, you can manage your users with your original system or with the user management function in Gallery Server Pro. Create a user Create a user by clicking Add new user on the Manage Users page in the Site admin area. The Create New User wizard appears as shown below. Gallery Server Pro 2.3 Administrator s Guide Page 114 of 238

115 Enter a username and password for the user. An address can be used for the username if desired. When you leave the username field, an AJAX callback validates the username and reports whether it is already in use. An address is optional but is useful for allowing users to retrieve forgotten passwords. Clicking the Next button displays the second page where one or more roles can be assigned to the user. Gallery Server Pro 2.3 Administrator s Guide Page 115 of 238

116 Click Create User. A confirmation message appears in the pop-up box. Close the pop-up box and the Manage Users page will be updated with the new user you just created. Edit a user Click the Edit link next to a user to open the Edit user dialog. Gallery Server Pro 2.3 Administrator s Guide Page 116 of 238

117 The General tab of the Edit user dialog allows a description and address for the user to be updated. You can disable a user account by clicking No on the Is approved setting. Disabled users cannot log on to access. You can also enable or disable the user's personal album. Note that this option does not appear when user albums are disabled. WARNING: Disabling a user's album causes the album and its contents to be deleted! The Roles tab allows one to configure the roles to which the user belongs. Gallery Server Pro 2.3 Administrator s Guide Page 117 of 238

118 The Password tab provides the ability to change the user s password. Note: To reset or change a password, select the desired option and then click the Update password button. Gallery Server Pro 2.3 Administrator s Guide Page 118 of 238

119 Roles Permissions in Gallery Server Pro are applied to roles rather than users. Users are allowed to carry out tasks when they are a member of one or more roles that provide the appropriate permission. By combining users and roles in different configurations, you can achieve a highly configurable gallery. Gallery Server Pro will give a user permission to perform an activity if any of the user's roles contain the requested permission, even if the others do not. For example, consider a user who belongs to three roles. Two of the roles do not have Delete album permission but the third one does. In this case, the user has permission to delete the album that is specified in the role with the Delete album permission. Below is a list of the permissions that can be applied to a role. Role permission Administer site (all Description Provides unrestricted access to all functionality in Gallery Server Pro. This is the Gallery Server Pro 2.3 Administrator s Guide Page 119 of 238

120 albums) View albums / objects View original, hi-res images Add albums only permission that applies to all albums in the gallery and cannot be selectively applied to individual albums. Provides a read-only view of photos, videos and other media objects. Note that it does not give access to the original, high resolution versions of images (if they exist). Provides read only access to the original, high resolution versions of images, if they exist. Allows a user to add an album in any of three ways: (a) The user can create a new album using the Create album menu item, (b) copy an album from another album, or (c) move an album from another album. Note 1: Adding an album by moving it from another location is allowed only if the user also has delete permission for the source album. Note 2: When moving or copying an album, users must have Add albums permission on the destination album. Note 2: When a user moves or copies an album, any media objects within the album are also transferred regardless of whether the user has Add media objects permission on the destination album. Add media objects Gives a user the ability to add media objects such as images, videos, audio files, and documents in any of three ways. The user can (a) add a new media object using the Add objects menu item, (b) copy a media object from another album, or (c) move a media object from another album. Note 1: Adding a media object by moving it from another album is allowed only if the user also has Delete media object permission for the album from which the media object is being moved. Note 2: A user must have both Add media objects permission and Add albums permission in order to add a ZIP file that contains one or more directories, since Gallery Server Pro converts the directories to albums. Note 3: Only those media objects that are enabled on the Media Object Types page can be added. Note 4: To add media objects through synchronizing, the Synchronize permission is also needed. Edit album Allows a user to edit album information, such as the title; summary; begin and end dates; assigned thumbnail; and sequence of media objects and child albums. Gallery Server Pro 2.3 Administrator s Guide Page 120 of 238

121 Edit media object Delete child albums Allows a user to edit any media object's title. For images, it also allows rotation as well as deletion of the original, high resolution image (if it exists). Allows the deletion of a child album in one of two ways: the user can either delete an album outright, or move an album to another album. Note: When moving an album, users must have this permission on the source album, as moving can be thought of as deleting an album from one location and adding it to another. (The user must also have permission to add an album to the destination album.) Delete media object Allows the deletion of a media object in one of two ways. The user can either delete a media object outright or move a media object to another album. Note: When moving a media object, users must have this permission on the source album, as moving can be thought of as deleting an object from one location and adding it to another. (The user must also have permission to add a media object to the destination album.) Synchronize Provides the ability to synchronize the media object files and directories on the web server's hard drive with the records in the data store. Note: If a user has the ability to edit the media objects directory outside the security boundary of Gallery Server Pro (such as using a utility like Windows Explorer), and the user also has Synchronize permission here, she effectively has the ability to add and delete albums and media objects, even if those permissions are not included in a user's role. Do not show watermark on image This permission causes images to be shown to the user in their original form, without a watermark applied. If a user belongs to more than one role with conflicting values, then watermarks are not shown. This permission is ignored if the watermark functionality is disabled for the gallery. Refer to the section Watermarking for more information. If you integrate Gallery Server Pro with an existing role provider, you can use the original role management function to manage the roles. However, you must use the role management function in Gallery Server Pro to execute tasks that are specific to Gallery Server Pro, such as specifying the permissions and albums each role applies to. Creating, editing, and deleting roles Create a role by clicking Add new role on the Manage Roles page in the Site admin area. Gallery Server Pro 2.3 Administrator s Guide Page 121 of 238

122 The following popup window appears. Gallery Server Pro 2.3 Administrator s Guide Page 122 of 238

123 Here we are creating a role named Read Only All Albums giving it view permission to all albums. Click Save changes to create the role. Note: Users are assigned to a role on the Manage Users page. Edit a role by clicking the Edit button next to a role. Similarly, a role can be deleted by clicking the Delete button. Understanding how roles apply to the album hierarchy Role permissions automatically propagate to all child albums of the selected album. The top level selected album(s) is considered to have explicitly assigned role permissions. Child albums are considered to have inherited role permissions because they inherit the permission from a parent album. Since permissions apply to all child albums of a selected album, notice that all child albums become selected when you click an album, and you cannot de-select individual child albums. Gallery Server Pro 2.3 Administrator s Guide Page 123 of 238

124 Role behavior for new, moved or copied albums Role permissions are assigned to the highest album you select, and child albums always inherit those permissions. If a child album is added, moved, or copied, it automatically inherits the permissions of its new parent album, and the previous permissions no longer apply. When you move or copy an album that has a role explicitly assigned to it, that role stays with the album. Self Registration Gallery Server Pro supports anonymous users creating accounts in the gallery. There are several configuration options available such as requiring a valid address, setting the default security access and more. When self-registration is combined with user albums, a maintenance-free community gallery is possible where visitors to your site each have their own gallery with no involvement required by administrators. Setting up self-registration The User Settings page in the Site admin area contains configuration options: Allow visitors to create accounts This enables the self-registration feature. When checked, a create account link appears in the top right of each page that takes the user to a registration wizard: Gallery Server Pro 2.3 Administrator s Guide Page 124 of 238

125 Registration wizard When disabled, the Create account link is not shown and the only way to create a user is on the Manage Users page in the Site admin area. Require validation to activate account This option sends an to the user with a validation link that must be clicked before the user can log on. Enable this feature to guarantee a valid address for each account. The sent to the user looks similar to this: Welcome to the gallery. Before you can use your new account you must activate it - this ensures the address you used is valid and belongs to you. To activate your account, click the link below or copy and paste it into your browser's location bar: Gallery Server Pro 2.3 Administrator s Guide Page 125 of 238

126 Once you successfully activated your account, you can throw away this . Thanks for joining. -- Gallery Server Pro Administrator The text of this can be changed by editing the appropriate text file in the directory \gs\templates\ of the web application. Note: Be sure functionality is configured. This is done on the page in the Site admin area. Note: When both validation and administrator approval are enabled, the user is first sent the verification . After the user clicks the verification link, the administrator is sent an that the user is waiting for approval. Require administrator approval to activate account When enabled, newly created users cannot log on until an administrator approves the account. To receive notification when an account needs approval, specify one or more administrators in the User accounts section on the User Settings page, as seen here: To receive an , the administrator must have a valid address and functionality must be configured. Only administrators have permission to approve users, so in most cases it makes sense to only choose from the administrators in a gallery. However, one can check the option to show all users if you want to notify a non-administrator that a user is created. Gallery Server Pro 2.3 Administrator s Guide Page 126 of 238

127 Use address for user name The default is to allow a user to specify both a username and address, but you may want to require everyone to use an address as their account name. This can simplify things for users and administrators: Users need only remember one piece of information rather than two, and remembering their address is often easier than remembering a username, especially if their first choice in usernames is already taken. Users can have their password ed to them. This is not possible when an address is optional. When this option is enabled, the registration screen no longer requests a username: An address that conforms to the expected format must be entered. For example, if a user enters "Billy Joe", the message Not a valid appears. But the address "fake@fake.com" is allowed. To force users to enter a valid address, enable the validation option discussed above. Gallery Server Pro 2.3 Administrator s Guide Page 127 of 238

128 Default roles Visitors who register their own accounts can be added to one or more roles when the account is created. For example, you might add them to a role that removes the watermark, gives them read-only access to the entire site, or permission to upload items to a particular album. Note: If user albums are enabled, the user is automatically given full permission to his or her personal album, even if no roles are specified here. This setting applies ONLY to self-registered users. That is, when an administrator manually creates an account, these roles are not assigned to the user. To assign one or more roles to new users, choose them from the drop down list: In this screen shot, new users are added to two roles - No Watermark (has the "Do not show watermark" permission) and Read Only All Albums (gives view permission to the entire gallery). The drop down box initially hides roles that were automatically created by the system for user albums and album owners. Typically you will never need to interact with them, but if you want to take a peek select the checkbox Show roles that support the album ownership and user album features. 7. Site Administration Overview Site settings can be accessed by choosing Site admin from the Actions menu. A new menu appears on the left. Notice that sections of this menu can be collapsed by clicking on the tiny arrows. We ll review each section from top to bottom. Gallery Server Pro 2.3 Administrator s Guide Page 128 of 238

129 Site Settings General The first section is for General Site settings. Select it and the page should look as below. Gallery Server Pro 2.3 Administrator s Guide Page 129 of 238

130 Product key Product keys are free and easily obtained from the Product Key Wizard at Enter your product key in the text box and click the Enter product key button. A message will appear indicating whether or not the key is valid. If it is, all functionality is enabled and you will not be asked for a key again. If Gallery Server Pro does not have permission to update the configuration file galleryserverpro.config, you must update it manually. Open the file, which can be found in the gs\config directory of the web application, in any text editor (such as Notepad) and edit the productkey attribute to contain the product key. Save the file. In some cases your changes won't take effect until you recycle the application pool or enter iisreset at a Start-Run dialog box. System settings The table below describes the system setting properties. Gallery Server Pro 2.3 Administrator s Guide Page 130 of 238

131 Gallery title Gallery title URL Allow anonymous browsing Allow anonymous browsing of high resolution images The header text that appears at the top of the gallery. This can be blank. The URL the user will be directed to when they click the header text. This setting is optional if not present, no link will be rendered. This setting is ignored if the Gallery title field is empty. Indicates whether users can browse the gallery without logging in. When unchecked, users must log in with a valid account to view media objects. Indicates whether users can view the original, high resolution images without logging in. When unchecked, users must log in with a valid account to view media objects, and that account must belong to a role that allows viewing the high resolution images. This setting is ignored when anonymous browsing is disabled. Show login/logout buttons When checked, login and logout controls are displayed in the top right corner of every page. You may want to disable this feature when the audience is primarily anonymous web users without user accounts or when you provide your own authentication system. Administrators can always log in by navigating directly to the login page (use the query string g=login; ex: default.aspx?g=login). Web Developers: You can override this system setting at the user control level with the ShowLogin property of the Gallery user control in the.aspx page. Show search link Indicates whether to display the search link in the top right corner of every page. Web Developers: You can override this system setting at the user control level with the ShowSearch property of the Gallery user control in the.aspx page. Gallery ID The value that uniquely identifies the gallery for this website. Each web application is associated with a single gallery. Read the section Working with Galleries for more information. Error management The table below describes the error management properties. detailed reports when web site error occurs Enable error handling When checked, the designated administrator is sent a detailed report when a web site error occurs. The settings must be configured. Select this option to use Gallery Server Pro's own error handling routine to deal with all unexpected errors. Disable this option if you have an application-level error Gallery Server Pro 2.3 Administrator s Guide Page 131 of 238

132 handler defined in web.config or global.asax that you want to use for unhandled exceptions. Show error details Indicates whether to display the full details of any unhandled exception that occurs within the gallery. This can reveal sensitive information to the user, so it should only be used for debugging purposes. When unchecked, a generic error message is displayed. This setting has no effect if Error Handling is disabled. If an error is preventing you from opening this page to enable the option, you can enable it directly in galleryserverpro.config. Open this file, found in the gs\config directory, in any text editor. Change showerrordetails to true. Error handling and <customerrors> in web.config: Gallery Server Pro implements its own error handling mechanism that is independent of the <customerrors> section in web.config. This allows Gallery Server Pro to have the desired behavior without depending on a particular configuration of <customerrors>. However, you can override this behavior and revert control to <customerrors> if you wish. To do this, disable the error handling by unchecking the checkbox on this page. Data providers This section provides read-only information about how the ASP.NET data providers are configured in web.config and galleryserverpro.config. Click the information icon next to each provider to learn more about it and where it is configured. Site Settings Below is the page where settings can be edited. Gallery Server Pro 2.3 Administrator s Guide Page 132 of 238

133 Name and address to error reports to : Name and address to show s as coming from: SMTP server: Gallery Server Pro sends administrative s, including error reports, to this person. s sent from Gallery Server Pro (error reports and password change notifications) will appear to be sent from this person at this address. Specify the IP address or name of the SMTP server used to send s (e.g , Godzilla, mail.yourisp.com). This value is stored in the config file galleryserverpro.config. If you wish to use the SMTP server specified in web.config, (either explicitly assigned in this web application or inherited from a parent application) you may leave this field blank. Gallery Server Pro will automatically use the value specified in the system.net Gallery Server Pro 2.3 Administrator s Guide Page 133 of 238

134 mailsettings section if no value is specified here. SMTP server port: Specify the port number to use when sending SMTP mail. This setting is useful when the web server is behind a proxy. This value is stored in the config file galleryserverpro.config. If you wish to use the SMTP port specified in web.config (either explicitly assigned in this web application or inherited from a parent application), you may leave this field blank. Gallery Server Pro will automatically use the value specified in the system.net mailsettings section if no value is specified here. If not specified, and if no value is defined (nor inherited) in web.config, the default port 25 is used. Use SSL Select this option to send using Secure Sockets Layer (SSL) encryption. For example, the Gmail SMTP server requires SSL. If your provider requires authentication, you can specify a username and password in web.config. Open web.config, located in the web application root, and look for this section: <!-- <system.net> <mailsettings> <smtp> <network host="relayserverhostname" port="portnumber" username="username" password="password" /> </smtp> </mailsettings> </system.net> --> Uncomment the section by moving the --> to just before the <system.net> element. Then update the host, port, username, and password attributes to the correct values. When you are done, it will look something like this: <!-- --> <system.net> <mailsettings> <smtp> <network host="localhost" port="25" username="administrator" password="admin_password" /> </smtp> </mailsettings> </system.net> Note: When you enable this section in web.config, the SMTP server and port on the Site Settings - page are ignored, so you must specify the server (i.e. the host attribute) and port in web.config. Gallery Server Pro 2.3 Administrator s Guide Page 134 of 238

135 Site Settings Backup and Restore Data Gallery Server Pro stores data in two locations: The media files are stored in a physical directory on the web server s hard drive. Information about media objects and albums are stored in a SQL Server or SQLite database. Backing up, moving, copying, or restoring Gallery Server Pro data requires moving or copying both sets of data. The backup function built in to Gallery Server Pro exports all gallery data to an XML file, and the restore function replaces existing data with the data in the XML file. Note: The backup / restore function backs up and restores only the gallery data, not the media files. There are several techniques for implementing a backup strategy, several of which do not even use the built-in backup / restore function. See the section Backup strategy below for more information about performing regular backups. Backup strategy A regular backup is a normal part of every computer user's life. Which method you use, and how often, is up to you. Hopefully you don't learn the hard way that your strategy is inadequate. Backing up your gallery data involves these sets of data: The media files The data in the database. web.config and galleryserverpro.config configuration files Backing up the media files The media files are stored on your server's hard drive and can be backed up the same way you back up any files. You can discover the location where the media files are stored by referring to the Original file storage location on the Media Objects General page in the Site admin section of Gallery Server Pro. In the example below, the media files are stored at C:\inetpub\wwwroot\gs\mediaobjects. Gallery Server Pro 2.3 Administrator s Guide Page 135 of 238

136 Backing up the data SQL Server: For SQL Server databases, there are a number of ways to back up the data: 1. Use the backup functionality built in to SQL Server. 2. Use the backup function built in to Gallery Server Pro to export data to an XML file. See below for more information. 3. Use a third party backup program that knows how to back up SQL Server databases. 4. Copy the MDF database file to your backup location, either manually or through an automated script. SQLite: If you are using SQLite, backup your data with one of these techniques: Use the backup function built in to Gallery Server Pro to export data to an XML file. Copy the data file App_Data\galleryserverpro_data.sqlite to your backup location, either manually or through an automated script. Backing up the configuration files There are two configuration files that store information specific to your application you may want to back up: web.config - This is in the root of your Gallery Server Pro web application. galleryserverpro.config - This is in the gs\config directory of the Gallery Server Pro web application. If desired, back up these files using the same technique you use for your media files, whether it is a third party program, manually copying, or an automated script. Using the built-in backup function to create a backup file The database stores information about your media objects, such as title, extracted metadata, file names, etc. To export this data to an XML file, follow these steps. Gallery Server Pro 2.3 Administrator s Guide Page 136 of 238

137 1. Log on to Gallery Server Pro with an account that has Administer Site permission. 2. Click the Actions menu and go to Site admin. 3. In the left menu, navigate to the Backup / Restore page. The following screen appears: 4. To include login accounts in the file, make sure the Export user accounts option is selected. Note: Selecting Export user accounts includes the users, roles, and applications stored in the membership tables (the tables whose names start with "aspnet_"). When selected, ALL membership data is exported. If you using these tables to manage membership for other applications, be aware that the data for these other applications are also included in the backup file. 5. To include the gallery data, make sure the Export media object and album data option is selected. 6. Click Create and download backup file. A file is created and downloaded to your browser. Note: Remember that the backup file does not include the media files. It includes information about the media objects, such as titles, captions, and extracted metadata. Note: Be aware that the backup file may contain passwords in clear text format. Gallery Server Pro 2.3 Administrator s Guide Page 137 of 238

138 Using the built-in restore function Use the restore function to replace all data in your Gallery Server Pro database with the data in the backup file. Remember that the backup file does not include the media files. Restore these files separately by copying them from your backup device to your media objects directory. (You can do this either before or after the restore.) Note: The backup file must be the same data schema version as the version expected by the web application. For example, a backup file created in 2.2 cannot be restored to 2.3. However, a backup file created in can be restored to because the data schema is the same. You can view the current data schema version by creating a backup file and inspecting the contents with a text editor. The version is in the SchemaVersion element, like this: <SchemaVersion> </SchemaVersion>. SQL Server 2000 users: A limitation in SQL Server 2000 prevents the Restore function from working correctly. The only known workaround is to upgrade to a newer version of SQL Server or use SQLite. SQL Server 2005 / 2008 users: The restore function uses a very efficient algorithm for importing large amounts of data very quickly (equivalent to the bcp utility), but this technique requires SQL permissions equivalent to that provided in the db_ddladmin or db_owner roles. You may have to manually configure the SQL user using a tool such as SQL Management Studio to provide this permission. After the restoration is complete, you can revert to the original permissions. Note: Restoring data replaces the existing data. This action cannot be undone! To restore the gallery data from an XML file created with the backup function, follow these steps: 1. Log on to Gallery Server Pro with an account that has Administer Site permission. 2. Click the Actions menu and go to Site admin. 3. In the left menu, navigate to the Backup / Restore page. Click the Restore tab. The following screen appears: Gallery Server Pro 2.3 Administrator s Guide Page 138 of 238

139 4. Use the Browse button to select the backup file. Click Upload. The file will be verified and the web page will display the number of records in each of the tables in the backup file. 5. To import login accounts, make sure the Import user accounts option is selected. Note: If you de-selected the option Export user accounts when you created the backup file, then you do not have any users to restore. In this case, make sure to de-select the option Import user accounts Gallery Server Pro 2.3 Administrator s Guide Page 139 of 238

140 when restoring your data so that the current accounts - including the one you are logged on as - are not deleted. 6. To import the gallery data, make sure the Import media objects and album data option is selected. 7. Click Restore data. When the restore process is finished, a message will confirm that the restoration is complete. Note: Your current login account may no longer be valid since it was deleted during the restore. If this occurs, log out and log in using an account that was in the backup file. Migrate Gallery Server Pro to a new gallery Follow these directions for transferring an existing installation of Gallery Server Pro to another web application. The new web application may be on the same server or a new server. 1. Copy the web application files to the destination. 2. Use Internet Information Services (IIS) Manager to configure the new directory as a web application, ensure it is running under ASP.NET 2.0 or higher, and has default.aspx specified as the default document. (Click Start Run and then type inetmgr to start IIS Manager.) Note: If using IIS 7, you do not need to specify the default document. Note: For more information on using IIS Manager, refer to Using Internet Information Services (IIS) Manager Note: If you encounter an error about permissions, use Windows Explorer to give the user account IIS is running under modify permission to the web directory (ex: C:\inetpub\wwwroot\galleryserverpro). Refer to the section Configuring NTFS Permissions In Microsoft Windows for more information. 3. If your media files are not stored in the mediaobjects directory, then copy them to the new location, if required. After you copy them, you will need to update Gallery Server Pro so that it knows where your files are. This is on the Media Objects - General page in the Site administration console. 4. If you are using SQLite, then you already copied the gallery data, since it is in the file App_Data\galleryserverpro_data.sqlite. Skip the next step. 5. If you are using SQL Server and you need to migrate the data to another instance of SQL Server, you have two options: Use the tool built in to SQL Server for detaching / backing up and re-attaching / restoring the Gallery Server Pro database. Refer to your SQL Server documentation for more information. Use the backup function in Gallery Server Pro to back up the data to an XML file, then use the restore function at the destination gallery. Refer to the relevant section in this guide for creating a backup file and restoring it. If necessary, update the SQL Server connection string in web.config. Gallery Server Pro 2.3 Administrator s Guide Page 140 of 238

141 General Error Log Gallery Server Pro stores a log of errors and unexpected events. These items can be access on the Error Log page: View detailed information about each error by clicking the plus sign at the beginning of the row. When trying to discover the cause of an error, consider these tips: Read the message carefully. Sometimes a solution is provided within the message. Use the Gallery Server Pro forum or a search engine like Google to search for your error message. Chances are pretty good that someone has already seen the same error. Gallery Server Pro 2.3 Administrator s Guide Page 141 of 238

142 Consider whether it is negatively affecting your gallery. For example, a search engine that is re-visiting your site might request images that no longer exist, triggering a "File not found" error. There are clues in the details that tell you if the error was caused by a search engine - I wouldn t worry about these. If you cannot discover the cause of an error message, feel free to post a question on the forum. Please include ALL the detailed information in the log, but use care not to post sensitive information. For example, an error that occurs while logging in may contain your password in the details. If you post a question on the forum and I answer it by pointing to another thread that you should have found, your Karma loses 10 points. Error log options Remove oldest items - When enabled, Gallery Server Pro will limit the size of the error log to the number of errors specified here. When the maximum size is reached, the oldest errors are deleted to make room for the new ones. Use this feature to keep a rolling history of errors. Membership - User Settings The following screen shot shows the User Settings page: Gallery Server Pro 2.3 Administrator s Guide Page 142 of 238

143 Gallery Server Pro 2.3 Administrator s Guide Page 143 of 238

144 Self registration Gallery Server Pro supports anonymous users creating accounts in the gallery. There are several configuration options available such as requiring a valid address, setting the default security access and more. A full discussion of this feature, including how to configure it, is in the Self Registration section. User albums Gallery Server Pro can be used in community scenarios where users automatically receive a personal album they manage. A full discussion of this feature, including how to configure it, is in the User album section. User accounts This section describes several settings related to user accounts. Send when user is created Users specified here receive an notification when an account is created. This applies to both administrator-created or self-registered accounts. To receive an , each user must have a valid address and functionality must be configured. If self-registration is enabled with the validation option selected, then the is not sent until the new account holder validates the account from the verification . Allow users to enter HTML Indicates whether to allow limited HTML in titles, captions and external media objects (for example, embed code for a YouTube video). The list of valid HTML tags and attributes is defined below. When checked, any HTML that is not approved is automatically removed when the user attempts to enter it. For external media objects, the user is alerted to the invalid tags and the object is not added. When unchecked, HTML is not accepted in any user-editable field. This is the most secure and reliable way to prevent malicious attacks such as cross-site scripting. Unchecking this option does not remove HTML from existing objects. However, new and changed album and media object titles and captions will be stripped of HTML when they are saved. Note: Read more about Security considerations when allowing HTML and javascript in user-entered input. Gallery Server Pro 2.3 Administrator s Guide Page 144 of 238

145 Allowed HTML tags This is a comma separated list of HTML tags that are accepted as user input when the HTML option is enabled. If a tag is in this list, a user may include it album titles and summaries, media object titles, and external media object HTML snippets. For best performance, put the most commonly used HTML tags first. Allowed HTML attributes This is a comma separated list of HTML attributes that are accepted as user input when the HTML option is enabled. If an attribute is in this list, a user may include it album titles and summaries, media object titles, and external media object HTML snippets. Note that when an attribute is allowed, the value of the attribute is also allowed. The only filtering that takes place on an attribute value is the removal of the string "javascript:" when the javascript option is disabled. Allow users to enter javascript Specifies whether javascript is allowed in user input. When enabled, a user may include <script> HTML blocks and the string "javascript:" in HTML attributes. When disabled, all <script> tags and the string "javascript:" is removed from user input. Note: To use <script> tags, you must also enable HTML content and specify the script HTML tag as an allowed tag. WARNING: It is recommended you leave this option disabled, or only enable it temporarily, as turning it on increases the risk of a cross-site scripting attack and other malicious attacks. There may be times when enabling javascript may be useful. For example, some web sites use script tags in their embed code, so the only way to create a media object with their embed code is to have javascript enabled. One option for dealing with this is to temporarily enable javascript long enough to configure the media objects with the desired javascript. Since disabling this option does not remove existing javascript, this technique preserves the javascript in those objects while preventing users from adding any new javascript. Allow users to copy read-only objects Indicates whether to allow the copying of objects a user has only view permissions for. In a community gallery scenario, disabling this option can help prevent users from copying other users' items. When disabled, a user must be able to write to an album in order to copy objects from it. When enabled, a user can copy objects from any album for which they have view permission. Allow users to manage their own account When enabled, a link to the user's account page appears at the top right of every page. This page allows a user to change their password, update their address, enter a description, disable their personal user album (if user albums are enabled), and delete their account. Gallery Server Pro 2.3 Administrator s Guide Page 145 of 238

146 Disable this option to prevent a user from making these changes. An administrator can always change these settings, even when this setting is disabled, through the Manage Users page in the Site admin area. Allow users to delete their account When enabled, an option is made available on each user's My account page to delete the account. This setting is typically enabled in community gallery scenarios where users are creating their own accounts. Warning: If user albums are enabled and a user deletes their account, the contents of the user's personal album are also deleted. Membership Users The Manage Users page is used to administer the accounts used by users in the gallery. User accounts are assigned to one or more roles. There is no limit to the number of users that can be created. A full discussion of users, including how to use the Manage Users page, is in the Users section. Membership Roles This section describes how to use the Manage Roles page. A full discussion of roles, including how to use the Manage Roles page, is in the Roles section. Albums General The Albums - General page contains settings specific to albums. Gallery Server Pro 2.3 Administrator s Guide Page 146 of 238

147 Album settings Enable album paging Page size Indicates whether to limit the number of media objects to display at a time. When paging is enabled and an album has a large number of items, paging controls appear to assist the user in navigating to them. When disabled, all objects are displayed in an album. The number of albums and media objects to display at one time. When an album contains more than this number of items, paging controls are Gallery Server Pro 2.3 Administrator s Guide Page 147 of 238

148 displayed. Pager location Number of characters of album title to display on thumbnail Indicates whether the pager controls are displayed at the top, bottom, or top and bottom. The maximum number of characters to display when showing the title of an album in thumbnail view. Empty album thumbnail settings Text Font name Font size (px) Font color Background color Aspect ratio The text to appear on an empty album s thumbnail image The font in which the text on an empty album s thumbnail is displayed. The font must be installed on the web server. If the font is not installed, a generic sans serif font will be substituted. The size, in pixels, of the font used to display the text on an empty album s thumbnail image. Valid values: The color of the text to display on an empty album s thumbnail image. It can be specified as hex (e.g. #336699), RGB (e.g. 127,55,95), or one of the System.Color.KnownColor enum values in the.net Framework (e.g. Maroon). The background color of the thumbnail image appearing on empty albums. It can be specified as hex (e.g. #336699), RGB (e.g. 127,55,95), or one of the System.Color.KnownColor enum values in the.net Framework (e.g. Maroon). The ratio of the width to height of the thumbnail image on an empty album. The length of the longest side of the image is set by the Thumbnail Image Length property (Media Objects General page), and the length of the remaining side is calculated using this ratio. A ratio of more than 1.00 results in the width being greater than the height (landscape), while a ratio less than 1.00 results in the width being less than the height (portrait). Example: If Thumbnail Image Length = 115 and the aspect ratio = 1.50, the width of the default thumbnail image is 115 and the height is 77 (115/1.50). Gallery Server Pro 2.3 Administrator s Guide Page 148 of 238

149 Media Objects General The Media Objects General page contains settings specific to media objects. Recall that a media object is any file that Gallery Server Pro is managing within its gallery. It can be a photo, video, audio, document, or any other type of file. Gallery Server Pro 2.3 Administrator s Guide Page 149 of 238

150 Media object storage The Media object storage section tells Gallery Server Pro where the media object files are stored. There are up to three different locations: (a) original location, (b) thumbnail image location, (c) compressed image location. By default Gallery Server Pro is configured to store the original files, thumbnails and compressed image files in the gs\mediaobjects directory of the web application. For example, if Gallery Server Pro is installed Gallery Server Pro 2.3 Administrator s Guide Page 150 of 238

151 at C:\inetpub\wwwroot\gallery\, then Gallery Server Pro uses C:\inetpub\wwwroot\gallery\gs\mediaobjects\ as the storage location for your media objects. If no location is specified for the thumbnail and compressed objects, these files are stored in the same directory as the original files. Each media object added to Gallery Server Pro has up to three files: (a) the original file, (b) a small thumbnail image representing the object, (c) a compressed, bandwidth friendly image (large image files only). You can specify where each of these types of files are stored. Gallery Server Pro supports storing media objects on a local hard drive or any UNC share. This includes other computers, external hard drives, and even network-attached storage (NAS) devices. Note: Mapped drives present a security risk and are not supported. SECURITY WARNING: If your media objects directory is within the web application (which is the default), then users can bypass security by guessing the URLs to the media object. If you wish to prevent this, move the directory outside the web application so that IIS will not serve requests to the objects. Note that your application must run in Full Trust to access files outside the web application directory. Original file storage location Enter a path to tell Gallery Server Pro where your media files exist. The path may be: Relative to the root of the web application (e.g. \gs\mediaobjects) A full path to a local resource (e.g. C:\mymedia) A UNC path to a local or network resource (e.g. \\mynas\media) Attention: Note that the IIS application pool identity must have modify permission to this location. If specifying a UNC share, it must also have file share permission. The default user (Network Service in IIS 7 and IIS AppPool\DefaultAppPool in IIS 7.5) does not have network permissions and cannot access remote directories. To provide access to a UNC share, modify the application pool identity in IIS to specify another user, and ensure that user has the required permission on the network device. Note: Changing the location does not move objects to the new location. To move your objects to the new directory, move them with a utility such as Windows Explorer. Media object storage options Media files are read-only In some cases you may not want to allow Gallery Server Pro to make any changes to your media files. In other words, you want to expose a read-only view of your media collection. When Gallery Server Pro is in read-only mode, users cannot create albums or Gallery Server Pro 2.3 Administrator s Guide Page 151 of 238

152 upload files, nor can they move, copy or delete albums and media objects. That is, they cannot perform any action that modifies the original media files. However, users can synchronize, download, rearrange and edit captions, and administrators can change settings in the Site admin area, including managing users and roles. When a gallery is read-only, the only way to add or remove media objects and albums is by manually updating the media objects directory with a tool like Windows Explorer and then running the synchronize function. For more information see the section Creating a read-only gallery. Synchronize directory names with album titles Indicates whether to update the directory name corresponding to an album when the album's title is changed. When true, modifying the title of an album causes the directory name to change to the same value. You may want to disable this if you have a directory structure that you do not want Gallery Server Pro to alter. Example: Changing where thumbnail and compressed images are stored By default Gallery Server Pro stores the original, thumbnail, and compressed file in the gs\mediaobjects directory. To keep the directory containing the original media files clean and tidy, you might want to keep the auto-generated thumbnail and compressed images in a separate directory named cache. Open the Media Objects General page in Gallery Server Pro. Update the Thumbnail image storage location and Compressed image storage location to cache. Click Save changes. Note: If the cache directory does not exist, Gallery Server Pro will attempt to create it. If the IIS application pool identity does not have permission to create the directory, an error message will appear. Use Windows Explorer to either manually create the directory using your own permissions or give the IIS account permission to create the directory. Note: If the cache directory exists, but the IIS application pool identity does not have permission to write to the directory, an error message will appear. Use Windows Explorer to give the IIS account modify permission to the cache directory. Select the Synchronize menu option from the Actions menu to open the synchronize page. Select the Include child directories (recursive) option and click Synchronize. Gallery Server Pro will create new thumbnails in the cache directory and remove the previous ones from the mediaobjects directory. Media object options Enable image metadata Specifies whether Gallery Server Pro extracts and displays metadata from image files. When enabled, image metadata such as title, camera model, etc, are extracted from image files when they are uploaded by Gallery Server Pro 2.3 Administrator s Guide Page 152 of 238

153 a user or added through the synchronization process. Users can view this metadata by clicking the toolbar button above the media object. The following formats are supported: EXIF, XMP, text, IFD, and IPTC. Disabling this option causes the toolbar icon to be hidden, even if metadata has previously been extracted. The metadata is not deleted and can be made visible again by re-enabling this option. This option is relevant only for image media types. Enhanced metadata extraction When enabled, metadata is extracted from image files using the Windows Presentation Foundation (WPF) classes available in.net Framework 3.0 and higher. The WPF classes allow additional metadata to be extracted beyond those allowed by the.net Framework 2.0, such as title, keywords, and rating. This option requires that.net Framework 3.0 or higher is installed on the web server and the web application is running in Full Trust. Allow downloading media files Specifies whether Gallery Server Pro shows a download button in the toolbar that appears above media objects. Note that disabling this setting is not 100% effective in preventing a user from downloading a media object, since a user already has access if he or she can view it in the browser. The only effective method for ensuring users cannot download your media files is to use DRM protection, which is a feature that Gallery Server Pro does not provide. Allow downloading multiple media files in ZIP archive Specifies whether users are allowed to download multiple media files in a ZIP archive. When enabled, a toolbar button appears above the media object, in the album summary section on the album view page, and in the Actions menu. This option is system wide and cannot be applied on a per-user or per-album basis. Generate permalink Specifies whether Gallery Server Pro offers a permalink for a media object. When enabled, a toolbar button appears above the media object that displays a permanent hyperlink to that object. This hyperlink links directly to the media object and is a convenient way to share links with others. This feature is necessary because AJAX callbacks are used as the user navigates the media objects in an album and the url in the browser's address bar is not updated for each media object. Enable slide show Specifies whether slide show functionality is enabled. When enabled, a start/pause slideshow button is displayed in the toolbar that appears above a media object. The length of time each image is shown before automatically moving to the next one is controlled by the slideshow interval setting. Gallery Server Pro 2.3 Administrator s Guide Page 153 of 238

154 Note that only images are shown during a slide show; other objects such as videos, audio files, and documents are skipped. Transition effects Media object transition effect Specifies the visual transition effect to use when browsing from one media object to the next. Media object transition duration The duration of the transition effect, in seconds, when navigating between media objects. This setting has no effect when the media object transition effect is set to None. Upload settings Upload media files Indicates whether users are allowed to upload media files, such as photos, audio, and video. Unchecking this setting causes the Local Media tab on the Add objects web page to be hidden. Users must also be authenticated and a member of a role with AllowAddMediaObject or AllowAdministerSite permission in order to upload files. If this setting is disabled, and the Link to external content setting is also disabled, the only way to add media objects is through synchronizing. Link to external content Indicates whether users can add a link to external content, such as a YouTube video. Unchecking this setting causes the External Content tab on the Add objects web page to be hidden. Users must also be authenticated and a member of a role with AllowAddMediaObject or AllowAdministerSite permission in order to add external links. If this setting is disabled, and the Upload media files setting is also disabled, the only way to add media objects is through synchronizing. Maximum upload file size Indicates the maximum size, in kilobytes, of the files that can be uploaded using the Add Objects function. The default value is (2 GB). Use this setting to keep users from uploading very large files and to help guard against Denial of Service (DOS) attacks. A value of zero (0) indicates there is no restriction on upload size (unlimited). Note: IIS 7 restricts uploads larger than about 30 MB, even if the maxrequestlength attribute is modified. Read the section Modify request filtering in IIS 7 below. Gallery Server Pro 2.3 Administrator s Guide Page 154 of 238

155 This value applies to the content length of the entire upload request, not just the file. For example, if this value is 1024 KB and the user attempts to upload two 800 KB images, the request will be blocked because the total content length is larger than 1024 KB. This setting is not used during synchronization. The maximum request length may also be specified in web.config through the maxrequestlength attribute. Gallery Server Pro will enforce the smaller of these two values. If web.config specifies a value smaller than the value specified here, ASP.NET will throw an error. For example, Firefox users receive the message "The connection was reset. The connection to the server was reset while the page was loading." IE 7 users receive "Internet Explorer cannot display the webpage." As you can see, the error is not very user friendly, so it is preferable to keep the value in web.config larger than the value specified here. Note: This setting is not used when the application is running at less than Full Trust. In this case, the maxrequestlength setting in web.config controls the upload file size. To change the setting in web.config, follow these steps: 1. Open web.config in a text editor such as Notepad. 2. Look for this section: <location path="default.aspx"> <system.web> <httpruntime maxrequestlength=" " executiontimeout="86400" /> </system.web> </location> 3. Edit the value for the maxrequestlength to the desired value. It is in kilobytes, so to specify 100 MB, enter the value Example You set the maximum upload limit to 4096 (4 MB). A user attempts to upload a 6 MB image. The upload will fail because it exceeds the 4MB limit. Another user attempts to upload three 2 MB images at one time. Even though each image is less than 4 MB, the upload will fail because the total size of the upload request is greater than the 4 MB limit. Another user attempts to upload a 1.5 MB zip file containing twenty 100 KB images. The upload succeeds. Note: This limit is enforced on the content length of the entire request, not just the size of the file(s), so you may notice some uploads are rejected if they are close, but not exceeding, this limit, because the total length of the request exceeds the limit. Modify request filtering in IIS 7 By default IIS 7 restricts uploads larger than about 30 MB. To allow larger uploads, configure web.config to specify a new value for the <requestfiltering> element. Open web.config and look for the following section. <security> <requestfiltering> Gallery Server Pro 2.3 Administrator s Guide Page 155 of 238

156 <requestlimits maxallowedcontentlength=" "/> </requestfiltering> </security> By default it is commented out. That is, it is surrounded by <!-- --> tags. Uncomment the section by moving the closing comment (-->) to before the <security> element. Modify the attribute maxallowedcontentlength to the desired value. It is in bytes, so a value of 2 GB would be specified as (2 * 1024 * 1024 * 1024). Save your changes. After making this change you may receive an error in Gallery Server Pro that says that requestfiltering cannot be overridden. This is a security feature. To allow requestfiltering to be overridden in web.config, you must edit another configuration file. Open %windir%\system32\inetsrv\config\applicationhost.config file and change the string: <section name="requestfiltering" overridemodedefault="deny" /> to: <section name="requestfiltering" overridemodedefault="allow" /> Media object thumbnail settings Thumbnail image length The length (in pixels) of the longest edge of a thumbnail image. The length of the shorter side is calculated automatically based on the aspect ratio of the image. Media object thumbnail title character max The maximum number of characters to display when showing the title of a media object in thumbnail view. Quality of thumbnail images The quality level that thumbnail JPG images are created with. Valid values are 1-100, with 1 being the worst quality (smallest file size) and 100 being the best quality (largest file size). Thumbnail file name prefix The string that is prepended to the thumbnail file name for each media object. For example, if an image named puppy.jpg is added, and this setting is zthumb_, the thumbnail image will be named zthumb_puppy.jpg. NOTE: Any file named zthumb_puppy.jpg that already exists will be overwritten, so it is important to choose a value that, when prepended to media object file names, will not conflict with existing media objects. Gallery Server Pro 2.3 Administrator s Guide Page 156 of 238

157 NOTE: After changing this value, perform a synchronization so that new thumbnails are created with the new name and the old ones are deleted. Media Objects Media Object Types The Media Object Types page lets you configure the types of media files managed by Gallery Server Pro. By default only files with a JPG or JPEG file extension are allowed. To enable Gallery Server Pro to manage additional types of media objects AVI videos, for example select the checkbox next to the AVI file type and click Save changes. Below is a screen shot of the Media Object Types page. If you disable a file type that has existing media objects in the gallery, those objects will be removed from the gallery during the next synchronization. Specifically, the associated database record in the media objects table (gs_mediaobject) is deleted but the original media file is not deleted. This provides the opportunity to later re-enable the file type, synchronize the database, and recover the previously removed media object. Gallery Server Pro 2.3 Administrator s Guide Page 157 of 238

158 Note that this is different behavior than when a media object is deleted with the Delete command, which deletes both the database record and the associated media files. To add a mime type not in the list, edit the file types directly in the configuration file gs\config\galleryserverpro.config. If the Allow any file type, regardless of whether it is listed below option is checked, Gallery Server Pro is allowed to manage file types not explicitly specified in the mime types list. When unchecked, only files with an extension in the list and marked as enabled are allowed. When this option is checked, Gallery Server Pro accepts all file types regardless of their file extension. For maximum security, leave this unchecked and enable only those file types you want to include in the Gallery Server Pro gallery. Media Objects Images The Media Objects Images page allows the administrator to specify several options for displaying images in Gallery Server Pro. The Media Objects Images page appears below. Gallery Server Pro 2.3 Administrator s Guide Page 158 of 238

159 Gallery Server Pro 2.3 Administrator s Guide Page 159 of 238

160 Compressed images When an image is added, Gallery Server Pro analyzes the image to determine if a compressed, bandwidth-friendly version of the image should be created. It uses two criteria when evaluating the image: 1. Is the file size of the image larger than the compression limit? 2. Is the length of the image's longest side larger than the compressed image length? If the answer to either of these questions is true, Gallery Server Pro creates a compressed version of the image. The following table describes the options that are available for compressed images. Display original images by default Compression Limit This setting specifies whether the original image or the compressed image is displayed when the user clicks the thumbnail of an image. If unchecked, the compressed image, if it exists, is shown. When checked, the compressed image is ignored and the original file is displayed. The compression limit is identified with the heading Make a compressed copy of images above this size (kb). If an image's file size is larger than this value, a bandwidth-friendly, compressed version is created. The original image is never altered nor deleted, regardless of this setting. (Rotating is the only function that modifies the original image.) This setting is used: (a) when new images are added to the gallery and (b) during synchronization if the Overwrite existing compressed images option is selected. Compressed Image Length The compressed image length is identified with the heading Length of longest side of compressed images (px). This value is used in two ways: 1. When a new image is added, Gallery Server Pro compares the length of the longest side of the new image to this value. If it is longer, than Gallery Server Pro creates a compressed version of the image. 2. This value dictates the length of compressed images in Gallery Server Pro. Specifically, it dictates the length of the longest side of an image. Therefore, it can refer to either the width or the height, depending whether an image is a portrait or landscape. The length of the shorter side of an image is automatically calculated based on the aspect ratio of the image. Compressed Image Quality This is the quality level with which compressed JPG images are created. Valid values are 1-100, with 1 being the worst quality (smallest file size) and 100 Gallery Server Pro 2.3 Administrator s Guide Page 160 of 238

161 being the best quality (largest file size). Example: You upload a 1656 px by 1242 px JPG image that is 800 kb. You have Gallery Server Pro configured with these settings: The compression limit is 50 kb. The compression quality setting is 70. The compressed image length is 640 px. Since the image is larger than the 50 kb limit, a compressed copy of the original is created with a quality setting of 70 and the dimensions 640 px by 480. NOTE: In this example, even if the original image is less than 50 kb, a compressed image is still created, because the length of its longest side px - is longer than the compressed image length setting (640 px). Original images Original Image Quality Discard original file when adding to gallery The quality level at which original JPG images are saved. This setting is only used when the original is rotated by the user. Valid values are 1-100, with 1 being the worst quality (smallest file size) and 100 being the best quality (largest file size). Specifies whether to discard the original image when it is added to the gallery. This option, when enabled, helps reduce disk space usage. This option applies only to images, and only when they are added through an upload or by synchronizing. Changing this setting does not affect existing media objects. When unchecked, users still have the option to discard the original image on the Add Objects page by unchecking the corresponding checkbox. Watermark settings Watermarks on images are helpful if images need to be protected from unwanted duplication or to communicate the source of the image. Below is an example of an image with an image and text watermark. Gallery Server Pro 2.3 Administrator s Guide Page 161 of 238

162 Configure settings for the watermark function on the Media Objects Images page as shown below. Apply watermark to compressed and original images - Applies a watermark to compressed and original images. If checked, both the text and the image specified in Watermark text options and Watermark image options are applied to images. Note: If a user belongs to a role with View images without watermarks permission, then no watermarks are applied to images for this user, regardless of this setting. Also apply watermark to thumbnails - Specifies whether to apply the text and/or image watermark to thumbnail images. This property is ignored if watermarking is disabled. Watermark text options Watermark text Font name Specifies the text to apply to images in the gallery. The text is applied in a single line. Leave this setting blank if no text watermark is desired. The font used for the watermark text. If the font is not installed on the web server, a generic sans serif font will be substituted. Font size Specifies the height, in pixels, of the watermark text. Valid values are Note: This value is ignored if the watermark text width percentage is non-zero. Text width % Specifies the percent of the overall width of the recipient image that should be covered with the watermark text. The size of the text is automatically scaled up Gallery Server Pro 2.3 Administrator s Guide Page 162 of 238

163 or down to achieve the desired width. Valid values are This setting overrides the watermark font size setting. To disable this setting so that the watermark font size is enabled, set this value to zero. For example, a value of 50 means the text is 50% as wide as the recipient image. The text is never rendered in a font smaller than 4 pixels, so in cases of long text it may stretch wider than the percentage specified in this setting. Font color Text opacity % Text location The background color of the thumbnail image. It can be specified as hex (e.g. #336699), RGB (e.g. 127,55,95), or one of the System.Color.KnownColor enum values in the Microsoft.NET Framework (e.g. Maroon). The opacity of the watermark image. Valid values are 0-100, 0 being completely transparent and 100 completely opaque. Specifies the location for the watermark text on the recipient image. Watermark image options Path to image to be used as watermark Specifies the full or relative path to a watermark image to be applied to the recipient image. Common image types, such as JPG, GIF, BMP, TIF, and PNG are accepted. Relative paths are relative to the root of the web application. The directory separator character can be either a forward or backward slash, and, for relative paths, the initial slash is optional. Leave this setting blank if no image watermark is desired. Examples: /gs/images/mywatermark.jpg gs/images/mywatermark.gif \gs\images\mywatermark.bmp gs\images\mywatermark.tif C:\images\mywatermark.png Watermark image width % Specifies the percent of the overall width of the recipient image that should be covered with the watermark image. The size of the image is automatically scaled to achieve the desired width. Valid values are For example, a value of 50 means the watermark image is 50% as wide as the recipient image. Gallery Server Pro 2.3 Administrator s Guide Page 163 of 238

164 Watermark image opacity % Watermark image location A value of 0 turns off this feature and causes the image to be rendered at its actual size. The opacity of the watermark image. Valid values are 0-100, 0 being completely transparent and 100 completely opaque. Specifies the location for the watermark image on the recipient image. More information about the watermarking functionality can be found in the Watermarking section. Media Objects Video / Audio / Other This page contains settings for any locally stored media file that meets the following criteria: It is not an image. (A file is considered an image if its file extension corresponds to the image mime type as configured in the Media Object Types list.) An htmloutput template has been defined for the file s mime type in the configuration file galleryserverpro.config. By default, Gallery Server Pro defines templates for all video, audio, and Shockwave Flash (SWF) files. Note: This page is not relevant for externally hosted media objects such as YouTube videos. It applies only to media files stored on the local network. Gallery Server Pro 2.3 Administrator s Guide Page 164 of 238

165 Automatically start video, audio, and other dynamic content when the browser loads - Specifies whether a video, audio or other dynamic media object will automatically start playing in the user's browser. This setting is ignored if the browser plug-in does not support this feature or if the htmloutput template does not reference the AutoStartMediaObjectInt or AutoStartMediaObjectText variables. Gallery Server Pro 2.3 Administrator s Guide Page 165 of 238

166 Video settings Video player width (px): Video player height (px): Specifies the width, in pixels, of the browser plug-in that plays a video file. Specifies the height, in pixels, of the browser plug-in that plays a video file. Audio settings Audio player width (px): Audio player height (px): Specifies the width, in pixels, of the browser plug-in that plays an audio file. Specifies the height, in pixels, of the browser plug-in that plays an audio file. Settings for objects other than images, video, and audio Generic object width (px): Specifies the width, in pixels, of the browser plug-in that displays a generic media object. This is used primarily for Shockwave Flash objects, but applies to any file with a mime type (a) that is not an image, video, or audio object, and (b) for which there are rendering instructions in the mediaobjects section of the configuration file galleryserverpro.config. This value is mapped to the dynamic {Width} property that can be used in the htmloutput attribute of the browser XML element in galleryserverpro.config. An alternative to setting the value here is to specify the desired value directly in the htmloutput attribute for the desired mime type in the configuration file instead of using {Width}. This can be useful if, for example, you want all Shockwave files rendered at one size and generic media objects of another type to be rendered at another size. Generic object height (px): Specifies the height, in pixels, of the browser plug-in that displays a generic media object. This is used primarily for Shockwave Flash objects, but applies to any file with a mime type (a) that is not an image, video, or audio object, and (b) for which there are rendering instructions in the mediaobjects section of the configuration file galleryserverpro.config. This value is mapped to the dynamic {Height} property that can be used in the htmloutput attribute of the browser XML element in galleryserverpro.config. An alternative to setting the value here is to specify the desired value directly in the htmloutput attribute for the desired mime type in the configuration file instead of using {Height}. This can be useful if, for example, you want all Shockwave files rendered at one size and generic Gallery Server Pro 2.3 Administrator s Guide Page 166 of 238

167 media objects of another type to be rendered at another size. Configuration Settings in galleryserverpro.config Gallery Server Pro stores application level configuration settings in a file named galleryserverpro.config. It is stored in the gs\config directory in the web application. Most of the settings are exposed in the user interface in the Site administration console (click Site admin from the Actions menu). Most users will not need to edit this file, but some advanced tasks such as modifying an HTML template or adding a new MIME type require manual editing. Core configuration settings The first part of the configuration file contains core configuration settings. It consists of an XML element named core with dozens of attributes. <core galleryid="1"... /> Below is a list of the attributes and a description. Edit the values as desired and save. The web application automatically senses that the file has been updated and will restart with the new values. Note: In some cases, the web application does not restart when the configuration file has changed, causing the file changes to be ignored. If this occurs, recycle the application pool or enter iisreset in a Start-Run dialog box. Configuration setting galleryid mediaobjectpath mediaobjectpathisreadonly Description The value that uniquely identifies the gallery for this website. Each web application is associated with a single gallery. The path to a directory containing the media objects. The path may be relative to the root of the web application (e.g. \gs\mediaobjects), a full path to a local resource (e.g. C:\mymedia), or a UNC path to a local or network resource (e.g. \\mynas\media). Mapped drives present a security risk and are not supported. The initial and trailing slashes are optional. For relative paths, the directory separator character can be either a forward or backward slash. Specifies that the directory containing the media objects should never be written to by Gallery Server Pro. This is useful when configuring the gallery to expose an existing media library and the administrator will not add, move, or copy objects using the Gallery Server Pro UI. Objects can be added or removed to the gallery only by the synchronize function. Functions that do not require modifying the original files are still available, such as editing captions and Gallery Server Pro 2.3 Administrator s Guide Page 167 of 238

168 summaries, rearranging items, and the security system. Configuring a read-only gallery requires setting the thumbnail and optimized paths to a different directory, disabling user albums (enableuseralbum), and disabling the album title / directory name synchronization setting (synchalbumtitleanddirectoryname). pageheadertext pageheadertexturl showlogin showsearch showerrordetails enableexceptionhandler defaultalbumdirectorynamelength synchalbumtitleanddirectorynam e The header text that appears at the top of each web page. Also known as the gallery title. The URL the user will be directed to when she clicks the page header text (gallery title). Optional. If not present, no link will be rendered. Examples: " "/" (the root of the web site), "~/" (the top level album). Indicates whether to show the login controls at the top right of each page. When false, no login controls are shown, but the user can navigate directly to the login page to log on. Indicates whether to show the search box at the top right of each page. Indicates whether to show the full details of any unhandled exception that occurs within the gallery. This can reveal secure information to the user, so it should only be used for debugging purposes. When false, a generic error message is given to the user. This setting has no effect when enableexceptionhandler="false". Indicates whether to use Gallery Server Pro's internal exception handling mechanism. When true, unhandled exceptions are transferred to a custom error page and, if showerrordetails="true", details about the error are displayed to the user. When false, the error is recorded and the exception is rethrown, allowing application-level error handling to handle it. This may include code in global.asax. The customerrors element in web.config may be used to manage error handling when this setting is false (the customerrors setting is ignored when this value is true). The maximum length of the directory name when a user creates an album. By default, a directory name is the same as the album's title, but is truncated when the title is longer than the value specified here. Indicates whether to update the directory name corresponding to an album when the album's title is changed. When true, modifying the title of an album causes the directory name to be changed to the Gallery Server Pro 2.3 Administrator s Guide Page 168 of 238

169 same value. If the title is longer than the value specified in defaultalbumdirectorynamelength, the directory name is truncated. You may want to set this to false if you have a directory structure that you do not want Gallery Server Pro to alter. Note that even if this setting is false, directories will still be moved or copied when the user moves or copies an album. Also, Gallery Server Pro always modifies the directory name when it is necessary to make it unique within a parent directory. For example, this may happen if you give two sibling albums the same title or you move/copy an album into a directory containing another album with the same name. emptyalbumthumbnailbackground Color emptyalbumthumbnailtext emptyalbumthumbnailfontname emptyalbumthumbnailfontsize emptyalbumthumbnailfontcolor The color used for the background of the GIF image generated by Gallery Server when creating a default thumbnail image for a newly created album or an album without any objects. The color can be specified as hex (e.g. #336699), RGB (e.g. 127,55,95), or one of the System.Color.KnownColor enum values (e.g. Maroon). The default text written on the GIF image generated by Gallery Server when creating a default thumbnail image for a newly created album or an album without any objects. The GIF is dynamically generated by the application when it is needed and is never actually stored on the hard drive. The font used for text written on the GIF image generated by Gallery Server when creating a default thumbnail image for a newly created album or an album without any objects. The font must be installed on the web server. If the font is not installed, a generic sans serif font will be substituted. The size, in pixels, of the font used for text written on the GIF image generated by Gallery Server when creating a default thumbnail image for a newly created album or an album without any objects. The color of the text specified in property EmptyAlbumThumbnailText. The color can be specified as hex (e.g. #336699), RGB (e.g. 127,55,95), or one of the System.Color.KnownColor enum values (e.g. Maroon). emptyalbumthumbnailwidthtohei ghtratio The ratio of the width to height of the default thumbnail image for an album that does not have a thumbnail image specified. The length of the longest side of the image is set by the MaxThumbnailLength property, and the length of the remaining side is calculated using this ratio. A ratio or more than 1.00 results in the width being greater than the height (landscape), while a ratio less than 1.00 results in the Gallery Server Pro 2.3 Administrator s Guide Page 169 of 238

170 width being less than the height (portrait). Example: If MaxThumbnailLength = 115 and EmptyAlbumThumbnailWidthToHeightRatio = 1.50, the width of the default thumbnail image is 115 and the height is 77 (115 / 1.50). maxalbumthumbnailtitledisplayle ngth maxmediaobjectthumbnailtitledis playlength allowhtmlintitlesandcaptions allowuserenteredjavascript allowedhtmltags allowedhtmlattributes allowcopyingreadonlyobjects Maximum # of characters to display when showing the title of an album thumbnail view. Maximum # of characters to display when showing the title of a media object in a thumbnail view. Indicates whether to allow limited HTML in titles, captions and external media objects (for example, embed code for a YouTube video). Read more in User accounts. Specifies whether javascript is allowed in user input. Read more in User accounts. This is a comma separated list of HTML tags that are accepted as user input when the HTML option is enabled. Read more in User accounts. This is a comma separated list of HTML attributes that are accepted as user input when the HTML option is enabled. Read more in User accounts. Indicates whether to allow the copying of objects a user has only view permissions for. In a community gallery scenario, disabling this option can help prevent users from copying other users' items. When disabled, a user must be able to write to an album in order to copy objects from it. When enabled, a user can copy objects from any album for which they have view permission. allowmanageownaccount When enabled, a link to the user's account page appears at the top right of every page. This page allows a user to change their password, update their address, enter a description, disable their personal user album (if user albums are enabled), and delete their account. Disable this option to prevent a user from making these changes. An administrator can always change these settings, even when this setting is disabled, through the Manage Users page in the Site admin area. Gallery Server Pro 2.3 Administrator s Guide Page 170 of 238

171 allowdeleteownaccount When enabled, an option is made available on each user's My account page to delete the account. This setting is typically enabled in community gallery scenarios where users are creating their own accounts. Warning: If user albums are enabled and a user deletes their account, the contents of the user's personal album are also deleted. mediaobjecttransitiontype mediaobjecttransitionduration slideshowinterval mediaobjectdownloadbuffersize encryptmediaobjecturlonclient encryptionkey Specifies the visual transition effect to use when moving from one media object to another. This value maps to the enumeration GalleryServerPro.Business.MediaObjectTransitionType, and must be one of the following values: None, Fade. The duration of the transition effect, in seconds, when navigating between media objects. This setting has no effect when mediaobjecttransitiontype = "None". The delay, in milleseconds, between images during a slide show. The size of each block of bytes sent to the client when downloading media objects (images, video, etc.) Indicates whether security-sensitive portions of the URL to the media object are encrypted when it is sent to the client browser. Valid values are "true" and "false". When false, the URL to the media object is sent in plain text, such as handler/getmediaobject.ashx?moid=34&aid=8&mo=c%3a%5cgs%5 Cmypics%5Cbirthday.jpeg&mtc=1&dt=1 These URLs can be seen by viewing the source of the HTML page. From this URL one can determine the album ID for this media object is 8, (aid=8), the file path to the media object on the server is C:\gs\mypics\birthday.jpeg, and the requested image is a thumbnail (dt=1, where 1 is the value of the GalleryServerPro.Business.DisplayObjectType enumeration for a thumbnail). For enhanced security, set encryptmediaobjecturlonclient to true, which uses Triple DES encryption to encrypt the query string. It is recommended to set this to true except when you are troubleshooting and it is useful to see the file name and path in the HTML source. The Triple DES algorithm uses the secret key specified in the encryptionkey attribute. The secret key used for the Triple DES algorithm. Applicable when encryptmediaobjecturlonclient = true. The string must be 24 characters in length and be sufficiently strong so that it cannot be easily cracked. An exception is thrown by the.net Framework if the key is considered weak. The installation wizard updates this setting Gallery Server Pro 2.3 Administrator s Guide Page 171 of 238

172 with a unique encryption key each time it is run. allowunspecifiedmimetypes imagetypesstandardbrowserscand isplay silverlightfiletypes allowanonymoushiresviewing enableimagemetadata enablewpfmetadataextraction Indicates whether Gallery Server Pro is allowed to manage file types not explicitly specified in the mimetypes configuration section. When false, any file with an extension not listed in the mimetypes section is rejected. When true, Gallery Server Pro accepts all file types regardless of their file extension. A comma separated list of file extensions indicating types of images that a standard browser can display. When the user requests an original image (high resolution), the original is sent to the browser in an <img> HTML tagif its extension is one of those listed here. If not, the user is presented with a message containing instructions for downloading the image file. Typically this setting should not be changed. A comma-delimited list of file extensions, including the period, indicating types of files that are supported by Microsoft Silverlight and that the user wishes to be rendered using Silverlight. This setting is used to determine whether to send the Silverlight javascript files to the browser. Note that this setting is used in combination with the HTML template. That is, rendering objects in Silverlight requires that the HTML template specify Silverlight and the file type associated with that template be included in this setting. If Silverlight is not used, a slight performance enhancement can be achieved by setting this value to an empty string. Ex:.mp3,.wma,.wmv,.asf,.asx Specifies whether anonymous users are allowed to view the original, uncompressed versions of images. When no compressed (optimized) version of an image exists, the user is allowed to view the original, regardless of this setting. This setting has no effect on non-image media objects or for logged on users. Specifies whether Gallery Server Pro extracts and displays metadata from image files. The metadata is displayed next to the optimized version of images when the View metadata toolbar icon is invoked. If the attribute enablewpfmetadataextraction is true, then additional metadata such as title, keywords, and rating is extracted. Specifies whether metadata is extracted from image files using Windows Presentation Foundation (WPF) classes in.net Framework 3.0. The WPF classes allow additional metadata to be extracted beyond those allowed by the.net Framework 2.0, such as title, keywords, and rating. This attribute has no effect unless the following requirements are met: The attribute Gallery Server Pro 2.3 Administrator s Guide Page 172 of 238

173 enableimagemetadata = "true";.net Framework 3.0 is installed on the web server; the web application is running in Full Trust. The WPF classes have exhibited some reliability issues during development, most notably causing the IIS worker process (w3wp.exe) to increase in memory usage and eventually crash during uploads and synchronizations. For this reason you may want to disable this feature until a.net Framework service pack or future version provides better performance. enablemediaobjectdownload enablemediaobjectzipdownload enablepermalink enableslideshow maxthumbnaillength thumbnailimagejpegquality Specifies whether Gallery Server Pro renders user interface objects to allow a user to download the file for a media object. Typically, this setting is used to control whether a download button is displayed in the toolbar that appears above a media object. Note that setting this value to false does not prevent a user from downloading a media object, since a user already has access to the media object if he or she can view it in the browser. To prevent certain users from viewing media objects (and thus downloading them), user private albums or disable anonymous viewing. Specifies whether users are allowed to download multiple media objects in a ZIP file. Specifies whether Gallery Server Pro renders user interface objects to provide the user with a hyperlink that links directly to the visible media object. This is convenient because AJAX callbacks are used as the user navigates the media objects in an album and the url in the browser's address bar is not updated for each media object. When true, a show permalink button is displayed in the toolbar that appears above a media object. Specifies whether slide show functionality is enabled. When true, a start/pause slideshow button is displayed in the toolbar that appears above a media object. The length of time each image is shown before automatically moving to the next one is controlled by the SlideshowInterval setting. Note that only images are shown during a slide show; other objects such as videos, audio files, and documents are skipped. The length (in pixels) of the longest edge of a thumbnail image. This value is used when a thumbnail image is created. The length of the shorter side is calculated automatically based on the aspect ratio of the image. The quality level that optimized JPG pictures are created with. This is a number from 1-100, with 1 being the worst quality and 100 being Gallery Server Pro 2.3 Administrator s Guide Page 173 of 238

174 the best quality. Not applicable for non-image media objects. thumbnailclickshowsoriginal thumbnailwidthbuffer thumbnailheightbuffer thumbnailfilenameprefix Specifies whether the original image is displayed when the user clicks the thumbnail of an image. If unchecked, the optimized image is shown instead. Not applicable for non-image media objects. The length (in pixels) that is added to the width of the each thumbnail image. A larger number creates more horizontal padding between the image and the border of the thumbnail container. The length (in pixels) that is added to the height of the each thumbnail image. A larger number creates more vertical padding between the image and the border of the thumbnail container. The string that is prepended to the thumbnail file name for each media object. For example, if an image named puppy.jpg is added, and this setting is "zthumb_", the thumbnail image will be named "zthumb_puppy.jpg". NOTE: Any file named "zthumb_puppy.jpg" that already exists will be overwritten, so it is important to choose a value that, when prepended to media object file names, will not conflict with existing media objects. thumbnailpath The path to a directory where Gallery Server should store the thumbnail images of media objects. If no path is specified, the directory containing the original media object is used to store the thumbnail image. The path may be relative to the root of the web application (e.g. \gs\mediaobjects), a full path to a local resource (e.g. C:\mymedia), or a UNC path to a local or network resource (e.g. \\mynas\media). Mapped drives present a security risk and are not supported. The initial and trailing slashes are optional. For relative paths, the directory separator character can be either a forward or backward slash. maxoptimizedlength The length (in pixels) of the longest edge of an optimized image. This value is used when an optimzed image is created. The length of the shorter side is calculated automatically based on the aspect ratio of the image. Not applicable for non-image media objects. optimizedimagejpegquality The quality level that optimized images are stored at (0-100). optimizedimagetriggersizekb optimizedfilenameprefix The size (in KB) above which an image is compressed to create an optimized version. Not applicable for non-image media objects. The string that is prepended to the optimized file name for images. This setting is only used for image media objects where an optimized Gallery Server Pro 2.3 Administrator s Guide Page 174 of 238

175 image file is created. For example, if an image named puppy.jpg is added, and this setting is "zopt_", the optimized image will be named "zopt_puppy.jpg". NOTE: Any file named "zopt_puppy.jpg" that already exists will be overwritten, so it is important to choose a value that, when prepended to media object file names, will not conflict with existing media objects. optimizedpath originalimagejpegquality discardoriginalimageduringimport applywatermark applywatermarktothumbnails The absolute or relative path to a directory on a local hard drive specifying where Gallery Server should store the optimized images of media objects. Relative paths are relative to the root of the web application. The initial and trailing slashes are optional. For relative paths, the directory separator character can be either a forward or backward slash. If no path is specified, the directory containing the original media object is used to store the thumbnail image. UNC or mapped drives are not valid. Not applicable for non-image media objects. The following are all valid and point to the same location (assuming Gallery Server is installed as a web application at C:\inetpub\wwwroot\gsp): "C:\inetpub\wwwroot\gsp\cache\", "C:\inetpub\wwwroot\gsp\cache", "\cache\", "\cache", "cache\", "cache", "/cache/", "/cache" The quality level that original JPG pictures are saved at. This is only used when the original is modified by the user, such as rotation. Not applicable for non-image media objects. Specifies whether to discard the original image when it is added to the gallery. This option, when enabled, helps reduce disk space usage. This option applies only to images, and only when they are added through an upload or by synchronizing. Changing this setting does not affect existing media objects. When false, users still have the option to discard the original image on the Add Objects page by unchecking the corresponding checkbox. Specifies whether to apply a watermark to optimized and original images. If true, the text in the watermarktext property is applied to images, and the image specified in watermarkimagepath is overlayed on the image. If watermarktext is empty, or if watermarkimagepath is empty or does not refer to a valid image, that watermark is not applied. If applywatermarktothumbnails = true, then the watermark is also applied to thumbnails. Specifies whether to apply the text and/or image watermark to thumbnail images. This property is ignored if applywatermark = Gallery Server Pro 2.3 Administrator s Guide Page 175 of 238

176 false. watermarktext watermarktextfontname watermarktextfontsize watermarktextwidthpercent watermarktextcolor watermarktextopacitypercent watermarktextlocation watermarkimagepath Specifies the text to apply to images in the gallery. The text is applied in a single line. The font used for the watermark text. If the font is not installed on the web server, a generic sans serif font will be substituted. Gets or sets the height, in pixels, of the watermark text. This value is ignored if the property watermarktextwidthpercent is non-zero. Valid values are Gets or sets the percent of the overall width of the recipient image that should be covered with the watermark text. The size of the text is automatically scaled up or down to achieve the desired width. For example, a value of 50 means the text is 50% as wide as the recipient image. Valid values are The text is never rendered in a font smaller than 6 pixels, so in cases of long text it may stretch wider than the percentage specified in this setting. A value of 0 turns off this feature and causes the text size to be determined by the watermarktextfontsize property. Specifies the color of the watermark text. The color can be specified as hex (e.g. #336699), RGB (e.g. 127,55,95), or one of the System.Color.KnownColor enum values (e.g. Maroon). The opacity of the watermark text. This is a value from 0 to 100, with 0 being invisible and 100 being solid, with no transparency. Gets or sets the location for the watermark text on the recipient image. This value maps to the enumeration System.Drawing.ContentAlignment, and must be one of the following nine values: TopLeft, TopCenter, TopRight, MiddleLeft, MiddleCenter, MiddleRight, BottomLeft, BottomCenter, BottomRight. Gets or sets the full or relative path to a watermark image to be applied to the recipient image. The image must be in a format that allows it to be instantiated in a System.Drawing.Bitmap object. Relative paths are relative to the root of the web application. The directory separator character can be either a forward or backward slash, and, for relative paths, the initial slash is optional. The following are all valid: "/images/mywatermark.jpg", "images/mywatermark.jpg", "\images\mywatermark.jpg", Gallery Server Pro 2.3 Administrator s Guide Page 176 of 238

177 "images\mywatermark.jpg", "C:\images\mywatermark.jpg" watermarkimagewidthpercent Gets or sets the percent of the overall width of the recipient image that should be covered with the watermark image. The size of the image is automatically scaled to achieve the desired width. For example, a value of 50 means the watermark image is 50% as wide as the recipient image. Valid values are A value of 0 turns off this feature and causes the image to be rendered its actual size. watermarkimageopacitypercent Gets or sets the opacity of the watermark image. Valid values are 0-100, with 0 being completely transparent and 100 completely opaque. watermarkimagelocation send onerror fromname fromaddress toname toaddress smtpserver Gets or sets the location for the watermark image on the recipient image. This value maps to the enumeration System.Drawing.ContentAlignment, and must be one of the following nine values: TopLeft, TopCenter, TopRight, MiddleLeft, MiddleCenter, MiddleRight, BottomLeft, BottomCenter, BottomRight. Specifies whether the Gallery Server Pro administrator (specified in ToName/ ToAddress) is sent a report when a web site error occurs. A valid SMTP server must be specified if this is set to true (attribute SmtpServer). The name associated with the FromAddress address. s sent from Gallery Server will appear to be sent from this person. The address associated with the FromName attribute. s sent from Gallery Server will appear to be sent from this address. The name associated with the ToAddress address. s sent from Gallery Server will be sent to this person. Note that the address is set in the attribute ToAddress. The address associated with the ToName attribute. s sent from Gallery Server will be sent to this address. Note that the name associated with this address is set inthe attribute ToName. Specifies the IP address or name of the SMTP server used to send s. (Examples: , Godzilla, mail.yourisp.com) This value Gallery Server Pro 2.3 Administrator s Guide Page 177 of 238

178 will override the SMTP server setting that may be in the system.net mailsettings section of the web.config file (either explicitly or inherited from a parent web.config file). Leave this setting blank to use the value in web.config or if you are not using the functionality. Note: If you need to specify a username and password for the SMTP server, you should follow these steps: 1. Set the smtpserver and smtpserverport values to blank in galleryserverpro.config. 2. Open web.config in the root of the web application. Add the following section, below the <configuration> element: <system.net> <mailsettings> <smtp> <network host="smtp.yourisp.com" username="soren" password="pwdforsoren" /> </smtp> </mailsettings> </system.net> 3. Set the host value to the SMTP server. Set the username and password to the appropriate values. 4. If using a port other than the default of 25, add a port attribute, like this: <network host=" " username=" " password=" " port="38" /> smtpserverport send usingssl autostartmediaobject Specifies the SMTP server port number used to send s. This value will override the SMTP server port setting that may be in the system.net mailsettings section of the web.config file (either explicitly or inherited from a parent web.config file). Leave this setting blank to use the value in web.config or if you are not using the functionality. Defaults to 25 if not specified here or in web.config. Specifies whether functionality uses Secure Sockets Layer (SSL) to encrypt the connection. Indicates whether a video, audio or other dynamic object will automatically start playing in the user's browser. Gallery Server Pro 2.3 Administrator s Guide Page 178 of 238

179 defaultvideoplayerwidth defaultvideoplayerheight Indicates the default width, in pixels, of the browser object that plays a video file. Typically this refers to the <object> tag that contains the video, resulting in syntax similar to this: <object style="width:640px;height:480px;"... > Indicates the default height, in pixels, of the browser object that plays a video file. Typically this refers to the <object> tag that contains the video, resulting in syntax similar to this: <object style="width:640px;height:480px;"... > defaultaudioplayerwidth Indicates the default width, in pixels, of the browser object that plays an audio file. Typically this refers to the <object> tag that contains the audio file, resulting in syntax similar to this: <object style="width:300px;height:200px;"... > defaultaudioplayerheight Indicates the default height, in pixels, of the browser object that plays an audio file. Typically this refers to the <object> tag that contains the audio file, resulting in syntax similar to this: <object style="width:300px;height:200px;"... > defaultgenericobjectwidth Indicates the default width, in pixels, of the browser object that displays a generic media object. A generic media object is defined as any media object that is not an image, audio, or video file. This includes Shockwave Flash, Adobe Reader, text files, Word documents and others. The value specified here is sent to the browser as the width for the object element containing this media object, resulting in syntax similar to this: <object style="width:640px;height:480px;"... > This setting applies only to objects rendered within the browser, such as Shockwave Flash. Objects sent to the browser via a download link, such as text files, PDF files, and Word documents, ignore this setting. defaultgenericobjectheight Indicates the default height, in pixels, of the browser object that displays a generic media object. A generic media object is defined as any media object that is not an image, audio, or video file. This includes Shockwave Flash, Adobe Reader, text files, Word documents and others. The value specified here is sent to the browser as the width for the object element Gallery Server Pro 2.3 Administrator s Guide Page 179 of 238

180 containing this media object, resulting in syntax similar to this: <object style="width:640px;height:480px;"... > This setting applies only to objects rendered within the browser, such as Shockwave Flash. Objects sent to the browser via a download link, such as text files, PDF files, and Word documents, ignore this setting. maxuploadsize Indicates the maximum size, in kilobytes, of the files that can be uploaded using the Add Objects function. Use this setting to keep users from uploading very large files and to help guard against Denial of Service (DOS) attacks. A value of zero (0) indicates there is no restriction on upload size (unlimited). This value applies to the content length of the entire upload request, not just the file. For example, if this value is 1024 KB and the user attempts to upload two 800 KB images, the request will fail because the total content length is larger than 1024 KB. This setting is not used during synchronization. allowaddlocalcontent allowaddexternalcontent allowanonymousbrowsing pagesize pagerlocation Indicates whether a user can upload a physical file to the gallery, such as an image or video file stored on a local hard drive. The user must also be authenticated and a member of a role with AllowAddMediaObject or AllowAdministerSite permission. This setting is not used during synchronization. Indicates whether a user can add a link to external content such as a YouTube video to the gallery. The user must also be authenticated and a member of a role with AllowAddMediaObject or AllowAdministerSite permission. This setting is not used during synchronization. Indicates whether users can view galleries without logging in. When false, users are redirected to a login page when any album is requested. Indicates the number of objects to display at a time. For example, if an album has more than this number of gallery objects, paging controls appear to assist the user in navigating to them. A value of zero disables the paging feature, allowing all objects to be displayed. Gets or sets the location for the pager used to navigate large collections of objects. This value maps to the enumeration GalleryServerPro.Business.PagerPosition, and must be one of the following values: Top, Bottom, TopAndBottom. This value is ignored Gallery Server Pro 2.3 Administrator s Guide Page 180 of 238

181 when paging is disabled (PageSize = 0). maxnumbererroritems enableselfregistration require validationforselfregis tereduser requireapprovalforselfregisteredu ser use foraccountname defaultrolesforselfregistereduser Indicates the maximum number of error objects to persist to the data store. When the number of errors exceeds this value, the oldest item is purged to make room for the new item. A value of zero means no limit is enforced. Indicates whether anonymous users are allowed to create accounts. Indicates whether verification is required when a user registers an account. When true, the account is initially disabled and an is sent to the user with a verification link. When clicked, user is approved and logged on, unless requireapprovalforselfregistereduser is enabled, in which case an administrator must approve the account before the user can log on. Setting this to true reduces spam activity and guarantees that a valid address is associated with the user. When the setting is false, an address is not required and the user account is immediately created. This setting is ignored when enableselfregistration=false. Indicates whether an administrator must approve newly created accounts before the user can log on. When true, the account is disabled until it is approved by an administrator. When a user registers an account, an is sent to each user specified in userstonotifywhenaccountiscreated. Only users belonging to a role with AllowAdministerSite permission can approve a user. If require validationforselfregistereduser is enabled, the requesting administrator approval is not sent until the user verifies the address. This setting is ignored when enableselfregistration=false. Indicates whether account names are primarily addresses. When true, certain forms, such as the self registration wizard, assume addresses are used as account names. For example, when this value is false, the self registration wizard includes fields for both an account name and an address, but when true it only requests an address. This setting is ignored when enableselfregistration=false. A comma-delimited list of roles to assign when a user registers a new account. This setting is ignored when enableselfregistration=false and when an account is created by an administrator. Ex: "ReadOnly,NoWatermark" Gallery Server Pro 2.3 Administrator s Guide Page 181 of 238

182 userstonotifywhenaccountiscreat ed enableuseralbum useralbumparentalbumid useralbumnametemplate useralbumsummarytemplate redirecttouseralbumafterlogin jqueryscriptpath A comma-delimited list of account names of users to receive an notification when an account is created. When require validationforselfregistereduser is enabled, the is not sent until the user verifies the address. Ex: "Admin, Billybob". Applies whether an account is self-created or created by an administrator. Indicates whether each user is assigned owner to a unique album. The title of the album is based on the template in the useralbumnametemplate property. The album is created when the account is created or if the album does not exist when the user logs on. It is created in the album specified in the useralbumparentalbumid property. Specifies the ID of the album containing user albums. This setting is ignored when enableuseralbum is false. This property may have a value of zero (0) when user albums are disabled. Specifies the template to use for naming the album that is created for new users. Applies only when enableuseralbum is true. The placeholder string {UserName}, if present, is replaced by the account name. Specifies the template to use for the album summary of a newly created user album. Applies only when enableuseralbum is true. No placeholder strings are supported. Indicates whether to redirect the user to his or her album after logging in. If set to false, the current page is re-loaded or, if there isn't a page, the user is shown the top level album for which the user has view access. This setting is ignored when EnableUserAlbum is false. The absolute or relative path to the jquery script file. Relative paths can be relative to the root of the web site (e.g. /mysites/mygallery/gs/script/jquery min.js) or relative to the directory containing the Gallery Server Pro user controls and other resources (e.g. /script/jquery min.js). It is NOT VALID to specify a path relative to the root of the web application. For relative paths the initial slash is optional and the directory separator character can be either a forward or backward slash. Absolute paths should be a full URI (e.g. It is not valid to specify a UNC path, mapped drive path, or path to the Gallery Server Pro 2.3 Administrator s Guide Page 182 of 238

183 local file system (e.g. "C:\scripts\jquery.js"). productkey Specifies the product key for this installation of Gallery Server Pro. The product key can be generated by the Product Key Wizard at HTML template configuration settings Following the core element in galleryserverpro.config is the galleryobject element. This section contains settings for controlling how HTML is rendered to the browser for various types of media objects. A full discussion is in the Rendering Media Objects in the Browser section. MIME types configuration settings The file galleryserverpro.config contains a list of file types that are managed by Gallery Server Pro. This list is exposed through the Media Object Types page in the Site administration console. (Click Site admin in the Actions menu, then click Media Object Types in the menu on the left.) The Media Object Types page allows one to review the list of file types Gallery Server Pro is configured to manage. Each type can be enabled or disabled as desired. However, the Media Object Types page does not allow adding new mime types or editing existing ones (except for enabling or disabling). For advanced configuration options, you can edit this data directly in galleryserverpro.config. Below is an example of one of the mime types in the file. <mimetype fileextension=".jpeg" browserid="default" type="image/jpeg" allowaddtogallery="true" /> The mimetype element provides mapping information between a file extension, its associated mime type, and the family of browsers to which it applies. Each mime type is uniquely identified by the fileextension and browserid attributes. If the combination of fileextension and browserid values are specified more than once within the mimetypes collection, only the first element is used (subsequent ones are ignored). Each fileextension may be listed more than once, but there must always be one entry where browserid = "default", and it must be listed prior to any other elements with the same fileextension. The type attribute may be used multiple times (e.g. "image/jpeg" is used for both.jpg and.jpeg extensions). The type attribute holds the MIME type of the file extension. The browsermimetype attribute holds the MIME type that should be sent to the browser. If the browsermimetype attribute is omitted, the MIME type specified in the type attribute is used instead. Use the browsermimetype attribute for certain types of objects where the browser does not understand the standard MIME type. Example: Imagine you want Gallery Server to play WAV files in the browser. WAV files have a MIME type of audio/wav. But most, and possibly all, browsers do not understand this value, so HTML like this does not work: Gallery Server Pro 2.3 Administrator s Guide Page 183 of 238

184 <object type='audio/wav' >... </object> Instead, browsers require this: <object type='application/x-mplayer2'>... </object> Therefore, we need to specify the.wav mime type like this: <mimetype fileextension=".wav" type="audio/wav" browserid="default" browsermimetype="application/x-mplayer2" allowaddtogallery="true" /> What if the above solution worked for most browsers, but Internet Explorer 5.0 required "application/x-mplayer"? Add an additional mimetype element specifying the new value for the IE 5.0 browser: <mimetype fileextension=".wav" type="audio/wav" browserid="ie50" browsermimetype="application/x-mplayer" allowaddtogallery="true" /> IMPORTANT: The MIME type for browserid="default" must appear before more specific browser IDs (if there are any). An error will occur if a non-default value is encountered before the default value for a particular file extension. The browserid attribute must be a valid browser specified in the.net Framework's.browser files. See for a hierarchical list of IDs recognized by.net Framework 2.0. If the client's browser matches multiple browser elements (e.g. "ie" and "default"), the most specific browser element is preferred (in this example "ie"). Thus you can specify a browser element with id="default" containing the default HTML for a particular type of media object. Create additional browser elements to handle individual browsers as desired. Data store configuration settings The datastore element in galleryserverpro.config stores configuration information about the data store. For example, if a SQL Server database is being used, these values are used by Gallery Server to set up the Command objects that communicate with the database. Configuration setting albumtitlelength albumdirectorynamelength albumsummarylength Description The maximum allowed string length for an album title. The maximum length for a directory name in the media objects library. Each directory name matches the title of the matching album, with the following exceptions: (1) Characters that are not valid for directory names are removed, and (2) the name is shortened (if necessary) to the maximum length specified here. The maximum allowed string length for an album summary. Gallery Server Pro 2.3 Administrator s Guide Page 184 of 238

185 mediaobjecttitlelength mediaobjectfilenamelength mediaobjecthashkeylength mediaobjectexternalhtmlsourcele ngth mediaobjectexternaltypelength mediaobjectmetadatadescriptionl ength mediaobjectmetadatavaluelength rolenamelength ownedbylength ownerrolenamelength createdbylength lastmodifiedbylength errorextypelength The maximum allowed string length for a media object title (caption). The maximum length allowed for a media object file name. This must be the smaller of the restrictions set by the operating system and the corresponding data types in the data store (ThumbnailFileName, OptimizedFileName, OriginalFileName). The maximum length of the hash key generated for each media object. Gallery Server generates 47-character hash keys, so this value must be greater than or equal to 47. This setting is used only by the SQL Server provider. The maximum allowed string length for a media object's external HTML source data. This setting is used only by the SQL Server provider. The maximum allowed string length for a media object's external type. This setting is used only by the SQL Server provider. The maximum allowed string length for a meta data description. This setting is used only by the SQL Server provider. The maximum allowed string length for a meta data value. This setting is used only by the SQL Server provider. The maximum allowed string length for a role name. This setting is used only by the SQL Server provider. The maximum allowed string length for the owned by user name. This setting is used only by the SQL Server provider. The maximum allowed string length for the owner role name. This setting is used only by the SQL Server provider. The maximum allowed string length for the created by user name. This setting is used only by the SQL Server provider. The maximum allowed string length for the last modified by user name. This setting is used only by the SQL Server provider. The maximum allowed string length for the exception type. This setting is used only by the SQL Server provider. Gallery Server Pro 2.3 Administrator s Guide Page 185 of 238

186 errorexmsglength errorexsourcelength errorurllength The maximum allowed string length for the exception message. This setting is used only by the SQL Server provider. The maximum allowed string length for the exception source. This setting is used only by the SQL Server provider. The maximum allowed string length for the URL that caused the exception. This setting is used only by the SQL Server provider. Data provider configuration settings This section stores configuration information about the data provider used by Gallery Server. It looks similar to this: <dataprovider defaultprovider=" SQLiteGalleryServerProProvider "> <providers> <clear /> <add applicationname="gallery Server Pro" connectionstringname="sqlitedbconnection" name="sqlitegalleryserverproprovider" type="galleryserverpro.data.sqlite.sqlitegalleryserverproprovider" /> <add applicationname="gallery Server Pro" name="sqldataprovider" type="galleryserverpro.data.sqlserver.sqldataprovider" /> </providers> </dataprovider> This example specifies the data provider is a class called SQLiteGalleryServerProProvider in the GalleryServerPro.Data.SQLite namespace, which is in a DLL named GalleryServerPro.Data.SQLite.dll. You may specify any provider that uses GalleryServerPro.Provider.DataProvider as its base class (which in turn inherits the.net class System.Configuration.Provider.ProviderBase and implements the custom interface GalleryServerPro.Provider.Interfaces.IDataProvider). 8. Working with Galleries Overview Gallery Server Pro supports multiple galleries. A gallery encompasses all the media objects associated with a single web application. Each web application has one gallery. However, there can be multiple installations of Gallery Server Pro on a web server, with each specifying a different gallery. The albums and media objects within each gallery are not visible to other galleries. The list of user accounts and roles can be shared across galleries or separated depending on your requirements. A single SQL Server database can store data for an unlimited number of galleries. Gallery Server Pro 2.3 Administrator s Guide Page 186 of 238

187 Galleries are useful for setting up hosted solutions where individuals require administrative permission to separate groups of media objects. They are also useful when site-wide settings, such as watermarking, need to be applied to multiple groups of albums and media objects. For example, one can set up a gallery at and another at Each gallery is set up with its own membership, where user Robert is the administrator for his site and user Susan is the administrator for the other. Robert and Susan manage each of their galleries, but neither has permission to the other gallery. Robert cannot view any of Susan s media objects from his URL and vice versa. Robert can enable any site-wide setting such as watermarking and thumbnail length without affecting Susan s site. Even though the two sites appear as completely separate web applications, both can share the same data store. This simplifies the management of Gallery Server Pro, and offers greater value to customers who pay hosting providers on a per-database policy. By default, Gallery Server Pro is installed with a gallery ID = 1. The gallery ID is managed on the Site settings General page in the Site administration console. SQLite users The concept of galleries is useful when groups of media objects must be kept separate and the data must be stored in a single SQL Server database. Starting with 2.1, you can store data in a SQLite database that is locally stored within the web application. Since each web application has its own SQLite database (and therefore list of user accounts and gallery data), it is not necessary to follow these directions for creating multiple galleries. Instead, just run the install wizard in each web application. Each web application is completely self contained and does not have access to the other. If you want to share a single set of user accounts across multiple web applications, then use SQL Server or store your SQLite database file in a shared location and then update your web.config file in each web application to point to this file (galleryserverpro_data.sqlite). SQL Server users To set up an additional instance of Gallery Server Pro to use a different gallery than the default, follow these steps. 1. Copy the web application files for Gallery Server Pro from the original instance and save them to a new location on the web server s hard drive. Do not copy any media files that may be in the mediaobjects directory. 2. Use IIS to configure the directory as a web application. 3. Open the home page for the new application in a web browser. Log on to the application as an administrator and click Site admin from the Actions menu. The Site Settings - General page appears. Gallery Server Pro 2.3 Administrator s Guide Page 187 of 238

188 4. Change the gallery ID to a new value, such as 2. Click Save changes. Behind the scenes, Gallery Server Pro updated the galleryid property in the configuration file galleryserverpro.config. 5. Click the root album in the breadcrumb menu (usually named All albums). You will probably see a screen similar to the following. * Behind the Scenes* The first time a page is clicked after the galleryserverpro.config file is updated, the Gallery Server Pro web application restarts, using the new values in the config file. Special startup code runs that checks for basic data integrity in the data store. This includes verifying that a record exists in the gallery table for the current gallery (table gs_gallery), a root album exists in the album table (gs_album), and that each role is linked to the current gallery (table gs_role). In this case, when a new gallery ID is specified, Gallery Server Pro will add a record to gs_gallery, a record to gs_album, and as many records to gs_role as there are roles in the roles provider. However, for security reasons, Gallery Server Pro does not give any of the roles permission to the root album, so no accounts will have access to the new gallery until one of the tables is manually updated (explained below). 4. If the message Insufficient permission appears, don t panic. The security system is working properly. Use SQL Management Studio (SQL 2005/2008) or Enterprise Manager (SQL 2000) to open the table gs_role in the Gallery Server Pro database. 5. You need to give Administer site permission to a role. Search the records in the table gs_role until you find one where the FKGalleryId column matches the new gallery ID and the RoleName field contains a role that should have Administer site permission to the new gallery. For this record, set the AllowAdministerSite field to true. (A default installation of Gallery Server Pro creates a role named System Administrator with this permission, so if this role exists in your installation you will look for the record where RoleName = System Administrator and FKGalleryId = 2.) 6. Since Gallery Server Pro uses caching to retain a list of roles and permissions, the cache must be cleared by restarting the web application. This can be done by recycling the application pool in IIS or by entering the text iisreset in a Start-Run dialog box. 6. Now click the All albums link to open the root album. It should be empty, as shown below. Gallery Server Pro 2.3 Administrator s Guide Page 188 of 238

189 7. The new gallery is ready to go! Add new albums and media objects. Notice they do not appear in the original gallery (gallery ID = 1), even though both galleries use the same database. Note: If your original gallery was configured to store media objects at an absolute path such as C:\MyMedia rather than a relative path such as gs\mediaobjects, then be sure to update the media objects path in the new gallery to a different location. You don't want both galleries storing files in the same directory. Creating a read-only gallery Gallery Server Pro helps you share and manage your media collection over the web. In some cases you may not want to allow it to make any changes to your media files. In other words, you want Gallery Server Pro to expose a read-only view of your collection. When Gallery Server Pro is in read-only mode, users cannot create albums or upload files, nor can they move, copy or delete albums and media objects. In other words, they can't perform any action that modifies the original media files. However, users can synchronize, download, rearrange and edit captions, and administrators can change settings in the Site admin area, including managing users and roles. A read-only gallery is configured on the Media Objects - General page in the Site admin area, as seen here: Gallery Server Pro 2.3 Administrator s Guide Page 189 of 238

190 Must be disabled Must be different than original file location There are several requirements that must be met before a gallery can be made read-only: User albums must be disabled The directory for the thumbnail and compressed images must be different than the original media objects directory The option Synchronize directory names with album titles must be disabled When a gallery is read-only, the only way to add or remove media objects is by manually updating the media objects directory with a tool like Windows Explorer and then running the synchronize function. Gallery Server Pro 2.3 Administrator s Guide Page 190 of 238

191 If this setting is enabled, it is recommended to configure the IIS application pool identity to have read-only access to the media objects directory as an additional safeguard. This helps guarantee that the web application cannot manipulate the media files. 9. Membership Configuration Membership overview Note: This section contains advanced information on customizing how Gallery Server Pro manages users and roles. If you are using the default configuration, you can skip this section. Gallery Server Pro uses the ASP.NET Provider model for storing users, roles, profiles, and gallery data. By default, the installer configures a set of tables for storing this data. However, Gallery Server Pro can take advantage of an existing Membership schema in the database, in another database, or it can use an entirely different data store through the use of alternate membership providers such as ActiveDirectoryMembershipProvider or even one you write yourself. We ll discuss setting up Gallery Server Pro in the following scenarios: Store users and roles in a new set of tables in the same SQL Server database as Gallery Server Pro, Store users and roles in an existing membership schema in the same SQL Server database as Gallery Server Pro, Store users and roles in an existing membership schema in a different SQL Server database than Gallery Server Pro, and Using a membership provider other than SQL Server or SQLite. Note: Although these scenarios assume you are using SQL Server, you can also achieve the same configuration with SQLite. New membership in current SQL database The simplest scenario, and the one Gallery Server Pro uses by default, is to let the web installer set up the tables, stored procedures, and views necessary for storing users and roles in the same database that Gallery Server Pro uses for its data. Run the web installer. SQL Server users should make sure the Script ASP.NET Membership option is checked. (If you specified SQLite, you do not have this option.) After the installation is complete, Gallery Server Pro is properly configured and ready to run. You can log in with the administrator account you specified in the installer. Gallery Server Pro 2.3 Administrator s Guide Page 191 of 238

192 Use existing membership schema in current SQL database Since all data objects used by Gallery Server Pro have names beginning with a gs_ prefix, you can install Gallery Server Pro in an existing database used by other applications. If this database already has the ASP.NET Membership installed, you can configure Gallery Server Pro to use it. When using an existing membership schema, there are two scenarios: You want Gallery Server Pro to use its own set of user accounts and roles. You want Gallery Server Pro to use the same set of users and roles as another application. For example, you may be using DotNetNuke and you want users to use their DotNetNuke accounts to log in to Gallery Server Pro. Use a new set of users and roles, same database 1. Run the web installer, making sure to uncheck the option Script ASP.NET Membership. 2. If the installer instructs you to update the connection string in web.config when it finishes, do so. After the installation is complete, Gallery Server Pro is properly configured and ready to run. You can log in with the administrator account you specified in the installer. Use an existing set of users and roles, same database 1. Run the web installer, making sure to uncheck the option Script ASP.NET Membership. Note: Since you will be using an existing set of users and roles, you will end up not using the administrator account requested on the last step of the web installer. You can forget whatever you enter on that step. 2. If the installer instructs you to update the connection string in web.config when it finishes, do so. Do not click the link to take you to the gallery. We need to do a couple of things first. 3. Open web.config in the root of the Gallery Server Pro web application and look for three instances of applicationname="gallery Server Pro" (one each for the membership, role, and profile providers). Replace Gallery Server Pro with the name of the application with which you are sharing membership. You can find this in the other application s web.config file. If the provider is SQL Server, you can also look it up in the table aspnet_applications. Note: At this point you are able to log in to Gallery Server Pro with any user that exists in the application, but you won t get very far, because users have not yet been given access to any albums. That is, you can authenticate but you don t have any authorization. 4. Decide which existing role will be the system administrator role for Gallery Server Pro (create one with the other application if necessary). Then open the table gs_role and add a record for this role. Set all true/false fields to true. The FKGalleryId field must match the GalleryId field in config/galleryserverpro.config (the default is 1). 5. Now you can click the link on the last step of the web installer to go to your gallery. You can log in with any user that belongs to the system administrator role you chose in the last step. Gallery Server Pro 2.3 Administrator s Guide Page 192 of 238

193 If you navigate to the Manage Users or Manage Roles web administration pages of Gallery Server Pro, you will see a list of all users and roles for the application you specified in step 3. You can assign permissions as desired to give additional users and roles permission to Gallery Server Pro. Use existing membership schema in different SQL database You can configure Gallery Server Pro to use an ASP.NET Membership schema installed in another SQL database on your server or network. For example, you may want Gallery Server Pro to use the same set of users and roles as an existing application, or you may have a dedicated database for storing membership data. When using an existing membership schema, there are two scenarios: You want Gallery Server Pro to use its own set of user accounts and roles. You want Gallery Server Pro to use the same set of users and roles as another application. For example, you may be using DotNetNuke and you want users to use their DotNetNuke accounts to log in to Gallery Server Pro. Use a new set of users and roles, different database 1. Run the web installer, making sure to uncheck the option Script ASP.NET Membership. 2. If the installer instructs you to update the connection string in web.config when it finishes, do so. 3. Open web.config in the root of the Gallery Server Pro web application and add a connection string that points to the database where membership data reside. Make sure you give it a unique name, such as MembershipDbConnection. 4. Update the connection string name for the membership, role, and profile sections in web.config. Look for three instances of connectionstringname="sqlserverdbconnection". Replace SqlServerDbConnection with the name of the connection string you added in the previous step. Note: If you selected the SQLite database during installation, the connection string is named SQLiteDbConnection. 5. Create a role that will be the system administrator role for Gallery Server Pro. Then create a user and assign the user to this role. For example, the role may be System Administrator and the user is Admin. One way to do this is to use the Web Site Configuration Tool that is included with Visual Studio. Using this tool is beyond the scope of this document, but online information is easily found. 6. Now you can click the link to the Gallery Server Pro home page that is on the last step of the web installer. You can log in with the user you created in the previous step. Use an existing set of users and roles, different database 1. Run the web installer, making sure to uncheck the option Script ASP.NET Membership. Note: Since you will be using an existing set of users and roles, you will end up not using the administrator account requested on the last step of the web installer. You can forget whatever you entered on that step. Gallery Server Pro 2.3 Administrator s Guide Page 193 of 238

194 2. If the installer instructs you to update the connection string in web.config when it finishes, do so. Do not click the link to take you to the gallery. We need to do a couple things first. 3. Open web.config in the root of the Gallery Server Pro web application and add a connection string that points to the database where membership data reside. Make sure you give it a unique name, such as MembershipDbConnection. 4. Update the connection string name for the membership, role, and profile sections in web.config. Look for three instances of connectionstringname="sqlserverdbconnection". Replace SqlServerDbConnection with the name of the connection string you added in the previous step. Note: If you selected the SQLite database during installation, the connection string is named SQLiteDbConnection. 5. Now look for three instances of applicationname="gallery Server Pro" (one each for the membership, role, and profile providers). Replace Gallery Server Pro with the name of the application with which you are sharing membership. You can find this in the application s web.config file. If the provider is SQL Server, it is also stored in the table aspnet_applications. Note: At this point you can log in to Gallery Server Pro with any user that exists in the application, but you won t get very far, because users have not yet been given access to any albums. That is, you can authenticate but you don t have any authorization. 6. Decide which existing role will be the system administrator role for Gallery Server Pro (create one with the other application if necessary). Open the table gs_role and add a record for this role. Set all true/false fields to true. The FKGalleryId field must match the GalleryId field in config/galleryserverpro.config (the default is 1). 7. Now you can click the link on the last step of the web installer to go to your gallery. You can log in with any user that belongs to the system administrator role you chose in the last step. If you navigate to the Manage users or Manage roles web administration pages of Gallery Server Pro, you will see a list of all users and roles for the application you specified in step 5. You can assign permissions as desired to give additional users and roles permission to Gallery Server Pro. Integrate Gallery Server Pro with Active Directory In this section I describe how to modify a default installation of Gallery Server Pro to use Active Directory for user management. Step 1: Configure basic AD integration The first step in Active Directory configuration is to modify the web.config file in the root of the Gallery Server Pro application. Add a connection string that points to your Active Directory: <connectionstrings> <add name="adconnection" connectionstring="ldap:// /cn=users,dc=mydomain,dc=techinfosystems,dc=com "/> Gallery Server Pro 2.3 Administrator s Guide Page 194 of 238

195 </connectionstrings> The value is the IP address of the domain controller. You can also specify the Fully Qualified Domain Name (ex. mydomain.techinfosystems.com), the Relative Distinguished Name (ex. godzilla if that is the name of your DC); or for more redundancy you can specify just the domain name (ex. mydomain). Whichever you choose just be sure you can ping it. The next step is to remove or comment out the existing membership configuration. Comment it out by adding <!-- to the beginning and --> to the end, like this: <!-- <membership defaultprovider="sqlitemembershipprovider"> <providers> <clear /> <add applicationname="gallery Server Pro" passwordformat="clear" minrequirednonalphanumericcharacters="0" minrequiredpasswordlength="2" maxinvalidpasswordattempts="2" enablepasswordreset="true" enablepasswordretrieval="true" passwordattemptwindow="10" requiresquestionandanswer="false" requiresunique ="false" connectionstringname="sqlitedbconnection" name="sqlitemembershipprovider" type="galleryserverpro.data.sqlite.sqlitemembershipprovider" /> <add applicationname="gallery Server Pro" passwordformat="encrypted" minrequirednonalphanumericcharacters="0" minrequiredpasswordlength="2" maxinvalidpasswordattempts="50" enablepasswordreset="true" enablepasswordretrieval="true" passwordattemptwindow="10" requiresquestionandanswer="false" requiresunique ="false" connectionstringname="sqlserverdbconnection" name="sqlmembershipprovider" type="system.web.security.sqlmembershipprovider" /> </providers> </membership> --> Now add the new membership info for Active Directory: <membership defaultprovider="aspnetactivedirectorymembershipprovider"> <providers> <add name="aspnetactivedirectorymembershipprovider" type="system.web.security.activedirectorymembershipprovider, System.Web,Version= ,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" connectionstringname="adconnection" enablesearchmethods="true"/> </providers> </membership> The version number must match the one installed on your web server, so update it as needed. Some examples I saw on the internet used instead of Make sure the connection string name matches the name you specified in the connection string definition. The enablesearchmethods attribute is required so that Gallery Server Pro can retrieve a list of all users on the user management page. Gallery Server Pro 2.3 Administrator s Guide Page 195 of 238

196 Now, at this point you should be able to log on to Gallery Server with your domain account, but you will receive the following message: This is because your user account is not a member of any roles in Gallery Server Pro. Recall that when you installed Gallery Server Pro, a role named System Administrator was created with administrative permission. Now you need to add one or more AD users to this role. But how do you do this when no one has authorization to perform this task? If you are using IIS 7, the answer is easy. Open up IIS Manager, navigate to the Gallery Server Pro web app, and click.net Users. A list of your AD users appears. Double click the one that you want to be the administrator, and add the user to the System Administrator role in the dialog box. The next time you log on to Gallery Server Pro you will have administrative access. For IIS 6 and earlier users, the task is more difficult because those versions don't provide a means for accessing the users. However, all versions of Visual Studio 2005 and higher - including the free Express versions - provide the Web Site Administration Tool, which allows you to edit the roles for users. Using this tool is beyond the scope of this document, but online information can be found. Use this tool to add one of the users to the System Administrator role. At this point you should be able to log on using your AD account. Use the syntax user@fully_qualified_domain_name, such as Roger@mydomain.techinfosystems.com. Later I'll show you how can get change it to just the username. Step 2: Create, edit and delete AD accounts within Gallery Server Pro Once you are logged on as an administrator, you can go to the Manage Users page and add the remaining AD accounts to appropriate roles. If the IIS user account does not have permission to make changes to AD, you may receive an error like this when you click Save changes: "Cannot update user. General access denied error" You will get this error because the IIS process identity does not have permission to modify AD data. To get around this, you have two choices: 1. Specify a domain account in web.config that has the necessary permission. Open web.config and add connectionusername and connectionpassword attributes to the provider definition, like this: <membership defaultprovider="aspnetactivedirectorymembershipprovider"> <providers> Gallery Server Pro 2.3 Administrator s Guide Page 196 of 238

197 <add name="aspnetactivedirectorymembershipprovider" type="system.web.security.activedirectorymembershipprovider, System.Web,Version= ,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" connectionstringname="adconnection" enablesearchmethods="true" connectionusername="rmartin" connectionpassword="mypassword"/> </providers> </membership> Note that putting an AD account name and password in a plain text file is a security risk. If you go this route, I HIGHLY recommend you encrypt the web.config file. Here are two links where you can learn more: How To: Encrypt Configuration Sections in ASP.NET 2.0 Using DPAPI Video: How Do I: Encrypt My Web.Config File? 2. Specify an account for the IIS application pool process identity that has the necessary AD permission. I prefer this over the first solution. Once the permissions are sorted out, you have the potential to create, edit and delete users. Remember that adding a user creates a new account in Active Directory and deleting an account removes it! Obviously this can be abused in a way that affects your entire domain, so use caution. For this reason, you may actually prefer to revert to read-only permissions and handle role membership via IIS 7 Manager (or the Web Site Administration Tool for IIS 5-6). Options Log on with simple username instead of fully qualified name Your users might prefer logging on with just the user name rather than the fully qualified name. That is, instead of typing Roger@mydomain.techinfosystems.com, you enter Roger. To enable this feature, add the attributemapusername to the membership configuration: <membership defaultprovider="aspnetactivedirectorymembershipprovider"> <providers> <add name="aspnetactivedirectorymembershipprovider" type="system.web.security.activedirectorymembershipprovider, System.Web,Version= ,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" connectionstringname="adconnection" enablesearchmethods="true" attributemapusername="samaccountname" /> </providers> </membership> By setting attributemapusername to samaccountname, you can log on with just the username, such as Roger in the previous example. Gallery Server Pro 2.3 Administrator s Guide Page 197 of 238

198 Additional provider options The AspNetActiveDirectoryMembershipProvider provider includes several attributes I haven't mentioned. These attributes configure various logon and password options. Be sure to check them out if you want more control. Additional notes Can't use Windows groups If you are using AD, you probably use Windows groups to control permissions. You may have a Marketing group whose members have read/write access to the marketing shared folder but read only access to the Development and Engineering folders. Wouldn't it be nice if you could map albums in Gallery Server to your groups, so that the Marketing users would have control over the Marketing album, Developers have the Dev album, and so on? On the surface, it seems we can just use the WindowsTokenRoleProvider instead of the SqlRoleProvider. However, if one tries this, the following error occurs during application startup: "The configured Role Provider (WindowsTokenRoleProvider) relies upon Windows authentication to determine the groups that the user is allowed to be a member of. ASP.NET Role Manager cannot be used to manage Windows users and groups. Please use the SQLRoleProvider if you would like to support custom user/role assignment." This error is generated when Gallery Server Pro tries to get a list of all roles with the Roles.GetAllRoles() method, and the WindowsTokenRoleProvider does not support it. Unfortunately, Gallery Server cannot do its job unless it can get a list of the roles, so for the time being we cannot take advantage of the Windows groups. If anyone discovers a way around this, let us know. Can't auto-logon users Back in my classic ASP days I built an intranet app that automatically recognized the Windows account the user was logged on with. No separate logon inside the web app was required. For reasons I don't understand, I cannot accomplish the same thing with ASP.NET Membership. Sure, you can disable anonymous authentication, enable Windows authentication, and turn on impersonation in web.config. Doing this *does* allow Gallery Server Pro to automatically log on users, but it doesn't think the user is in any roles, and there doesn't seem to be any way to configure roles for the user. Let us know if you know a way around this. Can't reset or change password on other accounts I didn't spend much time investigating this, but it appears you can't use Gallery Server Pro to reset or change another user's password. I received error messages when I tried. You *can*, however, change your own password. Gallery Server Pro 2.3 Administrator s Guide Page 198 of 238

199 10. Data Provider About the data provider model Gallery Server Pro implements the ASP.NET provider model for data and membership access. The Membership Configuration section discusses the membership provider, and this section focuses on the data provider. The beauty of the provider model is that it does not restrict the data storage technology. This allows Gallery Server Pro to use any source for its data storage as long as a provider is written for it. Gallery Server Pro contains two providers - SQL Server and SQLite. Additional providers can be written that use MySQL, Oracle, Microsoft Access, or even an XML file as the data store. Moving data between SQL Server and SQLite Recall that gallery data, such as file names, extracted metadata, and captions are stored in a SQL Server or SQLite database. The media files are not stored in the database - they reside in your media objects directory (named mediaobjects by default and is in the web application directory). Moving data from SQL Server to SQLite - or the other way around - involves these basic steps: 1. Export all gallery data to a backup file using the backup function. 2. Run the installer, choosing the new data provider. 3. Restore the backup file using the restore function. Below are detailed instructions for moving data from SQL Server to SQLite. Read the notes below for moving data from SQLite to SQL Server. Note: SQLite cannot be used if the web application is running at Medium Trust, unless the file System.Data.SQLite.dll is placed in the global assembly cache (GAC). 1. Before starting, make sure you are running version Gallery Server Pro 2.1 or higher. Upgrade if necessary. 2. Open the Backup/Restore page by clicking Actions - Site Admin, then Backup/Restore from the menu on the left. 3. Create a backup file and save it to your hard drive (instructions in the section Using the Built-In Backup Function). 4. Use a web browser to launch the Install Wizard. For example, if you installed to then enter On the Select Data Provider step, choose the database you are migrating to. Follow the wizard to set up the database structure. When ASP.NET does not have permission to edit web.config or galleryserverpro.config, you will receive a message on the Select Data Provider step of the wizard. This typically occurs when the IIS application pool process identity does not have modify permission to the directory containing the files. If you are unable to provide these permissions, you can manually edit these files. Read the section Behind the scenes: how the data provider is specified in the config files. Gallery Server Pro 2.3 Administrator s Guide Page 199 of 238

200 5. Restore the data from the backup file (see Using the built-in restore function for more information). 6. When the restore process is finished, you may browse the gallery to verify your objects are still there. Nothing should look different, except any changes you make will now occur in the new database. Note: Your current login account may no longer be valid since it was deleted during the restore. If this occurs, log out and log in using an account that was in the backup file. Behind the scenes: how the data provider is specified in the config files Hopefully you don't have to bother reading this section, but if you have any trouble with the installation or upgrade, you may need to manually configure the data provider in the web.config and galleryserverpro.config files. Typically this will occur when the IIS application pool process identity does not have NTFS permission to modify the files. By default, the user account is the ASPNET user in IIS 5 and 5.1, Network Service in IIS 6 and 7, and IIS AppPool\DefaultAppPool in IIS 7.5. You can often resolve this by giving this user 'modify' permission to the web directory containing Gallery Server Pro. Refer to the section Configuring NTFS Permissions In Microsoft Windows for more information. Gallery Server Pro provides a choice of storing data in SQL Server or SQLite. There are four types of data: Provider Config file Description Membership web.config User accounts Roles web.config Roles define the security context of users, such as which albums they are allowed to view Profile web.config Preferences associated with users, such as whether the Image Metadata popup is displayed Gallery data galleryserverpror.config Image and album captions, extracted metadata, and other data associated with the media objects Web.config file As the table above shows, the data providers for Membership, Roles, and Profile are stored in the web.config file, located in the root of the Gallery Server Pro web application. A web.config file is a standard file used in all ASP.NET applications, and it stores various configuration settings. Here is what the Membership, Roles, and Profile section looks like: <!-- Configure the Membership provider.--> <membership defaultprovider="sqlitemembershipprovider"> <providers> <clear /> <add applicationname="gallery Server Pro" passwordformat="clear" minrequirednonalphanumericcharacters="0" minrequiredpasswordlength="2" maxinvalidpasswordattempts="50" enablepasswordreset="true" enablepasswordretrieval="true" Gallery Server Pro 2.3 Administrator s Guide Page 200 of 238

201 passwordattemptwindow="10" requiresquestionandanswer="false" requiresunique ="false" connectionstringname="sqlitedbconnection" name="sqlitemembershipprovider" type="galleryserverpro.data.sqlite.sqlitemembershipprovider" /> <add applicationname="gallery Server Pro" passwordformat="encrypted" minrequirednonalphanumericcharacters="0" minrequiredpasswordlength="2" maxinvalidpasswordattempts="50" enablepasswordreset="true" enablepasswordretrieval="true" passwordattemptwindow="10" requiresquestionandanswer="false" requiresunique ="false" connectionstringname="sqlserverdbconnection" name="sqlmembershipprovider" type="system.web.security.sqlmembershipprovider" /> </providers> </membership> <!-- Configure the Role provider.--> <rolemanager enabled="true" cacherolesincookie="true" cookieprotection="validation" defaultprovider="sqliteroleprovider"> <providers> <clear /> <add applicationname="gallery Server Pro" connectionstringname="sqlitedbconnection" name="sqliteroleprovider" type="galleryserverpro.data.sqlite.sqliteroleprovider" /> <add applicationname="gallery Server Pro" connectionstringname="sqlserverdbconnection" name="sqlroleprovider" type="system.web.security.sqlroleprovider" /> </providers> </rolemanager> <!-- Configure the Profile provider.--> <profile defaultprovider="sqliteprofileprovider"> <providers> <clear /> <add applicationname="gallery Server Pro" connectionstringname="sqlitedbconnection" name="sqliteprofileprovider" type="galleryserverpro.data.sqlite.sqliteprofileprovider" /> <add applicationname="gallery Server Pro" connectionstringname="sqlserverdbconnection" name="sqlprofileprovider" type="system.web.profile.sqlprofileprovider" /> </providers> <properties> <add name="showmediaobjectmetadata" defaultvalue="false" type="string" allowanonymous="true" /> </properties> </profile> Gallery Server Pro 2.3 Administrator s Guide Page 201 of 238

202 It isn't too hard to figure it out when you study it for a couple minutes. Probably the most important attribute to understand is the defaultprovider attribute. Each provider section - Membership, Role, and Profile - specifies a defaultprovider. By default it is configured to use the SQLite providers - SQLiteMembershipProvider, SQLiteRoleProvider, and SQLiteProfileProvider. Each provider is configured in detail just below, in the <add /> element. To configure Gallery Server Pro to use SQL Server instead of SQLite, edit the defaultprovider for each of the three providers to specify the SQL Server provider. You can copy the provider name from the <add /> element within it that defines the SQL Server provider. When you are done, it will look like this: <membership defaultprovider="sqlmembershipprovider"> <rolemanager defaultprovider="sqlroleprovider" > <profile defaultprovider=" SqlProfileProvider "> Save the file. The changes will take effect the next time you access a page in your web browser. You may receive an error if the database specified by the new provider is empty or not configured. You can configure the new database by running the web-based install wizard (in the installer directory). Typically you will want to edit the Gallery data provider at the same time you change the other data providers. This is done in galleryserverpro.config, and is explained in the next section. SQLite cannot be used when Gallery Server Pro is running in a Medium Trust environment, unless the file System.Data.SQLite.dll is placed in the global assembly cache (GAC). In fact, an error is thrown if SQLite is even mentioned in web.config file or if a SQLite dll exists in the bin directory. For this reason, special Medium Trust-only versions of web.config are provided in the download. They are named web_sqlserver_2.0.config (for.net 2.0) and web_sqlserver_3.5.config (for.net 3.5) and are found in the root of the web application, next to web.config. Their only difference with web.config is that all references to SQLite have been removed. For example, the Membership section looks like this: <membership defaultprovider="sqlmembershipprovider"> <providers> <clear /> <add applicationname="gallery Server Pro" passwordformat="encrypted" minrequirednonalphanumericcharacters="0" minrequiredpasswordlength="2" maxinvalidpasswordattempts="50" enablepasswordreset="true" enablepasswordretrieval="true" passwordattemptwindow="10" requiresquestionandanswer="false" requiresunique ="false" connectionstringname="sqlserverdbconnection" name="sqlmembershipprovider" type="system.web.security.sqlmembershipprovider" /> </providers> Gallery Server Pro 2.3 Administrator s Guide Page 202 of 238

203 </membership> Similarly, the SQLite sections in the rolemanager and profile sections have been removed. If you want to use SQL Server in Medium Trust, replace the contents of web.config with the contents of web_sqlserver_2.0.config or web_sqlserver_3.5.config. Also delete the files System.Data.SQLite.dll and GalleryServerPro.Data.SQLite.dll from the bin directory. After you have made these changes, use the Install Wizard to complete the installation. Galleryserverpro.config Galleryserverpro.config, in the config directory, contains configuration settings specific to Gallery Server Pro, such as and watermark settings, and HTML templates used for rendering media objects. It also specifies the data provider. You will find it at the end of the file, as shown here: <dataprovider defaultprovider="sqlitegalleryserverproprovider"> <providers> <add applicationname="gallery Server Pro" connectionstringname="sqlitedbconnection" name="sqlitegalleryserverproprovider" type="galleryserverpro.data.sqlite.sqlitegalleryserverproprovider" /> <add applicationname="gallery Server Pro" connectionstringname="sqlserverdbconnection" name="sqlservergalleryserverproprovider" type="galleryserverpro.data.sqlserver.sqldataprovider" /> </providers> </dataprovider> It has a similar structure to the Membership, Role, and Profile sections in web.config. The above example shows that Gallery Server Pro is configured to store data in SQLite. To configure it to store data in SQL Server, change the defaultprovider attribute to SqlServerGalleryServerProProvider, like this: <dataprovider defaultprovider="sqlservergalleryserverproprovider"> You may find that to get Gallery Server Pro working in Medium Trust, you need to remove the reference to the SQLite provider. In this case, it will look like this: <dataprovider defaultprovider="sqlservergalleryserverproprovider"> <providers> <add applicationname="gallery Server Pro" connectionstringname="sqlserverdbconnection" name="sqlservergalleryserverproprovider" type="galleryserverpro.data.sqlserver.sqldataprovider" /> </providers> </dataprovider> Gallery Server Pro 2.3 Administrator s Guide Page 203 of 238

204 Create a custom data provider Below is a diagram showing how the SQL Server data provider, named SQLiteGalleryServerProProvider, inherits the DataProvider abstract class. The diagram above shows that the SQLiteGalleryServerProProvider class has several methods for retrieving and saving data. All data access in Gallery Server Pro passes through one of these methods. The DataProvider class is defined in GalleryServerPro.Provider.dll. It inherits from the Microsoft.NET Framework class System.Configuration.Provider.ProviderBase and implements the interface GalleryServerPro.Provider.Interfaces.IDataProvider (defined in GalleryServerPro.Business.Interfaces.dll). To enable Gallery Server Pro to use an alternative data store such as MySQL, Oracle, Microsoft Access, or something else, write a new class that inherits from the DataProvider abstract base class defined in GalleryServerPro.Provider.dll. If you use a tool such as Visual Studio, it will automatically define all the methods that must be implemented. For example, here is the skeleton for the method to delete an album: public override void Album_Delete(IAlbum album) Gallery Server Pro 2.3 Administrator s Guide Page 204 of 238

205 { } Gallery Server Pro will call this method whenever an album is to be deleted. It is your job, as the writer of this custom provider, to write the code that will delete the album record from your data store. How you do it is up to you. Note: You will probably want to refer to one of the existing providers to ensure you provide similar behavior. For example, when deleting an album the SQLiteGalleryServerProProvider provider recursively deletes all child albums of the specified album. Your custom provider should behave similarly. Once you have implemented all the methods and compiled your code, you are ready to configure Gallery Server Pro to use your provider. Copy the dll containing your provider into the bin directory of the Gallery Server Pro web application. Update the data provider section of galleryserverpro.config. For example, if your provider is in a class named OracleGalleryServerProProvider that is in an assembly named GalleryServerPro.Data.Oracle.dll, the data provider section will look like this: <dataprovider defaultprovider="oraclegalleryserverproprovider"> <providers> <add name="oraclegalleryserverproprovider" type="galleryserverpro.data.oracle.oraclegalleryserverproprovider, GalleryServerPro.Data.Oracle" /> </providers> </dataprovider> 11. Customizing Gallery Server Pro Overview Gallery Server Pro provides a great deal of customization options through the Site admin section and the configuration files web.config and galleryserverpro.config. For advanced users, there are additional ways to modify an installation: Change fonts, font size, colors, and other styles by editing the CSS files Add language packs to support other languages Integrate into another web site, even those not running ASP.NET Editing the source code Gallery Server Pro is built as an ASP.NET user control to allow for easy integration into other web sites. The HTML conforms to XHTML 1.0 Strict web standards, and all styling is done through Cascading Style Gallery Server Pro 2.3 Administrator s Guide Page 205 of 238

206 Sheets that validate against the W3C s CSS validation engine ( There are no deprecated tags such as <FONT> littered throughout the web app! Gallery Server Pro was written in C# and ASP.NET 2.0 using Visual Studio and uses 100% managed code. The source code and project files are available from Styling Formatting, such as fonts, font size, colors, padding and some layout, is done through Cascading Style Sheets (CSS). There are two key CSS files: ca_styles.css - Contains styles used by the ComponentArt controls, such as the menu, treeview, and grid. gallery.css - Contains all other styles. These files are located in the gs\styles directory and can be edited in any text editor. For example, the style of the gallery title "Media Gallery" is specified within a CSS class named bannertext:.gsp_ns p.gsp_bannertext { font-size:2em;color:#369;margin:0; padding: ; } You may specify a different font, font size, color, padding, or any other style. For example, to change it to smaller, italicized text in the Verdana font with a different color, you might use this:.gsp_ns p.bannertext { font:italic 14px Verdana,Arial,Sans-Serif; color:#000;margin: 0; padding: ; } Use a tool such as the Firebug add-on for Firefox to help you discover which CSS classes are associated with the formatting you wish to target. Multi-language support Gallery Server Pro supports multiple languages in the form of language packs that are created by volunteers. When a user navigates to a website, the browser sends the user's preferred language to the web server with the request. Gallery Server Pro uses this setting to automatically return a web page to the user in that language. If no translation has been provided for that language, the default resource - English - is used. For example, an English user might see a gallery like this: Gallery Server Pro 2.3 Administrator s Guide Page 206 of 238

207 Another user in France, whose browser is set to the French language, can view the same gallery and see the resources in French: Gallery Server Pro 2.3 Administrator s Guide Page 207 of 238

208 Notice that a single installation of Gallery Server Pro automatically provides the correct language, without any intervention by the user. You do not need to choose one language for everyone, nor do your users need to click the Espaňol link to read the Spanish version. Gallery Server Pro is released with English resources. Additional languages can be added by installing one or more language packs, available in the Language Translation forum. If a language pack has not yet been created in your language, consider being a volunteer and creating a translation. More details, including step by step instructions for deploying and creating a language pack, are available in the forum. Note: Some text in your gallery cannot be automatically served in different languages. This includes any text that is directly editable by an administrator, such as album titles and summaries, and media object titles. It is expected that you edit them directly in your preferred language. Gallery Server Pro 2.3 Administrator s Guide Page 208 of 238

209 Integrate into an ASP.NET web application Overview Gallery Server Pro is wrapped into a single ASP.NET user control. This allows you to easily incorporate the gallery into an existing ASP.NET web application where you can share membership, session, and all the benefits of keeping your application in one place. Adding a gallery to your site involves three basic steps (detailed step by step instructions are in the next section): 1. Copy the Gallery Server Pro files into your web application. Most of them can be placed in a directory of your choosing. A few, such as the SQLite database and.resx resource file, go into pre-defined ASP.NET directories, such as App_Data and App_GlobalResources. 2. Configure web.config to define a few settings required by Gallery Server Pro. 3. Choose one of your web pages to host the gallery. For example, create a new.aspx page and have it based on your current master page. Add the following to the top of the page: <%@ Register TagPrefix="gsp" Namespace="GalleryServerPro.Web" Assembly="GalleryServerPro.Web" %> At the location in the page where you want the gallery to appear, add: <gsp:gallery ID="gallery1" runat="server" /> That's it! Fire up the page and you will notice Gallery Server Pro appears in the location you defined. All the functionality that exists, such as logging on, searching, and the task and admin pages are there. And it will work beautifully with your existing master pages. You can add Gallery Server Pro to a VB.NET or C# web application. Step by step instructions Here are detailed instructions for adding a gallery into your existing ASP.NET application. We will use actual screen shots taken from adding the Gallery Server Pro demo site into 1. Download the ZIP file containing the compiled Gallery Server Pro web application from 2. Create a new, empty directory within your web app. This will contain the supporting files such as images, user controls, etc. It can have any name and be at any hierarchical level. I will choose the name 'gs': Gallery Server Pro 2.3 Administrator s Guide Page 209 of 238

210 3. Use Windows Explorer to open the ZIP file and copy the contents of the gs directory into the directory you just created. These are files used by the Gallery user control and are required in any web site containing Gallery Server Pro. 4. In Visual Studio, you can see the files in Solution Explorer by clicking the 'Show all files' toolbar button: Gallery Server Pro 2.3 Administrator s Guide Page 210 of 238

211 5. Select the folders below 'gs' (config, controls, etc). Right-click and choose Include In Project. The icons change to indicate they are now an official part of the web project: Gallery Server Pro 2.3 Administrator s Guide Page 211 of 238

212 6. If you do not have an App_Data directory in your application, create one by using Visual Studio to right click the web project and choosing Add - Add ASP.NET Folder - App_Data. 7. Copy galleryserverpro_data.sqlite from the App_Data directory in the ZIP file into your App_Data directory. 8. If you do not have an App_GlobalResources directory in your application, create one by using Visual Studio to right click the web project and choosing Add - Add ASP.NET Folder - App_GlobalResources. 9. Copy GalleryServerPro.resx from the App_GlobalResources directory in the ZIP file you re your App_GlobalResources directory. 10. Use Windows Explorer to copy the contents of the bin directory from the ZIP file into your bin directory. The screenshot below shows galleryserverpro_data.sqlite file in the App_Data directory (ignore gspweb_data.sqlite), the.resx file in App_GlobalResources, and the dll files from the bin directory. Gallery Server Pro 2.3 Administrator s Guide Page 212 of 238

213 Warning: The contents of the bin directory may be periodically deleted by Visual Studio, which will break the gallery. For a more robust solution, add the dll files to the root of your web application and set Build Action = None and Copy To Output Directory to Copy If Newer. Each time you compile, Visual Studio will copy the files to the bin directory. Unfortunately, this technique requires the files to be in the root directory, which clutters it up. An alternative is to add them to a subdirectory and then add references to them by right-clicking the References node and choosing Add Reference. This allows them to be neatly stored in a directory but adds references to your project, which also clutters things up, but perhaps in a more acceptable way. Gallery Server Pro 2.3 Administrator s Guide Page 213 of 238

214 11. Update your web.config file with settings from the web.config file in the Gallery Server Pro download. You probably can't just copy everything because your file already has settings important to your application. Go through the Gallery Server Pro version of web.config section by section. Copy the section if it is missing from your existing file, and merge those sections that exist in both places. Note: This step requires a skilled ASP.NET developer who is familiar with web.config files. Some sections may not need to be copied. For example, if your application runs only on IIS 7, you do not need to copy the httphandlers and httpmodules section. If you are using SQL Server as the data provider, you do not need to copy the SQLite related sections. 12. Okay! All the pieces are in place. Now you are ready to add the user control to one of your pages. I'll create a new web page based on a master page: Gallery Server Pro 2.3 Administrator s Guide Page 214 of 238

215 13. Below is the new, empty web page that appears. Your.aspx page may look different. Page Title="" Language="C#" MasterPageFile="~/master/global.Master" AutoEventWireup="true" CodeBehind="demo.aspx.cs" Inherits="TIS.GSPWeb.demo" %> MasterType VirtualPath="~/master/global.master" %> <asp:content ID="Content1" ContentPlaceHolderID="cpHeader" runat="server"> </asp:content> <asp:content ID="Content2" ContentPlaceHolderID="cpSideBar" runat="server"> </asp:content> <asp:content ID="Content3" ContentPlaceHolderID="MainContent" runat="server"> </asp:content> 14. If you plan to use HTML tags in any textbox within the gallery, disable the request validation feature of ASP.NET by adding ValidateRequest="false" to the Page element at the top: Page Title="" Language="C#" MasterPageFile="~/master/global.Master" AutoEventWireup="true" CodeBehind="demo.aspx.cs" Inherits="TIS.GSPWeb.demo" ValidateRequest="false" %> Note: The request validation feature of ASP.NET causes an error to occur when HTML or javascript is entered in a form field. This is a good feature but it means you cannot add external media objects or create hyperlinks and other formatting in the album and media object titles. Gallery Server Pro 2.3 Administrator s Guide Page 215 of 238

216 15. Ensure that the <head> tag has a runat="server" attribute. The head tag will be either in the master page or the.aspx page. It should look like this: <head runat="server"> your stuff </head> Note: Adding runat="server" gives Gallery Server Pro programmatic access to the head tag. This is required so Gallery Server Pro can insert links to the style sheets. 16. Register the Gallery user control on the page. Add the following to the top, just after the <%@ Page > element: <%@ Register TagPrefix="gsp" Namespace="GalleryServerPro.Web" Assembly="GalleryServerPro.Web" %> 17. At the location in the page where you want the gallery to appear, add this: <gsp:gallery ID="g" runat="server" /> 18. (MS Ajax 1.0 users): Add a ScriptManager to the page or ensure the master page has one defined. Gallery Server Pro attempts to dynamically add a ScriptManager if one is not present, but this does not reliably work in MS Ajax 1.0. (See the next code sample for an example of a ScriptManager control.) 19. Add other HTML elements as desired. In the example below, I added a ScriptManager and a <div> tag with some padding around the user control. <%@ Page Title="" Language="C#" MasterPageFile="~/master/global.Master" AutoEventWireup="true" CodeBehind="demo.aspx.cs" Inherits="TIS.GSPWeb.demo" %> <%@ MasterType VirtualPath="~/master/global.master" %> <%@ Register TagPrefix="gsp" Namespace="GalleryServerPro.Web" Assembly="GalleryServerPro.Web" %> <asp:content ID="Content1" ContentPlaceHolderID="cpHeader" runat="server"> </asp:content> <asp:content ID="Content2" ContentPlaceHolderID="cpSideBar" runat="server"> </asp:content> <asp:content ID="Content3" ContentPlaceHolderID="MainContent" runat="server"> <asp:scriptmanager ID="sm" runat="server" /> <div id="content" style="padding: px;"> <gsp:gallery ID="gallery1" runat="server" /> </div> </asp:content> 20. Update the paths in web.config. Find the sections shown below and verify the paths are correct. The paths are relative to root of the web application. The text default.aspx shown below should be updated to the.aspx or master page that contains the Gallery user control. <galleryserverpro configsource="gs\config\galleryserverpro.config" />... <location path="default.aspx"> <system.web> Gallery Server Pro 2.3 Administrator s Guide Page 216 of 238

217 <httpruntime maxrequestlength=" " executiontimeout="86400" /> </system.web> </location> <location path="gs/services/gallery.asmx"> <system.web> <httpruntime executiontimeout="86400" /> </system.web> </location> Note: Configuring a location element for the web page (default.aspx) and web service (Gallery.asmx) as shown above helps prevent upload and timeout errors. This is because ASP.NET blocks uploads larger than 4 MB and will throw a timeout error after 90 seconds. To change these settings, a <location> element is added to web.config to override the default values. IIS 7 users: By default, IIS 7 restricts uploads larger than about 30 MB even when a larger maxrequestlength attribute is assigned. Refer to the system.webserver section in the web.config file that ships with Gallery Server Pro for instructions for modifying this setting. 21. Compile the application and load the page in a web browser. A new gallery appears in the location you defined. For example: Gallery Server Pro 2.3 Administrator s Guide Page 217 of 238

218 22. At this point you may want to run the install wizard or the upgrade wizard. Refer to the install or upgrade chapters for more information. Customizing the Gallery user control There are two custom properties of the Gallery user control that may be useful: ShowLogin: When true, login/logout controls are displayed at the top right of every page. Overrides the global showlogin setting in galleryserverpro.config. This can be useful for hiding the login controls in your main gallery but showing them on another page for administrators. ShowSearch: When true, provides search functionality at the top right of every page. Overrides the global showsearch setting in galleryserverpro.config. Potential CSS conflicts between Gallery Server Pro and your application Gallery Server Pro makes extensive use of cascading style sheets (CSS) to format the HTML. One challenge is keeping the CSS used by Gallery Server Pro from interfering with any CSS used in your application. For example, you might have a CSS file included on every page that styles all paragraph tags: p { margin: em 0; padding: 0.4em 0 0 0; } And you might have classes with names that match CSS class names in Gallery Server Pro:.content { min-height: 400px; } In turn, Gallery Server Pro defines some styles that may affect your web pages:.gsp_footer { text-align:center;font-size:80%;} To help reduce the CSS interference, Gallery Server Pro uses a pseudo-namespace technique to qualify all of its CSS. The top HTML element rendered in the gallery control has the gsp_ns class assigned to it: <div class="gsp_ns"> gallery HTML content </div> All CSS styles are then defined under this "namespace". For example, the footer class used in Gallery Server Pro is actually defined like this:.gsp_ns.gsp_footer { text-align:center;font-size:80%; } This tells the browser that only classes named gsp_footer that are under an element with the gsp_ns class are affected by the rule. So if you are already using the gsp_footer class in your web site you will be unaffected by the Gallery Server Pro version. This technique is not perfect, however. It is possible for *your* gsp_footer class to interfere with Gallery Server Pro's gsp_footer. For example, let's say your web site is currently defining a gsp_footer class like this: Gallery Server Pro 2.3 Administrator s Guide Page 218 of 238

219 . gsp_footer { background-color:silver; } The footer in Gallery Server Pro will inherit this setting because it doesn't define its own background color. If this interference occurs, you have a few choices: Change the name of your gsp_footer class. Modify the class in Gallery Server Pro's style definition to provide explicit behavior. For example, add "background-color:transparent". Change the name of the class used in Gallery Server Pro. This may involve modifying the source code and recompiling. Many of the classes in Gallery Server Pro have a "gsp_" prefix like this:.gsp_bold { font-weight: bold; } Using this prefix reduces the likelihood of name interference, so hopefully you don't have much trouble. The CSS files used in Gallery Server Pro in the gs\styles directory. Integrate into non-asp.net web sites (iframe Method) You can add a gallery to any web site by adding an <iframe> to a web page and setting its source to an installation of Gallery Server Pro. This method is useful when your web site is not an ASP.NET web application. For example, it could be a static site built in FrontPage, Expression Web, or Dreamweaver, a dynamic site built with another technology such as Java or ColdFusion, or a web site created by a web host template application. This technique requires that you have access to a web server or hosting provider that satisfies the requirements of Gallery Server Pro, such as running ASP.NET. If your current server does not, you can install Gallery Server Pro on another server or choose another hosting provider that does satisfy the requirements. You will then modify a page on your existing site to point to this external installation. Follow these steps to add a gallery to your existing web site. 1. Install Gallery Server Pro as a stand-alone web application on a web server. It does not have to be the same web server that hosts your web site, but it must satisfy the technical requirements, such as running ASP.NET. 2. Note the URL that represents the home page of the gallery. Example: 3. On your existing web site, create a new page or choose an existing page to host the gallery. On that page, add the following HTML at the location where the gallery should appear: <iframe id="gs" src=" frameborder="0" style="width:100%;height:100%;border:none;" /> 4. Replace " with the URL to the gallery you installed in the first step. Gallery Server Pro 2.3 Administrator s Guide Page 219 of 238

220 Note: You may have to modify the style or attributes to match the desired look and feel of your site. For example, a fixed width or height may be more appropriate than 100%. 5. That's it! The page will load the gallery into the iframe element. To your users, it appears integrated with the rest of the web site. For example, below is a screenshot where Gallery Server Pro is integrated into a Classic ASP web site. Enable external links The page hosting the iframe does not, by default, pass its query string parameters to the iframe's URL. This means that when the page is first loaded it will always display the root album. You cannot link directly to child albums or media objects from other web pages. Links within the gallery work normally - you can navigate between albums and media objects just as easily as a normal installation, but you'll have trouble as soon as you want to send a link to a friend that points to a particular album or media object. Gallery Server Pro 2.3 Administrator s Guide Page 220 of 238

221 There is a solution! Add a little javascript that runs during the onload event that passes any query string parameters from the host page to the src attribute on the iframe element. Here's an example of a modified body tag on the web page that contains the iframe: <body onload="document.getelementbyid('gs').src = ' + location.search;"> The script gets a reference to the iframe (it has id "gs") and appends the query string from the current page to the gallery home page. Now you can create URL's that navigate directly to an album or media object. For example, say you want to link to album # 465 (that is, album ID hover over any link to an album to see the ID). If the web page containing the iframe is at then the link will be The javascript will append the "?g=album&aid=465" to the src attribute of the iframe element. Note that you will have to manually create the URL, since the permalink function in Gallery Server Pro does not work correctly with frames. See Limitations of the iframe technique for more information. Limitations of the iframe technique Broken Permalink. As you browse media objects, the toolbar above each object has a button with a picture of a hyperlink and a tooltip that says "Get a permanent hyperlink for this media object", as shown here: Gallery Server Pro is not aware of when it is being used inside an iframe, so the permalink function creates an URL to the Gallery Server Pro installation rather than the page containing the frame. It is recommended to disable the permalink feature on the Media Objects - General page in the Site admin area. Invalid XHTML 1.0 Strict. The iframe element is not supported in XHTML 1.0 Strict. If you have a web site that must validate you can use the object tag: Gallery Server Pro 2.3 Administrator s Guide Page 221 of 238

222 <object data=" type="text/html" /> Unfortunately, browser support for the object tag is inconsistent, so test this carefully to ensure it works in the browsers you want to support. 12. Using Internet Information Services (IIS) Manager IIS 6 Internet Information Services (IIS) 6 is native to Windows Server Configure a directory to run as a web application 1. Extract the Gallery Server Pro web application files to a directory on the web server. This example assumes they are copied to C:\inetpub\wwwroot\galleryserverpro\. 2. Once the files have been extracted to a destination directory, start IIS Manager. The following screen appears. Note: Start IIS Manager by entering inetmgr at a Start-Run dialog box. Gallery Server Pro 2.3 Administrator s Guide Page 222 of 238

223 3. Expand the Web Service Extensions node. Verify that ASP.NET 2.0 is installed and enabled, as shown below. Gallery Server Pro 2.3 Administrator s Guide Page 223 of 238

224 4. Since I created the galleryserverpro directory within C:\inetpub\wwwroot\, the directory automatically appears under the Default Web Site node. Right click the galleryserverpro directory, and choose Properties. Note: If the web files are located outside the default web directory, right click Default Web Site and choose New > Virtual Directory. Step through the wizard to create a virtual directory. (On the Virtual Directory Access Permissions step, leave Read permissions checked and the remaining items unchecked.) Once the virtual directory is created, right click on it and choose Properties. Then resume with the following steps. Gallery Server Pro 2.3 Administrator s Guide Page 224 of 238

225 5. After choosing Properties, the following screen appears. Click Create to convert the directory to a web application. Gallery Server Pro 2.3 Administrator s Guide Page 225 of 238

226 6. Navigate to the Documents tab. Verify default.aspx is specified as a default document, as shown below. Gallery Server Pro 2.3 Administrator s Guide Page 226 of 238

227 7. Navigate to the ASP.NET tab. Verify that ASP.NET is selected, as shown below. Note: In some cases the dropdown list is disabled. To enable the list, click OK on the Properties dialog, and then re-open the dialog. Gallery Server Pro 2.3 Administrator s Guide Page 227 of 238

228 8. That s it! The web application should now be configured and is available through your web browser at Note: Don t forget to use Windows Explorer to modify the NTFS permissions on the config and mediaobjects directories as described in the Installation instructions. IIS 7 and IIS 7.5 Internet Information Services (IIS) 7 is native to Windows Server 2008 and Vista. IIS 7.5 is included in Windows 7 and Windows Server 2008 R2. Configure a directory to run as a web application 1. Extract the Gallery Server Pro web application files to a directory on the web server. This example assumes they are copied to C:\inetpub\wwwroot\galleryserverpro\. 2. Once the files have been extracted to a destination directory, start IIS Manager. The following screen appears. Note: Start IIS Manager by entering inetmgr at a Start-Run dialog box. Gallery Server Pro 2.3 Administrator s Guide Page 228 of 238

229 3. Since I created the galleryserverpro directory within C:\inetpub\wwwroot\, the directory automatically appears under the Default Web Site node. Right click the galleryserverpro directory, and choose Convert to Application. Note: If the web files are located outside the default web directory, right click Default Web Site and choose Add Application. Gallery Server Pro 2.3 Administrator s Guide Page 229 of 238

230 4. The Add application dialog box appears. Click OK to create the application and return to the main IIS Manager screen. 5. IIS Manager now shows the galleryserverpro directory configured as a web application. Gallery Server Pro 2.3 Administrator s Guide Page 230 of 238

231 6. That s it! The web application should now be configured and is available through your web browser at Note: Don t forget to use Windows Explorer to modify the NTFS permissions on the web application directory as described in the Installation instructions. 13. Configuring NTFS Permissions In Microsoft Windows The user account that IIS runs under depends on the version of Internet Information Services (IIS). By default it is the ASPNET user in IIS 5 and 5.1, Network Service in IIS 6 and 7, and IIS AppPool\DefaultAppPool in IIS 7.5. It is also possible IIS has been configured to use a different account. Whatever account IIS is running under, you can follow these instructions to give the user modify permission to the directory containing Gallery Server Pro. Note: These instructions are screen shots from Windows Server 2008, but other versions of Windows work similarly. 1. Start Windows Explorer (type explorer.exe in the Start - Search box). 2. Navigate to the directory containing the Gallery Server Pro web application directory. Gallery Server Pro 2.3 Administrator s Guide Page 231 of 238

232 3. Right click the directory and choose Properties, as shown below: Gallery Server Pro 2.3 Administrator s Guide Page 232 of 238

233 Gallery Server Pro 2.3 Administrator s Guide Page 233 of 238

234 4. The Properties dialog appears. Select the Security tab, as seen here: 5. Click the Edit button. The Permissions dialog box appears: Gallery Server Pro 2.3 Administrator s Guide Page 234 of 238

235 6. Click Add to show the Select Users or Groups dialog box. Type the account name (typically Network Service, ASPNET, or IIS AppPool\DefaultAppPool) into the textbox, as shown below. Gallery Server Pro 2.3 Administrator s Guide Page 235 of 238

236 Click OK. Make sure the Allow checkbox is selected for the Modify permission, as seen below. 7. Click OK until all the dialog boxes disappear, and you are done! Note: In some cases you may find you still do not have sufficient permission. If this occurs, try giving IIS_WPG (IIS 6) or IIS_IUSRS (IIS 7) modify permission. If that doesn't work, try giving the Everyone group full permission. That gives all users all possible permissions. Once that is working, work backwards until you find the minimum amount of permission to keep the application running. 14. Management Tools for SQLite and SQL Server Overview When all is well and good in the world, you don't have to think about the database used by Gallery Server Pro. However, there may be times when you want to review - and possible edit - the data directly in the tables. Below I describe the various tools that are available for managing SQL Server and SQLite. Using these tools is outside the scope of this document and can be found on the internet, so I'll be brief. Gallery Server Pro 2.3 Administrator s Guide Page 236 of 238