http://community.paperthin.com/adf-docs/api.php?action=feedcontributions&user=Renee.mckechnie&feedformat=atomADF Docs - User contributions [en]2024-03-29T12:54:08ZUser contributionsMediaWiki 1.29.0http://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Auto_Create&diff=533PT Profile Auto Create2010-01-25T00:11:48Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Auto Create process will create a profile custom element record and all profile pages. <br />
<br />
Set up a data values structure with the structure key the same names as the profile element fields. This structure will populate the profile record.<br />
<br />
Call the Profile Service autoCreateProfile function and pass in the data value structure that was populated. The return value is true/false for if the profile record was created. (see example below)<br />
<br />
== Configuration Point ==<br />
* /ADF/apps/pt_profile/components/ProfileService.cfc<br />
** Function autoCreateProfile - Process to create the profile record and profile pages for the data values structure.<br />
<br />
Below is a sample script to set up the data value structure and then call the Profile Service autoCreateProfile function. <br />
<cfscript><br />
dataValues = StructNew();<br />
dataValues.userid = "testm";<br />
dataValues.firstName = "Mike";<br />
dataValues.lastName = "Test";<br />
dataValues.email = "testm@paperthin.com";<br />
// Call Profile Service to create account<br />
pageStatus = application.ptProfile.profileService.autoCreateProfile(dataValues);<br />
// Render out status<br />
WriteOutput("autoCreateLogin status = #pageStatus#");<br />
</cfscript><br />
<br />
[[Category:Profile]]<br />
[[Category:Customization]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Admin_Delete&diff=532PT Profile Admin Delete2010-01-25T00:06:12Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Delete Profile Page is used to delete profiles. Follow these steps to configure the link and page for delete profiles.<br />
<br />
== Steps ==<br />
# Create a new page called 'Delete Profile' in the ''/profileadmin/lightbox/'' subsite. <br />
# In the body of the page, add a Custom Script element.<br />
# From the Custom Script element interface, click the "Edit" icon.<br />
# Enter the following text into the Explicit Module path:<br />
## '/ADF/apps/pt_profile/customcf/handle_profile_delete.cfm' <br />
# Publish the page.<br />
<br />
== Update Profile Site Config ==<br />
This page will be used to delete profile records. Update the ptProfile.xml config file set up during [[PT_Profile Site Configuration|Site Configuration]]. Get the URL for this new page and update the <DELETE_URL> tag value with the page URL. Exclude the site name and leading slash from this value.<br />
*(i.e. <DELETE_URL>webadmin/profileadmin/lightbox/Delete-Profile.cfm</DELETE_URL>).<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Admin_Datasheet&diff=531PT Profile Admin Datasheet2010-01-24T23:59:46Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Profile element is a global custom element. Data for global custom elements can be easily managed with Datasheets. The following sections describe how to configure simple management pages. <br />
<br />
<br />
== Steps ==<br />
# Create a 'profileadmin' subsite for the Profile Admin pages.<br />
# Create a page from the Base Plus One called "Manage Profiles" in the ''/profileadmin/'' subsite.<br />
# In the body of the page, add a Custom Script element.<br />
# From the Custom Script element interface, click the "Edit" icon.<br />
# Enter the following text into the Explicit Module path:<br />
## '/ADF/apps/pt_profile/customcf/profile_admin_ds.cfm'<br />
# From the Datasheet element interface, click the "Datasheet" icon.<br />
# From the "Datasheet Views" dialog, select the "Click here to create a new datasheet view" text.<br />
# Enter the following information and then click "Next:"<br />
## Name: All Profiles<br />
## Private: unchecked<br />
## Default View: unchecked<br />
## Description: View to manage all of the profiles<br />
## Datasheet Source: Form Result/Custom Element Sheet<br />
# From the Datasheet Source dialog, choose the "Profile" custom element and click "Next".<br />
# From the Datasheet Columns dialog, choose a few columns from the Available Columns list and move them to the Selected Columns list. Select the following fields in this order ''UniqueID'', ''UserID'', ''firstname'', ''lastname'', and ''email'' as the first field to display in the table and then click "Finish".<br />
# You will be brought to the Datasheet View page. Click "Close" to return to your page.<br />
# You will now see the datasheet element on this page. Click the Datasheet element interface icon again and this time choose "Edit Columns".<br />
# Select the column field ''UniqueID'' and then the edit button. <br />
# In the Render Handler field, select the ''Change'' button. Enter the following value into the ''Explicit Module'' text box:<br />
## '/ADF/apps/pt_profile/datasheet-modules/datasheet-action-edit-delete-view.cfm'<br />
# Click ''Finish''.<br />
# In the Header field, clear out the text and leave the text field blank. Click ''Finish''.<br />
# Publish this page.<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Admin_Datasheet&diff=530PT Profile Admin Datasheet2010-01-24T23:58:58Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Profile element is a global custom element. Data for global custom elements can be easily managed with Datasheets. The following sections describe how to configure simple management pages. <br />
<br />
'''Recommended:''' to create a 'profileadmin' subsite for the Profile Admin pages.<br />
<br />
== Steps ==<br />
# Create a page from the Base Plus One called "Manage Profiles" in the ''/profileadmin/'' subsite.<br />
# In the body of the page, add a Custom Script element.<br />
# From the Custom Script element interface, click the "Edit" icon.<br />
# Enter the following text into the Explicit Module path:<br />
## '/ADF/apps/pt_profile/customcf/profile_admin_ds.cfm'<br />
# From the Datasheet element interface, click the "Datasheet" icon.<br />
# From the "Datasheet Views" dialog, select the "Click here to create a new datasheet view" text.<br />
# Enter the following information and then click "Next:"<br />
## Name: All Profiles<br />
## Private: unchecked<br />
## Default View: unchecked<br />
## Description: View to manage all of the profiles<br />
## Datasheet Source: Form Result/Custom Element Sheet<br />
# From the Datasheet Source dialog, choose the "Profile" custom element and click "Next".<br />
# From the Datasheet Columns dialog, choose a few columns from the Available Columns list and move them to the Selected Columns list. Select the following fields in this order ''UniqueID'', ''UserID'', ''firstname'', ''lastname'', and ''email'' as the first field to display in the table and then click "Finish".<br />
# You will be brought to the Datasheet View page. Click "Close" to return to your page.<br />
# You will now see the datasheet element on this page. Click the Datasheet element interface icon again and this time choose "Edit Columns".<br />
# Select the column field ''UniqueID'' and then the edit button. <br />
# In the Render Handler field, select the ''Change'' button. Enter the following value into the ''Explicit Module'' text box:<br />
## '/ADF/apps/pt_profile/datasheet-modules/datasheet-action-edit-delete-view.cfm'<br />
# Click ''Finish''.<br />
# In the Header field, clear out the text and leave the text field blank. Click ''Finish''.<br />
# Publish this page.<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Admin_Add&diff=529PT Profile Admin Add2010-01-24T23:48:29Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Add Profile Page will be used to add new profiles. Follow these steps to configure the link and page for adding profiles.<br />
<br />
== Steps ==<br />
# Create a new page called 'Add Profile' in the ''/profileadmin/lightbox/'' subsite. <br />
# In the main content of the page, add a Custom Script element.<br />
# From the Custom Script element interface, click the "Edit" icon.<br />
# Enter the following text into the Explicit Module path:<br />
## '/ADF/apps/pt_profile/customcf/handle_profile_add.cfm' <br />
# Add a simple form element.<br />
# From the Simple Form element interface icons, choose the "Select Form" icon.<br />
# In the Create/Select Simple Form dialog, choose the "Select Simple Form/Custom Element" option and click "next".<br />
# From the Select Form/Custom Element dialog, choose the "Profile" custom element and click "Finish".<br />
# Within the "Manage Simple Form Element" dialog, enter the following information: <br />
## Name: (leave as is)<br />
## Email Notification Recipients: if you would like to receive an e-mail whenever an event is added place your e-mail in here. (optional)<br />
## Sender's Email Address: leave checked<br />
## Anonymous Sender's Email Address: if needed, add an anonymous email address<br />
## Form Action: choose "Display Textblock on Submission" option and add 'Profile successfully created!' text in the RTE. <br />
## Select Finish, then Finish again.<br />
# Publish the page.<br />
<br />
== Update Profile Site Config ==<br />
This page will be used to add new profile records. Update the ptProfile.xml config file that we setup in [[PT_Profile Site Configuration|Site Configuration]]. Get the URL for this page and update the <ADD_URL> tag value with this page URL. Exclude the site name and leading slash from this value.<br />
*(i.e. <ADD_URL>webadmin/profileadmin/lightbox/Add-Profile.cfm</ADD_URL>).<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Import_Content_Known_Issues_and_Bugs&diff=528PT Import Content Known Issues and Bugs2010-01-24T23:38:31Z<p>Renee.mckechnie: /* Known Issues */</p>
<hr />
<div>== Known Issues ==<br />
# Running the "Build Subsite Mapping" tool repeatedly creates multiple records in Subsite Mapping Element (should just place one record per OldSubsiteURL)<br />
# Reload Dashboard button is not working<br />
# Subsites with "underscores" are not being mapped/created correctly<br />
# When a tool is done we need a new message that displays that the tool is done<br />
<br />
[[Category:Import Content]][[Category:Known Issues]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Import_Content_Installation&diff=527PT Import Content Installation2010-01-24T23:37:02Z<p>Renee.mckechnie: </p>
<hr />
<div>'''Important''': Ensure that the [[Installation | ADF is installed]] and functioning correctly before installing PT Import Content.<br />
<br />
== Import Custom Elements ==<br />
Import two custom elements into your site (via the Elements dialog located in the CommonSpot Site Administrator):<br />
<br />
#Subsite Mapping<br />
#Page Mapping<br />
<br />
Note: these elements are located in the /ADF/apps/pt_import_content/exported_objects/ folder<br />
<br />
== Build CCAPI page ==<br />
#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.<br />
# Add the following elements to this page:<br />
## Subsite Mapping<br />
## Page Mapping<br />
# Give each element a unique name (e.g. "subsiteMapElement", "pageMapElement")<br />
# Record the pageID of this new page<br />
<br />
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.<br />
<br />
Switch into Read Mode after creating this page. <br />
<br />
== Create Generic Content Template ==<br />
# 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.<br />
# Place a Textblock Element on the page and give that element a name (e.g. "pageContent").<br />
# Save this page as the Generic Content Template.<br />
<br />
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.<br />
<br />
== Configure Site ==<br />
# Add the following line to the init() function of your sites ADF.cfc (ADF.cfc is located in /yoursite/_cs_apps/ directory)<br />
<br />
loadApp("PTImport", "PTImport");<br />
<br />
# Copy the /pt_import_content/ folder from the /ADF/apps/pt_import_content/site_folder/ folder - into your sites /_cs_apps/ folder<br />
# Copy the /config/ folder from the /ADF/apps/pt_import_content/site_folder/ folder - into your sites /_cs_apps/ folder<br />
# 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.<br />
# 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.<br />
# Modify the Subsite Spread Sheet Mapping document located in the/yoursite /_cs_apps/pt_import_content/data/ folder<br />
<br />
Note: make sure that the Content Creation API is enabled for your server (see the CommonSpot Developer's Guide for more info)<br />
<br />
== Build Import Dashboard Page ==<br />
# Create a page and place a Custom Script Element on the page<br />
# Configure the Custom Script Element to point to the file "main_controller.cfm" located in the /ADF/apps/pt_import_content/customcf/ directory<br />
<br />
[[Category:Import Content]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Roles_Component&diff=526PT Profile Roles Component2010-01-24T23:20:00Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The [[ProfileRoles_Component|ProfileRoles Component]] is required for establishing the logic for roles at global and site levels.<br />
<br />
The [[ProfileRoles_Component|ProfileRoles Component]] contains a ''setRolePermission'' function which controls the rules for the profiles on the site. The function contains a switch statement that examines the passed-in role name and runs through logic to determine a user's permission for the role. <br />
<br />
Every time [[How_to_add_profile_role | a new role is added]], a new case statement for the role should also be added.<br />
<br />
If the site roles or logic differs from the global roles or logic, a [[ProfileRoles_Component|ProfileRoles Component]] can be set up for the site. For details on overriding this component at the site, see the [[Load_ADF_App_Site_Components|Load ADF Application Site Components]] wiki page.<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Roles_Component&diff=525PT Profile Roles Component2010-01-24T23:17:48Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The [[ProfileRoles_Component|ProfileRoles Component]] is required for establishing the logic for roles at the global and site levels.<br />
<br />
The [[ProfileRoles_Component|ProfileRoles Component]] contains a function ''setRolePermission'' which controls the rules for the profiles on the site. The function contains a switch statement that examines the passed-in role name and runs through logic to determine a user's permission for the role. <br />
<br />
Every time [[How_to_add_profile_role | a new role is added]], a new case statement for the role should also be added.<br />
<br />
If the site roles or role logic differs from the global, then a [[ProfileRoles_Component|ProfileRoles Component]] can be set up for the site. For details on overriding this component at the site, see the [[Load_ADF_App_Site_Components|Load ADF Application Site Components]] wiki page.<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Gallery_Element&diff=524PT Profile Gallery Element2010-01-24T23:13:52Z<p>Renee.mckechnie: /* Overview */</p>
<hr />
<div>== Overview ==<br />
The [[Profile Select |Profile Select Element]] allows a contributor to select specific profile records and sort the rendering order.<br />
<br />
== Fields ==<br />
* profileSelect<br />
** Type: General Chooser<br />
** Label: Profile Select<br />
*** Properties<br />
**** Chooser Bean Name: profileGC<br />
<br />
<br />
For more information, view the [[Profile_Select | Profile Select Element]] wiki page.<br />
<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Gallery_Element&diff=523PT Profile Gallery Element2010-01-24T23:13:08Z<p>Renee.mckechnie: /* Fields */</p>
<hr />
<div>== Overview ==<br />
The Profile Select element allows a contributor to select specific profile records and sort the rendering order. <br />
<br />
== Fields ==<br />
* profileSelect<br />
** Type: General Chooser<br />
** Label: Profile Select<br />
*** Properties<br />
**** Chooser Bean Name: profileGC<br />
<br />
<br />
For more information, view the [[Profile_Select | Profile Select Element]] wiki page.<br />
<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Gallery_Element&diff=522PT Profile Gallery Element2010-01-24T23:12:52Z<p>Renee.mckechnie: /* Fields */</p>
<hr />
<div>== Overview ==<br />
The Profile Select element allows a contributor to select specific profile records and sort the rendering order. <br />
<br />
== Fields ==<br />
* profileSelect<br />
** Type: General Chooser<br />
** Label: Profile Select<br />
*** Properties<br />
**** Chooser Bean Name: profileGC<br />
<br />
For more information, view the [[Profile_Select | Profile Select Element]] wiki page.<br />
<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Gallery_Element&diff=521PT Profile Gallery Element2010-01-24T23:12:29Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Profile Select element allows a contributor to select specific profile records and sort the rendering order. <br />
<br />
== Fields ==<br />
* profileSelect<br />
** Type: General Chooser<br />
** Label: Profile Select<br />
*** Properties<br />
**** Chooser Bean Name: profileGC<br />
<br />
For more information, view the [[Profile_Select | Profile Select Element]] wiki page.<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Gallery&diff=520PT Profile Gallery2010-01-24T23:10:22Z<p>Renee.mckechnie: /* Import Custom Element */</p>
<hr />
<div>== Overview ==<br />
The Profile Select element allows a contributor to select profile records to display on a CommonSpot page. The order in which profiles are displayed can be customized.<br />
<br />
The following steps are for will import and implement the Profile Select element.<br />
<br />
== Import Custom Element ==<br />
The Profile Select custom element can be found in the Exported Objects directory (/ADF/apps/pt_profile/exported-objects/).<br />
<br />
Import the Profile Select custom element into the site via the CommonSpot site administrator. <br />
<br />
For additional information, view the [[Profile Select Element|Profile Select Element]] wiki page. <br />
<br />
After import, 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 sites path. <br />
<br />
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'.<br />
<br />
== How to Use This Element ==<br />
To use the Profile Select element:<br />
# Insert the Photo Select element into any content area on a page.<br />
# Select the element indicator and select ''data''.<br />
# In the dialog, you have two boxes on the left and right. The left box contains available items; the right box contains selected items. Drag and drop items from left to right to select; drag and drop from right to left to unselect. The right box selected items can also be sorted for rendering order. To populate the left box of available items, search for text or click the ''show all items'' link. <br />
# Once the items are selected, click finish.<br />
# Finally, assign the ''Listing Highlighted Display'' render handler.<br />
<br />
<br />
[[Category:Profile]]<br />
[[Category:Customization]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Gallery&diff=519PT Profile Gallery2010-01-24T23:09:59Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Profile Select element allows a contributor to select profile records to display on a CommonSpot page. The order in which profiles are displayed can be customized.<br />
<br />
The following steps are for will import and implement the Profile Select element.<br />
<br />
== Import Custom Element ==<br />
The Profile Select custom element can be found in the Exported Objects directory (/ADF/apps/pt_profile/exported-objects/).<br />
<br />
Import the Profile Select custom element into the site via the CommonSpot site administrator. <br />
<br />
For additional information, view the [[Profile Select Element|Profile Select Element]], wiki page. <br />
<br />
After import, 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 sites path. <br />
<br />
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'.<br />
<br />
== How to Use This Element ==<br />
To use the Profile Select element:<br />
# Insert the Photo Select element into any content area on a page.<br />
# Select the element indicator and select ''data''.<br />
# In the dialog, you have two boxes on the left and right. The left box contains available items; the right box contains selected items. Drag and drop items from left to right to select; drag and drop from right to left to unselect. The right box selected items can also be sorted for rendering order. To populate the left box of available items, search for text or click the ''show all items'' link. <br />
# Once the items are selected, click finish.<br />
# Finally, assign the ''Listing Highlighted Display'' render handler.<br />
<br />
<br />
[[Category:Profile]]<br />
[[Category:Customization]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Roles&diff=518PT Profile Roles2010-01-24T23:02:42Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
Profile roles are set up through the [[PT_Profile_Site_Configuration|Site Configuration]] and [[ProfileRoles_Component|ProfileRoles Component]]. These roles establish permissions for the profile and determines which subsites and/or templates the profile page will be derived from. This configuration allows the same profile information to be used for multiple displays throughout the site.<br />
<br />
Profile roles will differ depending on the purpose of the application. For example, if the profiles were implemented in an educational institution, roles could be 'student', 'faculty', and 'staff;' if implemented for healthcare, the roles could be 'doctor', 'surgeon', 'nurse', and 'staff.'<br />
<br />
== Configuration Points ==<br />
* /SiteName/_cs_apps/config/ptProfile.xml<br />
** [[How_to_add_profile_role | Add a new profile role]]<br />
** See the [[PT_Profile_Site Configuration|Site Configuration]] for details on updates for additional roles.<br />
* [[ProfileRoles_Component|ProfileRoles Component]]<br />
* [optional] /ADF/apps/pt_profile/customcf/profile_manager.cfm<br />
** Profile Manager script iterates over the profile roles to display what the logged in user has permissions to access/view. To make a new role render, this needs to be updated manually.<br />
<br />
<br />
<br />
<br />
[[Category:Profile]]<br />
[[Category:Customization]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Roles&diff=517PT Profile Roles2010-01-24T23:00:06Z<p>Renee.mckechnie: /* Configuration Points */</p>
<hr />
<div>== Overview ==<br />
The profile roles are setup through the [[PT_Profile_Site_Configuration|Site Configuration]] and [[ProfileRoles_Component|ProfileRoles Component]]. These roles establish the permissions of the profile and what subsites and/or templates the profile page will be derived. This allows the same profile information to be used for multiple displays through out the site.<br />
<br />
This will differ for the purpose of the application. If the profiles were implemented in an educational institution, then roles could be 'student', 'faculty', and 'staff'. If implemented for healthcare, the roles could be 'doctor', 'surgeon', 'nurse', and 'staff'.<br />
<br />
== Configuration Points ==<br />
* /SiteName/_cs_apps/config/ptProfile.xml<br />
** [[How_to_add_profile_role | Add a new profile role]]<br />
** See the [[PT_Profile_Site Configuration|Site Configuration]] for details on updates for additional roles.<br />
* [[ProfileRoles_Component|ProfileRoles Component]]<br />
* [optional] /ADF/apps/pt_profile/customcf/profile_manager.cfm<br />
** Profile Manager script iterates over the profile roles to display what the logged in user has permissions to access/view. To make a new role render, this needs to be updated manually.<br />
<br />
<br />
<br />
<br />
[[Category:Profile]]<br />
[[Category:Customization]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Roles&diff=516PT Profile Roles2010-01-24T22:58:31Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The profile roles are setup through the [[PT_Profile_Site_Configuration|Site Configuration]] and [[ProfileRoles_Component|ProfileRoles Component]]. These roles establish the permissions of the profile and what subsites and/or templates the profile page will be derived. This allows the same profile information to be used for multiple displays through out the site.<br />
<br />
This will differ for the purpose of the application. If the profiles were implemented in an educational institution, then roles could be 'student', 'faculty', and 'staff'. If implemented for healthcare, the roles could be 'doctor', 'surgeon', 'nurse', and 'staff'.<br />
<br />
== Configuration Points ==<br />
* /SiteName/_cs_apps/config/ptProfile.xml<br />
** See the [[PT_Profile_Site Configuration|Site Configuration]] for details on updates for additional roles.<br />
* [[ProfileRoles_Component|ProfileRoles Component]]<br />
* [optional] /ADF/apps/pt_profile/customcf/profile_manager.cfm<br />
** Profile Manager script iterates over the profile roles to display what the logged in user has permissions to access/view. To make a new role render, this needs to be updated manually.<br />
<br />
[[How_to_add_profile_role | Add a new profile role]]<br />
<br />
<br />
[[Category:Profile]]<br />
[[Category:Customization]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Roles_Component&diff=515PT Profile Roles Component2010-01-24T22:56:40Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The [[ProfileRoles_Component|ProfileRoles Component]] is required for establishing the logic for the roles at the global and site level.<br />
<br />
The [[ProfileRoles_Component|ProfileRoles Component]] contains a function ''setRolePermission''. This function controls the rules for the profiles on the site. The function contains a switch statement for the role name passed in and then runs through logic to determine the users permission for the role. <br />
<br />
Every time [[How_to_add_profile_role | a new role is added]], then a new case statement for the role should be added as well.<br />
<br />
If the site roles or role logic differs from the global, then a [[ProfileRoles_Component|ProfileRoles Component]] can be setup for the site. Follow the wiki page for [[Load_ADF_App_Site_Components|Load ADF Application Site Components]] for details on how to override this component at the site.<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Multiple_Subsites&diff=514PT Profile Multiple Subsites2010-01-24T18:59:20Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Profile App provides the ability to have multiple profile pages in separate subsites. Based on the [[Profile Roles]], a specific subsite can be defined for the subsite id where the profile page will be created.<br />
<br />
== Configuration Point ==<br />
* /SiteName/_cs_apps/pt_profile/config.xml<br />
** See the [[PT_Profile_Site Configuration|Site Configuration]] for details on updates for additional roles.<br />
<br />
[[Category:Profile]]<br />
[[Category:Customization]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Multiple_Templates&diff=513PT Profile Multiple Templates2010-01-24T18:58:25Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Profile App provides the ability to have multiple profile page templates associated with separate roles. Based on the Profile Roles, a specific template can be defined for the role for which the profile page will be created.<br />
<br />
== Configuration Points ==<br />
* /SiteName/_cs_apps/pt_profile/config.xml<br />
** See the [[PT_Profile Site Configuration|Site Configuration]] for details on updates for additional roles.<br />
<br />
[[Category:Profile]]<br />
[[Category:Customization]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=ADF_Core_LightWire_Config_Extended_Base&diff=512ADF Core LightWire Config Extended Base2010-01-24T18:56:57Z<p>Renee.mckechnie: /* Overview */</p>
<hr />
<div>== Overview ==<br />
The Lightwire Config Extended Base is a component file that provides functions to automate the factory object creation.</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Import_Content&diff=511PT Import Content2010-01-24T18:55:10Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The PT Import Content project allows CS Owners to easily import content via the Content Creation API. The basic controls import subsites and page content into Formatted Text Blocks based on a formatted spread sheet. Imported content for subsites and pages can also be re-imported and modified.<br />
<br />
== Process Overview ==<br />
The import process:<br />
# Import Subsite content into the Subsite Mapping Custom Element<br />
# Process the records in the Subsite Mapping Custom Element [create subsites]<br />
# Import Page content into the Page Mapping Custom Element<br />
# Process the records in the Page Mapping Custom Element [create pages]<br />
# Fix Page links<br />
<br />
== Getting Started ==<br />
* [[PT Import Content Installation | Installation]]<br />
* [[PT Import Content Customize Subsite Map data | Customize Subsite Map data]]<br />
* [[PT Import Content Customize Page Map data | Customize Page Map data]]<br />
<br />
== Components ==<br />
* [[PT Import Content ImportController | ImportController]]<br />
=== Subsite ===<br />
* [[PT Import Content SubsiteController | SubsiteController]]<br />
* [[PT Import Content SubsiteMapDAO | SubsiteMapDAO]]<br />
* [[PT Import Content SubsiteDAO | SubsiteDAO]]<br />
<br />
=== Pages ===<br />
* [[PT Import Content PageController | PageController]]<br />
* [[PT Import Content PageMapDAO | PageMapDAO]]<br />
* [[PT Import Content PageDAO | PageDAO]]<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
== [[PT Import Content Known Issues and Bugs | Known Issues/Bugs]] ==<br />
<br />
== Tasks ==<br />
* Delete pages needs CSSecurity integration<br />
* Delete Page and Subsite Mapping content needs CSSecurity integration<br />
* Update Page Mapping - set NeedsUpdate = 1 (to reprocess content)<br />
* Fix Links Method for PageController.cfc<br />
<br />
<br />
=== Reports ===<br />
* Pages Mapped<br />
* Subsites Mapped<br />
* Subsites Created<br />
* Subsites Needed to be Created<br />
* Pages Needed to be Updated<br />
<br />
[[Category:Import Content]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Extended_Elements&diff=510PT Profile Extended Elements2010-01-24T18:50:30Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
Additional elements can be connected to the base profile element to extend the information/data within the profile element. Allows the profile fields to be expanded with adding new classifications of data.<br />
<br />
<br />
[[Category:Profile]]<br />
[[Category:Customization]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=Known_Issues&diff=509Known Issues2010-01-24T18:45:14Z<p>Renee.mckechnie: /* Known Issues/Bugs */</p>
<hr />
<div>== Known Issues/Bugs ==<br />
* When the server is restarted, the ADF initial build fails. To fix, [[Reset ADF | Reset the ADF]].<br />
<br />
[[Category:Known Issues]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=Known_Issues&diff=508Known Issues2010-01-24T18:44:56Z<p>Renee.mckechnie: /* Known Issues/Bugs */</p>
<hr />
<div>== Known Issues/Bugs ==<br />
* When the server is restarted, the ADF initial build fails. To fix, [[Reset ADF | REset the ADF]].<br />
<br />
[[Category:Known Issues]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=How_to_add_profile_role&diff=495How to add profile role2010-01-24T18:03:55Z<p>Renee.mckechnie: </p>
<hr />
<div>Adding a new profile role is a valuable piece to the profile application. To add a new profile role:<br />
<br />
# Update the [[PT_Profile Site_Configuration|Site Configuration]] with the new role. Add a new tag under the <ROLES> tag with the name of the role. Next, you'll add the SUBSITE_ID and TEMPLATE_ID tags.<br />
# Populate SUBSITE_ID by creating a new subsite for the profile pages and update the ID in the configuration file. See the [[PT_Profile Subsites|Subsites]] wiki page for additional details.<br />
# Populate TEMPLATE_ID by creating a new template for the profile pages and update the ID in the configuration file. See the [[PT_Profile_Template|Profile_Template]] wiki page for additional details. (Note: This step is optional - you can also use one template for all profile roles.)<br />
# Depending on the complexity of your roles and how many sites are implementing the profile app, you can either update the [[ProfileRoles_Component|ProfileRoles Component]] with the new roles.<br />
## To update the ProfileRoles.cfc:<br />
### Locate the '/ADF/apps/pt_profile/components/profileRoles.cfc' file<br />
### In the ''setRolePermission'' function, add a new case statement for the role name. Add your logic to set the roles permmission.<br />
<br />
[[Category:Profile]]<br />
[[Category:How-to Guide]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=How_to_add_profile_role&diff=494How to add profile role2010-01-24T18:03:04Z<p>Renee.mckechnie: </p>
<hr />
<div>== Add a New Profile Role ==<br />
Adding a new profile role is a valuable piece to the profile application. To add a new profile role:<br />
<br />
# Update the [[PT_Profile Site_Configuration|Site Configuration]] with the new role. Add a new tag under the <ROLES> tag with the name of the role. Next, you'll add the SUBSITE_ID and TEMPLATE_ID tags.<br />
# Populate SUBSITE_ID by creating a new subsite for the profile pages and update the ID in the configuration file. See the [[PT_Profile Subsites|Subsites]] wiki page for additional details.<br />
# Populate TEMPLATE_ID by creating a new template for the profile pages and update the ID in the configuration file. See the [[PT_Profile_Template|Profile_Template]] wiki page for additional details. (Note: This step is optional - you can also use one template for all profile roles.)<br />
# Depending on the complexity of your roles and how many sites are implementing the profile app, you can either update the [[ProfileRoles_Component|ProfileRoles Component]] with the new roles.<br />
## To update the ProfileRoles.cfc:<br />
### Locate the '/ADF/apps/pt_profile/components/profileRoles.cfc' file<br />
### In the ''setRolePermission'' function, add a new case statement for the role name. Add your logic to set the roles permmission.<br />
<br />
[[Category:Profile]]<br />
[[Category:How-to Guide]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=How_to_add_profile_role&diff=493How to add profile role2010-01-24T17:53:48Z<p>Renee.mckechnie: </p>
<hr />
<div>== Add a New Profile Role ==<br />
Adding a new profile role is a valuable piece to the profile application. The following is a list of steps and options to consider moving forward.<br />
<br />
# Update the [[PT_Profile Site_Configuration|Site Configuration]] with the new role. Add a new tag under the <ROLES> tag for the name of the role. Also, remember the SUBSITE_ID and TEMPLATE_ID tags.<br />
# Populate the SUBSITE_ID by creating a new subsite for the profile pages and update the ID in the configuration file. More details are on the [[PT_Profile Subsites|Subsites]] wiki page.<br />
# Populate the TEMPLATE_ID by creating a new template for the profile pages and update the ID in the configuration file. More details are on the [[PT_Profile_Template|Profile_Template]] wiki page. This is optional, b/c you can use one template for all profile roles.<br />
# Depending on the complexity of your roles and how many sites are implementing the profile app, you can either update the [[ProfileRoles_Component|ProfileRoles Component]] with the new roles.<br />
## To update the ProfileRoles.cfc:<br />
### Locate the '/ADF/apps/pt_profile/components/profileRoles.cfc' file<br />
### In the ''setRolePermission'' function, add a new case statement for the role name. Add your logic to set the roles permmission.<br />
<br />
[[Category:Profile]]<br />
[[Category:How-to Guide]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=Create_SVN_Branch&diff=492Create SVN Branch2010-01-24T17:42:03Z<p>Renee.mckechnie: /* Overview */</p>
<hr />
<div>== Overview ==<br />
A key feature of version control systems is the ability to isolate changes into a separate line of development known as a ''branch''. Branches are often used to try out new features without disturbing the main line of development with compiler errors and bugs. As soon as the new feature is stable, the development branch is ''merged'' back into the main branch (trunk). <br />
<br />
Subversion does not have special commands for branching, but uses so-called ''cheap copies'' instead. (Cheap copies are similar to hard links in Unix) Instead of making a complete copy in the repository, an internal link is created, pointing to a specific tree/revision. As a result, branches are very quick to create and take up almost no extra space in the repository.<br />
<br />
For more information: [http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-branchtag.html TortoiseSVN branching/tagging]<br />
<br />
== Create a New Branch ==<br />
Follow the steps below to create a new branch and set it as your working copy.<br />
<br />
# Locate the Apps directory (not within the ADF directory) and right click the checked out SVN repository. From the menu, select ''TortoiseSVN'' > ''Branch/tag...''.<br />
## [[File:svn_apps_04.jpg]]<br />
# In the ''Copy'' dialog, enter the URL for the new branch. It will be something like ''http://consulting.paperthin.com/svn/pt_article_editor/branches/1.0.0''. For the other fields in the dialog, select ''HEAD revision in the repository'' and check the box for ''Switch working copy to new branch/tag'' <br />
## [[File:svn_apps_05.jpg]]<br />
<br />
[[Category: How-to Guide]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=Create_SVN_Branch&diff=491Create SVN Branch2010-01-24T17:41:40Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
A key feature of version control systems is the ability to isolate changes into a separate line of development known as a ''branch''. Branches are often used to try out new features without disturbing the main line of development with compiler errors and bugs. As soon as the new feature is stable, the development branch is ''merged'' back into the main branch (trunk). <br />
<br />
Subversion does not have special commands for branching, but uses so-called ''cheap copies'' instead. (Cheap copies are similar to hard links in Unix) Instead of making a complete copy in the repository, an internal link is created, pointing to a specific tree/revision. As a result, branches are very quick to create and take up almost no extra space in the repository.<br />
<br />
For more information: [http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-branchtag.html | TortoiseSVN branching/tagging]<br />
<br />
== Create a New Branch ==<br />
Follow the steps below to create a new branch and set it as your working copy.<br />
<br />
# Locate the Apps directory (not within the ADF directory) and right click the checked out SVN repository. From the menu, select ''TortoiseSVN'' > ''Branch/tag...''.<br />
## [[File:svn_apps_04.jpg]]<br />
# In the ''Copy'' dialog, enter the URL for the new branch. It will be something like ''http://consulting.paperthin.com/svn/pt_article_editor/branches/1.0.0''. For the other fields in the dialog, select ''HEAD revision in the repository'' and check the box for ''Switch working copy to new branch/tag'' <br />
## [[File:svn_apps_05.jpg]]<br />
<br />
[[Category: How-to Guide]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=ADF_Core_Bean_Config&diff=490ADF Core Bean Config2010-01-24T17:33:06Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Core Bean Configuration file for the lightwire framework creates the singletons and dependencies for the ADF.<br />
<br />
== Architecture ==<br />
The Bean Configuration file extends the [[Lightwire Config Extended Base|Lightwire Config Extended Base]] component file. <br />
<br />
The configuration file sets up the factory objects for all components in the [[lib]] directory and initiates the [[App Bean Config|App Bean Config]] for the custom applications.<br />
* loadADFLibComponents function in the [[Lightwire Config Extended Base|Lightwire Config Extended Base]]. The parameters are the ADF directory to locate all components and the directories to exclude. This function locates and creates singletons for all the components in the argument directory.<br />
/*<br />
* Build bean objects for all components in the ADF\LIB directory<br />
* Argument 1 = Directory to recurse for component files<br />
* Argument 2 = Director names to exclude<br />
*/<br />
loadADFLibComponents("ADF\lib\", "ajax");<br />
* Create the CoreConfig object into the factory.<br />
/*<br />
* Load the singleton for the Core Config file<br />
*/<br />
addSingleton("ADF.core.Config", "CoreConfig");<br />
* loadADFAppBeanConfig function in the [[Lightwire Config Extended Base|Lightwire Config Extended Base]] locates all the [[App Bean Config|App Bean Config]] files under the [[apps]] directory.<br />
/*<br />
* Load the ADF application bean configuration files (appBeanConfig.cfc)<br />
*/<br />
loadADFAppBeanConfig();<br />
* loadSiteAppBeanConfig function in the [[Lightwire Config Extended Base|Lightwire Config Extended Base]] locates all the [[App Bean Config|App Bean Config]] files under the sites.<br />
/*<br />
* Load the site level application bean configuration files (appBeanConfig.cfc)<br />
*/<br />
loadSiteAppBeanConfig();<br />
* loadSiteComponents function in the [[Lightwire Config Extended Base|Lightwire Config Extended Base]] locates the site components to include in the object factory.<br />
/*<br />
* Load the site level components into application.ADF space.<br />
* Recurse through the '/_cs_apps/components/' directory for each site.<br />
*/<br />
loadSiteComponents();<br />
<br />
[[Category:Core]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=Overview&diff=486Overview2010-01-24T17:06:00Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Application Development Framework (ADF) provides a common library of building blocks for CommonSpot custom applications. The ADF is located at the server level and is accessible from all sites on the server.<br />
<br />
Visit the [[Glossary|Term Glossary]] for definitions of the terminology used with the lightwire object factory.<br />
<br />
The ADF is a series of components and methodology to build apps within CommonSpot. ([[Licenses|Read the licensing details]])<br />
<br />
== Architecture ==<br />
The ADF is built on the LightWire object factory framework. The object factory is configured and saved in server scope. <br />
ADF directory structure:<br />
* [[Apps|Apps]] - Location of the custom applications to be used throughout the server.<br />
* [[Core|Core]] - Configuration components that build and control the ADF.<br />
* [[Extensions|Extensions]] - Directory of custom scripts, custom field types, datasheet modules, render handlers, etc, used in development of custom applications.<br />
* [[Lib|Lib]] - Library of components.<br />
* [[ThirdParty|ThirdParty]] - Third party software used in the ADF.<br />
<br />
== Security ==<br />
[[Security|Read about ADF security]]<br />
<br />
== ADF Library ==<br />
[[Library|Library]] provided within the ADF.<br />
<br />
== Installation Steps/Requirements ==<br />
<br />
Minimum requirements for the ADF:<br />
* ColdFusion 8<br />
* Windows/Unix<br />
* CommonSpot 5.0.3 (Hot Fix 11) or above<br />
<br />
<br />
[[Installation|Step-by-step installation instructions]] for the ADF on your server.<br />
<br />
[[Naming Conventions|ADF Naming Conventions]]<br />
<br />
== Custom Applications ==<br />
* [[Custom Application Configuration|Custom Application Configuration]]<br />
* [[Custom Application ADF Library Overrides|Custom Application ADF Library Overrides]]<br />
* [[Custom Application Site Level Configuration|Custom Application Site Level Configuration]]<br />
* [[Custom Application Site Level Customization|Custom Application Site Level Customization]]<br />
<br />
== Starter Application ==<br />
A [[Starter Application|Starter Application]] can be used as a base to develop new applications.<br />
<br />
== Auto CFC Documentation ==<br />
Documentation for the ADF library components is automatically generated based on metadata from the component files. This self-documenting process ensures documentation for the ADF library components remains in-sync with the code. <br />
<br />
To produce complete documentation, the component needs:<br />
* Component hints<br />
* Function hints<br />
* Argument hints<br />
* Properties<br />
<br />
== Known Issues/Bugs ==<br />
* [[Bug_Tracking|Bug Tracking]]<br />
<br />
[[Category:Landing Page]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=App_Bean_Config&diff=485App Bean Config2010-01-24T16:57:28Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The App Bean Config is the custom application configuration file for the lightwire object factory. This file establishes the bean configuration with application-specific components and ADF library components.<br />
<br />
The App Bean Config must have the file name 'AppBeanConfig.cfm' and be located at the root of the custom application directory.<br />
<br />
== Architecture ==<br />
The App Bean Config is separated into six sections: <br />
* Initialization: set up variables to be used in this configuration file.<br />
// App specific variables<br />
appBeanName = "STARTER_APP";<br />
// Get the com path for the current custom application<br />
appComPath = getComPathForCustomAppDir(GetCurrentTemplatePath());<br />
* Load the custom application App component. This component extends the Core Application Base component (\ADF\Core\AppBase.cfc) in the ADF [[Core]], creating the custom application singleton where the dependencies will be injected.<br />
// Load the APP Base<br />
addSingleton("#appComPath#App", appBeanName);<br />
* Load the custom application components. Create singletons, transients, and dependencies for the specific components within the custom application.<br />
// Load the STARTER APP service component<br />
/* <br />
addSingleton("#appComPath#MYCOMPONENT", "MYCOMPONENT");<br />
addConstructorDependency(appBeanName, "MYCOMPONENT");<br />
*/<br />
* Load the ADF library components. Create the dependencies to the custom application singleton. <br />
// Dependecies from ADF Lib<br />
addConstructorDependency(appBeanName, "cedata_1_0", "cedata");<br />
addConstructorDependency(appBeanName, "scripts_1_0", "scripts");<br />
* Call the ADFOverrides function. This function overrides ADF library components at the custom application level.<br />
// Load the Custom App overrides<br />
ADFOverrides(appComPath, appBeanName);<br />
* Call the loadAppSiteComponents function. This function loads the site level application components into the object factory, giving objects a unique name with the ''AppBeanName_SiteID_ComponentName''.<br />
//Load the site level application components<br />
loadAppSiteComponents(appBeanName);<br />
<br />
== App Component (App.cfc) ==<br />
All custom applications must contain the App component (App.cfc).<br />
<br />
This file is a simple component used as the base object for the custom application where all dependencies will be injected. This component extends the AppBase component in the ADF [[Core|Core]].</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=App_Bean_Config&diff=484App Bean Config2010-01-24T16:55:51Z<p>Renee.mckechnie: /* Architecture */</p>
<hr />
<div>== Overview ==<br />
The App Bean Config is the custom application configuration file for the lightwire object factory. This file establishes the bean configuration with application-specific components and ADF library components.<br />
<br />
The App Bean Config must have the file name 'AppBeanConfig.cfm' and be located at the root of the custom application directory.<br />
<br />
== Architecture ==<br />
The App Bean Config is separated into 6 sections: <br />
* Initialization: set up variables to be used in this configuration file.<br />
// App specific variables<br />
appBeanName = "STARTER_APP";<br />
// Get the com path for the current custom application<br />
appComPath = getComPathForCustomAppDir(GetCurrentTemplatePath());<br />
* Load the custom application App component. This component extends the Core Application Base component (\ADF\Core\AppBase.cfc) in the ADF [[Core]], creating the custom application singleton where the dependencies will be injected.<br />
// Load the APP Base<br />
addSingleton("#appComPath#App", appBeanName);<br />
* Load the custom application components. Create singletons, transients, and dependencies for the specific components within the custom application.<br />
// Load the STARTER APP service component<br />
/* <br />
addSingleton("#appComPath#MYCOMPONENT", "MYCOMPONENT");<br />
addConstructorDependency(appBeanName, "MYCOMPONENT");<br />
*/<br />
* Load the ADF library components. Create the dependencies to the custom application singleton. <br />
// Dependecies from ADF Lib<br />
addConstructorDependency(appBeanName, "cedata_1_0", "cedata");<br />
addConstructorDependency(appBeanName, "scripts_1_0", "scripts");<br />
* Call the ADFOverrides function. This function overrides ADF library components at the custom application level.<br />
// Load the Custom App overrides<br />
ADFOverrides(appComPath, appBeanName);<br />
* Call the loadAppSiteComponents function. This function loads the site level application components into the object factory, giving objects a unique name with the ''AppBeanName_SiteID_ComponentName''.<br />
//Load the site level application components<br />
loadAppSiteComponents(appBeanName);<br />
<br />
== App Component (App.cfc) ==<br />
All custom applications must contain the App component (App.cfc).<br />
<br />
This is a simple component that is used as the base object for the custom application where all the dependencies will be injected. This component extends the AppBase component in the ADF [[Core|Core]].</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=App_Bean_Config&diff=483App Bean Config2010-01-24T16:50:46Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The App Bean Config is the custom application configuration file for the lightwire object factory. This file establishes the bean configuration with application-specific components and ADF library components.<br />
<br />
The App Bean Config must have the file name 'AppBeanConfig.cfm' and be located at the root of the custom application directory.<br />
<br />
== Architecture ==<br />
The App Bean Config is separated into 5 sections. <br />
* Initialization, setup for the variables to be used in this configuration file.<br />
// App specific variables<br />
appBeanName = "STARTER_APP";<br />
// Get the com path for the current custom application<br />
appComPath = getComPathForCustomAppDir(GetCurrentTemplatePath());<br />
* Load the custom application App component. This components extends the Core Application Base component (\ADF\Core\AppBase.cfc) in the ADF [[Core]]. This creates the custom applications singleton where the dependencies will be injected.<br />
// Load the APP Base<br />
addSingleton("#appComPath#App", appBeanName);<br />
* Load the custom application components. Create singletons, transients, and dependencies for the specific components within the custom application.<br />
// Load the STARTER APP service component<br />
/* <br />
addSingleton("#appComPath#MYCOMPONENT", "MYCOMPONENT");<br />
addConstructorDependency(appBeanName, "MYCOMPONENT");<br />
*/<br />
* Load the ADF library components. Create the dependencies to the custom application singleton. <br />
// Dependecies from ADF Lib<br />
addConstructorDependency(appBeanName, "cedata_1_0", "cedata");<br />
addConstructorDependency(appBeanName, "scripts_1_0", "scripts");<br />
* Call the ADFOverrides function. This creates the overrides at the custom application level to the ADF library components.<br />
// Load the Custom App overrides<br />
ADFOverrides(appComPath, appBeanName);<br />
* Call the loadAppSiteComponents function. This function loads the site level application components into the object factory. This gives the objects a unique name with the ''AppBeanName_SiteID_ComponentName''.<br />
//Load the site level application components<br />
loadAppSiteComponents(appBeanName);<br />
<br />
== App Component (App.cfc) ==<br />
All custom applications must contain the App component (App.cfc).<br />
<br />
This is a simple component that is used as the base object for the custom application where all the dependencies will be injected. This component extends the AppBase component in the ADF [[Core|Core]].</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=App_Bean_Config&diff=482App Bean Config2010-01-24T16:49:40Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The App Bean Config is the custom application configuration file for the lightwire object factory. This file establishes the bean configuration with application-specific components and ADF library components.<br />
<br />
The [[App Bean Config|App Bean Config]] must have the file name 'AppBeanConfig.cfm'.<br />
<br />
The file is located at the root of the custom application directory.<br />
<br />
== Architecture ==<br />
The [[App Bean Config|App Bean Config]] is separated into 5 sections. <br />
* Initialization, setup for the variables to be used in this configuration file.<br />
// App specific variables<br />
appBeanName = "STARTER_APP";<br />
// Get the com path for the current custom application<br />
appComPath = getComPathForCustomAppDir(GetCurrentTemplatePath());<br />
* Load the custom application App component. This components extends the Core Application Base component (\ADF\Core\AppBase.cfc) in the ADF [[Core]]. This creates the custom applications singleton where the dependencies will be injected.<br />
// Load the APP Base<br />
addSingleton("#appComPath#App", appBeanName);<br />
* Load the custom application components. Create singletons, transients, and dependencies for the specific components within the custom application.<br />
// Load the STARTER APP service component<br />
/* <br />
addSingleton("#appComPath#MYCOMPONENT", "MYCOMPONENT");<br />
addConstructorDependency(appBeanName, "MYCOMPONENT");<br />
*/<br />
* Load the ADF library components. Create the dependencies to the custom application singleton. <br />
// Dependecies from ADF Lib<br />
addConstructorDependency(appBeanName, "cedata_1_0", "cedata");<br />
addConstructorDependency(appBeanName, "scripts_1_0", "scripts");<br />
* Call the ADFOverrides function. This creates the overrides at the custom application level to the ADF library components.<br />
// Load the Custom App overrides<br />
ADFOverrides(appComPath, appBeanName);<br />
* Call the loadAppSiteComponents function. This function loads the site level application components into the object factory. This gives the objects a unique name with the ''AppBeanName_SiteID_ComponentName''.<br />
//Load the site level application components<br />
loadAppSiteComponents(appBeanName);<br />
<br />
== App Component (App.cfc) ==<br />
All custom applications must contain the App component (App.cfc).<br />
<br />
This is a simple component that is used as the base object for the custom application where all the dependencies will be injected. This component extends the AppBase component in the ADF [[Core|Core]].</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Template&diff=480PT Profile Template2009-12-24T01:51:32Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
Pages built from the Profiles Template will be the base definition for the profiles. To construct your Profiles Template complete the following steps. <br />
<br />
== Steps ==<br />
# Create a CommonSpot page called 'Profile' from the Base Plus One template. (The subsite for this is not critical but it may be a good idea to create a subsite called profiles). <br />
# Place the 'Profile' Custom Element on this page.<br />
# Click "Render Mode" in the element interface.<br />
# Select 'Display existing element data (content reuse)' on the 'Rendering Mode' tab.<br />
# Select the 'Filter' tab. <br />
# Select Filter Type to 'Show subset of records'.<br />
# Select the field drop-down as the 'uniqueID' field. <br />
# Select the operator as 'Equals'.<br />
# Click the '...' button to open the ColdFusion expression window.<br />
# Enter the text 'request.page.metadata.profiles.uniqueid' as the expression and check the 'force cache' checkbox. Click 'OK' and then check the box to 'Ignore ColdFusion error', then click 'Ok'.<br />
# Click 'Ok' on the render mode window.<br />
# Click "More" in the element interface. Then the "Custom Render Handlers" menu option, and choose the "Full Page" Render Handler.<br />
# Submit Page and then Save as Template.<br />
# Remember to submit the template for public use.<br />
# Go to the CommonSpot Site Administration and bind the 'profiles' metadata form to this 'Profile Template'.<br />
<br />
== Update Profile Site Config ==<br />
This template will be used to create profile pages. Update the pt_profile.xml config file that we setup in [[PT_Profile Site Configuration|Site Configuration]]. Get the pageid for this page and update the <TEMPLATE_ID> tag value with the pageid.<br />
<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Subsites&diff=479PT Profile Subsites2009-12-24T01:51:01Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
Profile pages can to be created in a specific subsite. The subsites for the profile pages can differ by role. Each role can have it's own subsite. This is managed in the [[PT_Profile Site Configuration|Site Configuration]]. <br />
<br />
Follow the steps to create a new subsite and update the pt_profile config file.<br />
<br />
== Profile Admin Subsite ==<br />
It is '''highly recommended''' that the Profile Admin subsite be created for administrators. This allows security to be setup for the subsite to allow only administrators access.<br />
<br />
# Create a new subsite called ''profileAdmin''.<br />
# Create a new subsite within the ''profileAdmin'' subsite called ''lightbox''. This will be used for the lightbox pages.<br />
# Configure the ''lightbox'' General Security to not inherit security from parent. When the installation is completed, comeback and remove the ''Show CommonSpot Interface'' permission from all groups and users.<br />
# Configure the ''lightbox'' Content Security to not inherit security from parent. Change the ''Authenticated Users'' to only have read permissions.<br />
# Configure the ''profileAdmin'' subsite Content Security to give 'No Rights' to 'Anonymous Users' and 'Authenticated Users'. <br />
# Configure the ''profileAdmin'' subsite Content Security to allow permissions to the group of administrators that will manage the Photos.<br />
<br />
'''Note:''' We are setting up separate security for the ''lightbox'' subsite because these pages security will differ from the ''profileAdmin'' subsite.<br />
<br />
== Profile Roles Subsite ==<br />
# Create a new subsite called 'general' (where 'general' is the role name).<br />
# Find the subsite id for the new 'general' subsite.<br />
<br />
== Update Profile Site Config ==<br />
This subsite will be used to store the profile pages. Update the pt_profile.xml config file that we setup in [[PT_Profile Site Configuration|Site Configuration]]. Update the <SUBSITE_ID> tag value with the subsite id for the subsite you just created.<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Listing&diff=477PT Profile Listing2009-12-24T01:49:44Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
Profile listing page is a sample page to demonstrate a display for the profile records. To configure this page do the following steps.<br />
<br />
== Steps ==<br />
# Create a new page from the Base Plus One Template, call this page "Profile Listing" (the name is not important and is only used for reference). This page can be created in any subsite (not specifically the profileadmin subsite). The page does needs to be accessible by all users, therefore the best place is at the root or a profile subsite. <br />
# In the content area of the page place the "Profile" custom element.<br />
# Choose the "content reuse" option and leave the option for "Render results dynamically...".<br />
# Click to the "Filter tab" and choose the "Show all records" radio button.<br />
# From the "Sort Order" option, sort by "UserID", "Ascending" (Any sort order can be used here).<br />
# Then click "Ok" on the entire Rendering Mode dialog.<br />
# From the "Custom Render Handlers" menu option, choose the "Listing Large Display" Render Handler.<br />
# Publish the page.<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Dashboard&diff=476PT Profile Dashboard2009-12-24T01:48:48Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
Profile Dashboard is used as a profile overview page for a single user. This is a custom script that gathers information for the user logged in and renders the profile info, edit link, and profile role pages.<br />
<br />
To configure the detail viewing page, complete the following steps.<br />
<br />
== Steps ==<br />
# Create a new page from the Base Plus One Template previously created, call this page "Profile Dashboard" (the name is important for other links). This page can be created in any subsite (not specifically the profileadmin subsite). The page does needs to be accessible by all users, therefore the best place is at the root or a ''profile'' subsite.<br />
# In the content area of the page place the Custom Script element.<br />
# Click the element indicator and select the "Edit" button.<br />
# In the Explicit Module path, enter the following path: <br />
## /ADF/apps/pt_profile/customcf/profile_dashboard.cfm<br />
# Publish the page.<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_CCAPI_Configuration&diff=475PT Profile CCAPI Configuration2009-12-24T01:48:23Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Profile Application uses the [[CCAPI|ADF CCAPI]] to populate profile records and create profile pages. This needs to be configured for the site and profile app.<br />
<br />
Follow the steps to setup the [[CCAPI Config|CCAPI Config]] file for the site if this is not done. Once this is completed, follow the steps below to setup the CCAPI config for the Profile App. Make sure to update the ''wsVars'' section with the correct URL's and username/password.<br />
<br />
== Setup ==<br />
'''Recommended''' to create a 'webadmin' subsite for this Profile CCAPI page.<br />
<br />
# Create a new page called 'ccapiProfile'. <br />
# Add the 'Profile' element to the page.<br />
# Select the 'Profile' element indicator and go to 'more...'. Select 'Name' from the menu.<br />
# In the Element Name field, enter the text 'ccapiProfileElement'.<br />
# Publish this page and put in read mode.<br />
# Edit the 'ccapi.xml' file for the site and add the following xml block into the <elements> section:<br />
<Profile><br />
<pageID>#####</pageID><br />
<subsiteID>##</subsiteID><br />
<elementType>custom</elementType><br />
<controlName>ccapiProfileElement</controlName><br />
</Profile><br />
# To populate the <pageID> and <subsiteID> tags, view the source code for the 'ccapiProfile' page that was just created. <br />
# Identify the following line in the source code and enter this numeric value into the <subsiteID> tag:<br />
var jsSubSiteID = ##;<br />
# Identify the following line in the source code and enter this numeric value into the <pageID> tag:<br />
var jsPageID = ####;<br />
# The ADF needs to be reset for the server and site for these CCAPI updates to take effect. Enter the following URL parameter string to any page call within the site:<br />
?resetServerADF=1&resetSiteADF=1<br />
'''Note: Resetting the ADF server might affect all sites implementing the ADF.''' If an error occurs, this could cause sites to go down. Needless to say, updates to the ADF Bean Configs and config files should be done in a controlled development environment (not on production servers!).<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Admin_Delete&diff=474PT Profile Admin Delete2009-12-24T01:47:16Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Add Profile Page will be used to add new profiles. Follow these steps to configure the link and page for adding profiles.<br />
<br />
== Steps ==<br />
# Create a new page called 'Delete Profile', in the ''/profileadmin/lightbox/'' subsite. <br />
# In the main content of the page place a Custom Script element.<br />
# From the Custom Script element interface, click the "Edit" icon.<br />
# Enter the following text into the Explicit Module path:<br />
## '/ADF/apps/pt_profile/customcf/handle_profile_delete.cfm' <br />
# Publish the page<br />
<br />
== Update Profile Site Config ==<br />
This page will be used to add delete profile records. Update the ptProfile.xml config file that we setup in [[PT_Profile Site Configuration|Site Configuration]]. Get the URL for this page and update the <DELETE_URL> tag value with the page URL. Exclude the site name and leading slash from this value.<br />
*(i.e. <DELETE_URL>webadmin/profileadmin/lightbox/Delete-Profile.cfm</DELETE_URL>).<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Admin_Datasheet&diff=473PT Profile Admin Datasheet2009-12-24T01:46:39Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Profile element is a global custom element. Managing data for global custom elements can be configured easily through the use of Datasheets. The following sections will describe how to configure some simple pages to manage the data for the events. <br />
<br />
'''Recommended''' to create a 'profileadmin' subsite for the Profile Admin pages.<br />
<br />
== Steps ==<br />
# Create a page from the Base Plus One called "Manage Profiles", in the ''/profileadmin/'' subsite.<br />
# In the main content of the page place a Custom Script element.<br />
# From the Custom Script element interface, click the "Edit" icon.<br />
# Enter the following text into the Explicit Module path:<br />
## '/ADF/apps/pt_profile/customcf/profile_admin_ds.cfm'<br />
# From the Datasheet element interface, click the "Datasheet" icon.<br />
# From the "Datasheet Views" dialog, click the "Click here to create a new datasheet view" text.<br />
# Enter the following information and then click "Next":<br />
## Name: All Profiles<br />
## Private: unchecked<br />
## Default View: unchecked<br />
## Description: View to manage all of the profiles<br />
## Datasheet Source: Form Result/Custom Element Sheet<br />
# From the Datasheet Source dialog choose the "Profile" custom element and click "Next".<br />
# From the Datasheet Columns Dialog choose a few columns from the Available Columns list and move them to the Selected Columns list. Select the following fields in this order ''UniqueID'', ''UserID'', ''firstname'', ''lastname'', and ''email'' as the first field to display in the table and then click "Finish".<br />
# You will be brought to the Datasheet View page click "Close" to return to your page.<br />
# You will see the datasheet element on this page now. Click the Datasheet element interface icon again and this time choose "Edit Columns".<br />
# Select the column field ''UniqueID'' and then the edit button. <br />
# In the Render Handler field, select the ''Change'' button. Enter the following value into the ''Explicit Module'' text box:<br />
## '/ADF/apps/pt_profile/datasheet-modules/datasheet-action-edit-delete-view.cfm'<br />
# Click ''Finish''.<br />
# In the Header field, clear out the text and leave the text field blank. Click ''Finish''.<br />
# Publish this page.<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Admin_Add&diff=472PT Profile Admin Add2009-12-24T01:45:50Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The Add Profile Page will be used to add new profiles. Follow these steps to configure the link and page for adding profiles.<br />
<br />
== Steps ==<br />
# Create a new page called 'Add Profile', in the ''/profileadmin/lightbox/'' subsite. <br />
# In the main content of the page place a Custom Script element.<br />
# From the Custom Script element interface, click the "Edit" icon.<br />
# Enter the following text into the Explicit Module path:<br />
## '/ADF/apps/pt_profile/customcf/handle_profile_add.cfm' <br />
# From the Simple Form element interface icons choose the "Select Form" icon.<br />
# In the Create/Select Simple Form dialog choose the option to "Select Simple Form/Custom Element" option and click "next".<br />
# From the Select Form/Custom Element dialog choose the "Profile" custom element and click "Finish".<br />
# Within the "Manage Simple Form Element" dialog enter the following information: <br />
## Name: (leave as is)<br />
## Email Notification Recipients: (If you would like to receive an e-mail whenever an event is added place your e-mail in here. This is optional)<br />
## Sender's Email Address: leave checked<br />
## Anonymous Sender's Email Address: (add in an anonymous email address if needed)<br />
## Form Action: choose "Display Textblock on Submission" option and add 'Profile successfully created!' text in the RTE. <br />
## Select Finish and then Finish again.<br />
# Publish the page<br />
<br />
== Update Profile Site Config ==<br />
This page will be used to add new profile records. Update the ptProfile.xml config file that we setup in [[PT_Profile Site Configuration|Site Configuration]]. Get the URL for this page and update the <ADD_URL> tag value with the page URL. Exclude the site name and leading slash from this value.<br />
*(i.e. <ADD_URL>webadmin/profileadmin/lightbox/Add-Profile.cfm</ADD_URL>).<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Import_Content&diff=471PT Import Content2009-12-24T01:44:42Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The PT Import Content project will allow CS Owners to easily import content via the Content Creation API. The basic controls are to import subsites based on a formatted spread sheet and to import page content into Formatted Text Blocks. Imported content for subsites and pages can be re-imported and modified.<br />
<br />
== General Process ==<br />
The Import process looks like this:<br />
# Import Subsite content into the Subsite Mapping Custom Element<br />
# Process the records in the Subsite Mapping Custom Element [create subsites]<br />
# Import Page content into the Page Mapping Custom Element<br />
# Process the records in the Page Mapping Custom Element [create pages]<br />
# Fix Page links<br />
<br />
== Getting Started ==<br />
* [[PT Import Content Installation | Installation]]<br />
* [[PT Import Content Customize Subsite Map data | Customize Subsite Map data]]<br />
* [[PT Import Content Customize Page Map data | Customize Page Map data]]<br />
<br />
== Components ==<br />
* [[PT Import Content ImportController | ImportController]]<br />
=== Subsite ===<br />
* [[PT Import Content SubsiteController | SubsiteController]]<br />
* [[PT Import Content SubsiteMapDAO | SubsiteMapDAO]]<br />
* [[PT Import Content SubsiteDAO | SubsiteDAO]]<br />
<br />
=== Pages ===<br />
* [[PT Import Content PageController | PageController]]<br />
* [[PT Import Content PageMapDAO | PageMapDAO]]<br />
* [[PT Import Content PageDAO | PageDAO]]<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
== [[PT Import Content Known Issues and Bugs | Known Issues/Bugs]] ==<br />
<br />
== Tasks ==<br />
* Delete pages needs CSSecurity integration<br />
* Delete Page and Subsite Mapping content needs CSSecurity integration<br />
* Update Page Mapping - set NeedsUpdate = 1 (to reprocess content)<br />
* Fix Links Method for PageController.cfc<br />
<br />
<br />
=== Reports ===<br />
* Pages Mapped<br />
* Subsites Mapped<br />
* Subsites Created<br />
* Subsites Needed to be Created<br />
* Pages Needed to be Updated<br />
<br />
[[Category:Import Content]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Import_Content_Known_Issues_and_Bugs&diff=470PT Import Content Known Issues and Bugs2009-12-24T01:43:35Z<p>Renee.mckechnie: </p>
<hr />
<div>== Known Issues ==<br />
# Running the "Build Subsite Mapping" tool repeatedly creates multiple records in Subsite Mapping Element (should just place one record per OldSubsiteURL)<br />
# Reload Dashboard button is not working<br />
# Subsites with "underscores" are not being mapped/created correctly<br />
# When a tool is done we need a new message that displays that the tool is done<br />
<br />
[[Category:Import Content]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Import_Content_Installation&diff=469PT Import Content Installation2009-12-24T01:42:33Z<p>Renee.mckechnie: </p>
<hr />
<div>Important: Ensure that the [[Installation | ADF is installed]] and functioning correctly<br />
<br />
== Import Custom Elements ==<br />
Import the two custom elements into your site (via the Elements dialog located in your Site Administrator:<br />
<br />
#Subsite Mapping<br />
#Page Mapping<br />
<br />
Note: these elements are located in the /ADF/apps/pt_import_content/exported_objects/ folder<br />
<br />
== Build CCAPI page ==<br />
#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.<br />
# Add the following elements to the page:<br />
## Subsite Mapping<br />
## Page Mapping<br />
# For each Element give it a unique name (e.g. "subsiteMapElement", "pageMapElement")<br />
# Record the pageID for the new page you created<br />
<br />
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.<br />
<br />
Note: Be sure to move into Read Mode after creating this page<br />
<br />
== Create Generic Content Template ==<br />
# 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).<br />
# Place a Textblock Element on the page and give that element a name (e.g. "pageContent")<br />
<br />
Note: Conversely you can use an existing content template - just ensure that the template contains a Formatted Text Block (with or without header) element<br />
<br />
== Configure Site ==<br />
# Add the following line to the init() function of your sites ADF.cfc (ADF.cfc is located in /yoursite/_cs_apps/ directory)<br />
<br />
loadApp("PTImport", "PTImport");<br />
<br />
# Copy the /pt_import_content/ folder from the /ADF/apps/pt_import_content/site_folder/ folder - into your sites /_cs_apps/ folder<br />
# Copy the /config/ folder from the /ADF/apps/pt_import_content/site_folder/ folder - into your sites /_cs_apps/ folder<br />
# 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.<br />
# 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<br />
# Modify the Subsite Spread Sheet Mapping document located in the/yoursite /_cs_apps/pt_import_content/data/ folder<br />
<br />
Note: make sure that the Content Creation API is enabled for your server (see Developers Guide for more info)<br />
<br />
== Build Import Dashboard Page ==<br />
# Create a page and place a Custom Script Element on the page<br />
# Configure the Custom Script Element to point to the file "main_controller.cfm" located in the /ADF/apps/pt_import_content/customcf/ directory<br />
<br />
[[Category:Import Content]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Roles_Component&diff=468PT Profile Roles Component2009-12-24T01:40:59Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
The [[ProfileRoles_Component|ProfileRoles Component]] is required for establishing the logic for the roles at the global and site level.<br />
<br />
The [[ProfileRoles_Component|ProfileRoles Component]] contains a function ''setRolePermission''. This function controls the rules for the profiles on the site. The function contains a switch statement for the role name passed in and then runs through logic to determine the users permission for the role. <br />
<br />
Every time a new role is added, then a new case statement for the role should be added as well.<br />
<br />
If the site roles or role logic differs from the global, then a [[ProfileRoles_Component|ProfileRoles Component]] can be setup for the site. Follow the wiki page for [[Load_ADF_App_Site_Components|Load ADF Application Site Components]] for details on how to override this component at the site.<br />
<br />
[[Category:Profile]]</div>Renee.mckechniehttp://community.paperthin.com/adf-docs/index.php?title=PT_Profile_Gallery_Element&diff=467PT Profile Gallery Element2009-12-24T01:40:33Z<p>Renee.mckechnie: </p>
<hr />
<div>== Overview ==<br />
Profile Select element allows for a contributor to select specific profile records and sort the rendering order. <br />
<br />
== Fields ==<br />
* profileSelect<br />
** Type: General Chooser<br />
** Label: Profile Select<br />
*** Properties<br />
**** Chooser Bean Name: profileGC<br />
<br />
[[Category:Profile]]</div>Renee.mckechnie