Difference between revisions of "PT Import Content Installation"

From ADF Docs
Jump to: navigation, search
Line 1: Line 1:
−
Important: Ensure that the [[Installation | ADF is installed]] and functioning correctly
+
'''Important''': Ensure that the [[Installation | ADF is installed]] and functioning correctly before installing PT Import Content.
  
 
== Import Custom Elements ==
 
== Import Custom Elements ==
−
Import the two custom elements into your site (via the Elements dialog located in your Site Administrator:
+
Import two custom elements into your site (via the Elements dialog located in the CommonSpot Site Administrator):
  
 
#Subsite Mapping
 
#Subsite Mapping
Line 10: Line 10:
  
 
== Build CCAPI page ==
 
== Build CCAPI page ==
−
#Create a page in the root of your web site called CCAPI (ensure that Anonymous users have "Read" access to this page and all of its elements.
+
#Create a page in the root of your web site called CCAPI (confirm Anonymous users have "Read" access to this page and all of its elements.
−
# Add the following elements to the page:
+
# Add the following elements to this page:
 
## Subsite Mapping
 
## Subsite Mapping
 
## Page Mapping
 
## Page Mapping
−
# For each Element give it a unique name (e.g. "subsiteMapElement", "pageMapElement")
+
# Give each element a unique name (e.g. "subsiteMapElement", "pageMapElement")
−
# Record the pageID for the new page you created
+
# Record the pageID of this new page
  
−
Note: Easiest way to get the pageID is to view the page and look at the header of the document - you will notice a block of JavaScript with a variable called "jsPageID" - the value of this variable is the pageID for the page.
+
Note: The easiest way to get the pageID is to view the page source code.  Examine the header of the document - you will notice a block of JavaScript with a variable called "jsPageID." The value of this variable is the pageID for the page.
  
−
Note: Be sure to move into Read Mode after creating this page
+
Switch into Read Mode after creating this page.
  
 
== Create Generic Content Template ==
 
== Create Generic Content Template ==
−
# Create a Generic Content template (typically this page will derive directly from the Base Plus One and will be located in the root of the site).
+
# Create a new page, to be used as the Generic Content template. Typically, this page will derive directly from the Base Plus One and will be located in the root of the site.
−
# Place a Textblock Element on the page and give that element a name (e.g. "pageContent")
+
# Place a Textblock Element on the page and give that element a name (e.g. "pageContent").
 +
# Save this page as the Generic Content Template.
  
−
Note: Conversely you can use an existing content template - just ensure that the template contains a Formatted Text Block (with or without header) element
+
Note: Alternatively, you can use an existing content template as long as the template contains a named Formatted Text Block (with or without header) element.
  
 
== Configure Site ==
 
== Configure Site ==
Line 35: Line 36:
 
# Copy the /config/ folder from the /ADF/apps/pt_import_content/site_folder/ folder - into your sites /_cs_apps/ folder
 
# Copy the /config/ folder from the /ADF/apps/pt_import_content/site_folder/ folder - into your sites /_cs_apps/ folder
 
# Modify the ccapi.xml file located in /yoursite/_cs_apps/config/ directory.  Use the information from the above two steps (Build CCAPI Page and Create Generic Content Template) to configure the <elements> node.
 
# Modify the ccapi.xml file located in /yoursite/_cs_apps/config/ directory.  Use the information from the above two steps (Build CCAPI Page and Create Generic Content Template) to configure the <elements> node.
−
# Modify the ptImport.xml file located in /yoursite/_cs_apps/config/ directory to match your current sites environment.  This file will contain the name of the CF Datasource used to get access to your external data
+
# Modify the ptImport.xml file located in /yoursite/_cs_apps/config/ directory to match your current sites environment.  This file will contain the name of the CF Datasource used to access to your external data.
 
# Modify the Subsite Spread Sheet Mapping document located in the/yoursite /_cs_apps/pt_import_content/data/ folder
 
# Modify the Subsite Spread Sheet Mapping document located in the/yoursite /_cs_apps/pt_import_content/data/ folder
  
−
Note: make sure that the Content Creation API is enabled for your server (see Developers Guide for more info)
+
Note: make sure that the Content Creation API is enabled for your server (see the CommonSpot Developer's Guide for more info)
  
 
== Build Import Dashboard Page ==
 
== Build Import Dashboard Page ==

Revision as of 23:37, 24 January 2010

Important: Ensure that the ADF is installed and functioning correctly before installing PT Import Content.

Import Custom Elements

Import two custom elements into your site (via the Elements dialog located in the CommonSpot Site Administrator):

  1. Subsite Mapping
  2. Page Mapping

Note: these elements are located in the /ADF/apps/pt_import_content/exported_objects/ folder

Build CCAPI page

  1. Create a page in the root of your web site called CCAPI (confirm Anonymous users have "Read" access to this page and all of its elements.
  2. Add the following elements to this page:
    1. Subsite Mapping
    2. Page Mapping
  3. Give each element a unique name (e.g. "subsiteMapElement", "pageMapElement")
  4. Record the pageID of this new page

Note: The easiest way to get the pageID is to view the page source code. Examine the header of the document - you will notice a block of JavaScript with a variable called "jsPageID." The value of this variable is the pageID for the page.

Switch into Read Mode after creating this page.

Create Generic Content Template

  1. Create a new page, to be used as the Generic Content template. Typically, this page will derive directly from the Base Plus One and will be located in the root of the site.
  2. Place a Textblock Element on the page and give that element a name (e.g. "pageContent").
  3. Save this page as the Generic Content Template.

Note: Alternatively, you can use an existing content template as long as the template contains a named Formatted Text Block (with or without header) element.

Configure Site

  1. Add the following line to the init() function of your sites ADF.cfc (ADF.cfc is located in /yoursite/_cs_apps/ directory)
loadApp("PTImport", "PTImport");
  1. Copy the /pt_import_content/ folder from the /ADF/apps/pt_import_content/site_folder/ folder - into your sites /_cs_apps/ folder
  2. Copy the /config/ folder from the /ADF/apps/pt_import_content/site_folder/ folder - into your sites /_cs_apps/ folder
  3. Modify the ccapi.xml file located in /yoursite/_cs_apps/config/ directory. Use the information from the above two steps (Build CCAPI Page and Create Generic Content Template) to configure the <elements> node.
  4. Modify the ptImport.xml file located in /yoursite/_cs_apps/config/ directory to match your current sites environment. This file will contain the name of the CF Datasource used to access to your external data.
  5. Modify the Subsite Spread Sheet Mapping document located in the/yoursite /_cs_apps/pt_import_content/data/ folder

Note: make sure that the Content Creation API is enabled for your server (see the CommonSpot Developer's Guide for more info)

Build Import Dashboard Page

  1. Create a page and place a Custom Script Element on the page
  2. Configure the Custom Script Element to point to the file "main_controller.cfm" located in the /ADF/apps/pt_import_content/customcf/ directory
Retrieved from "http://community.paperthin.com/adf-docs/index.php?title=PT_Import_Content_Installation&oldid=527"