Difference between revisions of "OHSU Navigation Install v1.0"

From ADF Docs
Jump to: navigation, search
(Created page with '== Download == Download the OHSU Navigation Application from the [http://community.paperthin.com/projects/ohsu_navigation/ Community Site] or from the SVN Repository. Extract …')
 
(→‎Import Custom Elements)
Line 24: Line 24:
 
=== Import ===
 
=== Import ===
  
−
Import Custom Elements in this order:  
+
Import Custom Element:  
  
−
# Photo (Photo-Custom-Element.zip)
+
# Nav Element (Nav-Element-Custom-Element.zip)
−
# Photo Category (Photo-Category-Custom-Element.zip)
 
−
# Photo Size (Photo-Size-Custom-Element.zip)
 
−
# Photo Gallery (Photo-Gallery-Custom-Element.zip)
 
−
# PTPhotoGallery Configuration (PTPhotoGallery-Configuration-Custom-Element.zip)
 
  
−
Import Metadata form:
+
Import the Custom Field Type:
  
−
# PhotoSizeRender (PhotoSizeRender-Metadata-Form.zip)
+
# Navigation (Navigation-Custom-Field-Type.zip)
−
## Bind this form to the following Photo Gallery Render Handler
 
−
### Cycle
 
−
### Cycle Thumb Nav
 
−
### Grid
 
−
 
 
−
=== Verify Imports ===
 
−
 
 
−
The imported components' render handlers and custom field types must be verified.  During the import process, the render handler and custom field types paths may have been changed to reflect the current site's path. 
 
−
 
 
−
Review and update these paths to reference the ADF path.  In most cases, this will just require to be unlocked and a change in the path from the site name to 'ADF'.  Check the paths for the [[PT_Photo_Gallery_Overview#Contents|custom field types that were imported]] with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".
 
−
 
 
−
If the custom elements that are imported contain custom field types that are already in the site, the naming convention for the custom field type will be unique.  To resolve this, unlock the field types and elements, and reassign the element field type to the pre-existing field type. 
 
−
 
 
−
Example: The Photo Category custom element contains two uses of the General Chooser field type, if the General Chooser field type is already installed on the site then the import process will attempt to import another General Chooser but with a new name such as "General Chooser_import_1250003208472." To resolve this issue, open the custom element and assign the field type (General Chooser_import_1250003208472) to the field type with the simple name General Chooser. Note that when you assign the existing general chooser you will need to click on the "properties" tab and enter "photoSizeGC" as the bean name.  After reassigning the field type, delete the new imported field from the list of custom field types.
 
  
 
== Subsites ==
 
== Subsites ==

Revision as of 18:38, 5 September 2012

Download

Download the OHSU Navigation Application from the Community Site or from the SVN Repository.

Extract the zip files into the following directory: /ADF/apps/ohsu_nav/

Site Configuration

The OHSU Navigation Application is built within the ADF. The ADF must be installed in the site to run the OHSU Nav, follow the ADF Installation instructions.

  • Make sure the ADF is setup and running on the site. If the ADF is not setup, then follow the instructions for ADF Installation.
  • Open the sites 'ADF.cfc' (See Site Configuration (ADF.cfc) for more info) file (located in your site's /_cs_apps/ directory) in a text editor. Locate the Load the ADF Application into application space comment in the file. Add (or uncomment) the following command under the comment section:
loadApp("ohsuNav");

Import Custom Elements

The OHSU Navigation Application has a couple Custom Components defined within CommonSpot. The components have been exported and are available in the OHSU Navigation's "exported-objects" folder located at the root of the OHSU Nav application directory (e.g. /ADF/apps/ohsu_nav/exported-objects/)

Optional: You may want to create a new category within the CommonSpot Element Gallery for 'OHSU Navigation Elements'.

To import these objects, you will need to be an administrator for your site. If you are not a site administrator, consult your Server administrator for more information

Import

Import Custom Element:

  1. Nav Element (Nav-Element-Custom-Element.zip)

Import the Custom Field Type:

  1. Navigation (Navigation-Custom-Field-Type.zip)

Subsites

It is highly recommended that a Navigation webadmin subsite is created for Administrators. This configuration allows subsite security to be used to allow only Administrators access to the webadmin subsite. A forms subsite is also created to store the pages for the administrator forms.

Your site may already have a webadmin subsite. The steps below will add a navigation subsite under the webadmin subsite.

Web Admin

  1. Create a new subsite under the site root called webadmin.
  2. Create a new subsite under webadmin called navigation.
  3. Configure the /webadmin/navigation/ subsite Content Security to give 'No Rights' to 'Anonymous Users' and 'Authenticated Users'.
  4. Configure the /webadmin/navigation/ subsite Content Security to give permissions to the group of administrators who will manage the Photos.

CCAPI Configuration

Configuration Page

Reset the ADF

Reset the ADF for the server and site.

Retrieved from "http://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation_Install_v1.0&oldid=5780"