Difference between revisions of "PT Social Media Version 1.0 Install"

From ADF Docs
Jump to: navigation, search
Line 26: Line 26:
  
 
Note: the classes and styles defined for the Social Media app are targeted tightly for the layout generated by the Social Media application and should not interfere with your site styles. However, it is a good idea to give these styles sheets higher precedence in your style definitions.
 
Note: the classes and styles defined for the Social Media app are targeted tightly for the layout generated by the Social Media application and should not interfere with your site styles. However, it is a good idea to give these styles sheets higher precedence in your style definitions.
 +
 +
== Import Custom Elements ==
 +
The Social Media App has several Custom Components defined within CommonSpot. These components are available in the Social Media's "exported-objects" folder located at the root of the Social Media application directory (e.g. /ADF/apps/pt_social_media/exported-objects/)
 +
 +
To import these objects, you will need to be an administrator for your site.
 +
 +
=== Import ===
 +
 +
Create a "PT Social Media Elements" category and import all portions of each component in the order listed.
 +
 +
'''Import Custom Elements:'''
 +
 +
#[[SocialMedia Selector]] (SocialMedia-Selector-Custom-Element.zip)
 +
#[[Facebook Pages]] (Facebook-Pages-Custom-Element.zip)
 +
#[[Twitter Accounts Keywords]] (Twitter-Accounts-Keywords-Selector-Custom-Element.zip)
 +
#[[WordPress Blogs]] (WordPress-Blogs-Custom-Element.zip)
 +
#[[YouTube Channels]] (YouTube-Channels-Custom-Element.zip)
 +
#[[ptSocialMedia Configuration]] (ptSocialMedia-Configuration-Custom-Element.zip)
 +
 +
== Verify Imports ==
 +
 +
The imported components' render handlers and custom field types must be verified.  During the import process, the render handler and custom field types paths may have been changed to reflect the current site's path. 
 +
 +
Review and update these paths to reference the ADF path.  In most cases, this will just require to be unlocked and a change in the path from the site name to 'ADF'.  Check the paths for the custom field types that were imported with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".
 +
 +
If the custom elements that are imported contain custom field types that are already in the site, the naming convention for the custom field type will be unique.  To resolve this, unlock the field types and elements, and reassign the element field type to the pre-existing field type. 
 +
 +
Example: The SocialMedia Selector custom element contains two uses of the General Chooser field type, if the General Chooser field type is already installed on the site then the import process will attempt to import another General Chooser but with a new name such as "General Chooser_import_1250003208472." To resolve this issue, open the custom element and assign the field type (General Chooser_import_1250003208472) to the field type with the simple name General Chooser. After reassigning the field type, delete the new imported field from the list of custom field types.

Revision as of 15:49, 1 May 2012

Back to Social Media

Download

Download the Social Media Application from the Community Site Project or from the SVN Repository.

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

Site Configuration

The Social Media Application is built within the ADF. The ADF 1.5 or greater must be installed in the site to run the Social Media Application, follow the ADF Installation instructions.

Steps

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

Styles

There are several out of the box style options for the Social Media application. Most of the styles are defined in the following style sheets located in the /style directory within the ADF Social Media App directory:

  • socialmedia.css

You have two options: you can either load them into your Base Plus One (recommended) or your can load them into the Social Media Template you create.

Note: the classes and styles defined for the Social Media app are targeted tightly for the layout generated by the Social Media application and should not interfere with your site styles. However, it is a good idea to give these styles sheets higher precedence in your style definitions.

Import Custom Elements

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

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

Import

Create a "PT Social Media Elements" category and import all portions of each component in the order listed.

Import Custom Elements:

  1. SocialMedia Selector (SocialMedia-Selector-Custom-Element.zip)
  2. Facebook Pages (Facebook-Pages-Custom-Element.zip)
  3. Twitter Accounts Keywords (Twitter-Accounts-Keywords-Selector-Custom-Element.zip)
  4. WordPress Blogs (WordPress-Blogs-Custom-Element.zip)
  5. YouTube Channels (YouTube-Channels-Custom-Element.zip)
  6. ptSocialMedia Configuration (ptSocialMedia-Configuration-Custom-Element.zip)

Verify Imports

The imported components' render handlers and custom field types must be verified. During the import process, the render handler and custom field types paths may have been changed to reflect the current site's path.

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

If the custom elements that are imported contain custom field types that are already in the site, the naming convention for the custom field type will be unique. To resolve this, unlock the field types and elements, and reassign the element field type to the pre-existing field type.

Example: The SocialMedia Selector custom element contains two uses of the General Chooser field type, if the General Chooser field type is already installed on the site then the import process will attempt to import another General Chooser but with a new name such as "General Chooser_import_1250003208472." To resolve this issue, open the custom element and assign the field type (General Chooser_import_1250003208472) to the field type with the simple name General Chooser. After reassigning the field type, delete the new imported field from the list of custom field types.