Difference between revisions of "PT Calendar2 Import Custom Elements"

From ADF Docs
Jump to: navigation, search
(Created page with 'Back to PT Calendar Overview')
 
Line 1: Line 1:
 
Back to [[Calendar|PT Calendar Overview]]
 
Back to [[Calendar|PT Calendar Overview]]
 +
 +
== Overview ==
 +
The Calendars App has several Custom Components defined within CommonSpot. These components are available in the Calendar "exported-objects" folder located at the root of the pt_calendar2 application directory (e.g. /ADF/apps/pt_calendar2/exported-objects/)
 +
 +
To import these objects, you will need to be an administrator for your site.
 +
 +
== Import ==
 +
 +
Import all portions of each component in the order listed.
 +
 +
'''Create a new Custom Element Category:'''
 +
# ptCalendar2 Elements (optional)
 +
 +
'''Import Custom Elements in to the new Category:'''
 +
# Event Organizations (Event-Organizations-Custom-Element.zip)
 +
# Event Categories (Event-Categories-Custom-Element.zip)
 +
# Calendar (Calendar-Custom-Element.zip)
 +
# Calendar Page Map (Calendar-Page-Map-Custom-Element.zip)
 +
# ptCalendar2 Configuration (ptCalendar2-Configuration-Custom-Element.zip)
 +
 +
<!-- REMOVED / NOT NEEDED -->
 +
<!-- '''Import Metadata:''' -->
 +
<!-- Profiles (profiles-Metadata-Form.zip) -->
 +
 +
'''Verify/Update 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. 
 +
 +
# General Chooser
 +
# Subsite Select
 +
# App Config Page
 +
 +
Review and update these paths to reference the ADF path.  In most cases, this will just require a change in the path from the site name to 'ADF'.  Check the paths for the custom field types that were imported with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".
 +
 +
<!-- REMOVED until security settings can be verified
 +
== Security Settings ==
 +
During the import, field permissions may have been cleared or assigned to an unknown group.  The following custom element should have explicit security settings:
 +
 +
* Forum Messages Custom Element
 +
** profileID - Field has Read/Edit permissions to the Site Administrators group.  Read permissions for Anonymous and Authenticated Users groups.
 +
* Profiles Metadata Form
 +
** Type - Field has Read permissions to the Site Administrators group. 
 +
** profileID - Field has Read permissions to the Site Administrators group. 
 +
** UniqueID - Field has Read permissions to the Site Administrators group.
 +
 +
For additional details on field security, view the [[Forum_Messages_Custom_Element|Forum Messages Custom Element]] wiki page.
 +
-->
 +
 +
[[Category:Calendar]]

Revision as of 05:51, 22 April 2010

Back to PT Calendar Overview

Overview

The Calendars App has several Custom Components defined within CommonSpot. These components are available in the Calendar "exported-objects" folder located at the root of the pt_calendar2 application directory (e.g. /ADF/apps/pt_calendar2/exported-objects/)

To import these objects, you will need to be an administrator for your site.

Import

Import all portions of each component in the order listed.

Create a new Custom Element Category:

  1. ptCalendar2 Elements (optional)

Import Custom Elements in to the new Category:

  1. Event Organizations (Event-Organizations-Custom-Element.zip)
  2. Event Categories (Event-Categories-Custom-Element.zip)
  3. Calendar (Calendar-Custom-Element.zip)
  4. Calendar Page Map (Calendar-Page-Map-Custom-Element.zip)
  5. ptCalendar2 Configuration (ptCalendar2-Configuration-Custom-Element.zip)


Verify/Update 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.

  1. General Chooser
  2. Subsite Select
  3. App Config Page

Review and update these paths to reference the ADF path. In most cases, this will just require a change in the path from the site name to 'ADF'. Check the paths for the custom field types that were imported with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".

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