Difference between revisions of "PT Social Media Version 2.2 Upgrade"
From ADF Docs
Gcronkright (talk | contribs) (→ptSocialMedia Configuration) |
Gcronkright (talk | contribs) (→ptSocialMedia Configuration) |
||
Line 8: | Line 8: | ||
=== ptSocialMedia Configuration === | === ptSocialMedia Configuration === | ||
Due to misnamed twitter API Consumer fields in the ptSocialMedia Configuration custom element you will need to run the Social Media App Updater Custom Script. | Due to misnamed twitter API Consumer fields in the ptSocialMedia Configuration custom element you will need to run the Social Media App Updater Custom Script. | ||
− | + | IMPORTANT: It is a good idea to backup your CommonSpot Site Database before running the '''SocialMediaAppUpdate''' script | |
− | IMPORTANT: It is a good idea to backup your CommonSpot Site Database before running | ||
Use these steps to update the 'Customer Key' and 'Customer Secret' fields to be updated to the correct '''Consumer Key''' and '''Consumer Secret''' fields names and labels: | Use these steps to update the 'Customer Key' and 'Customer Secret' fields to be updated to the correct '''Consumer Key''' and '''Consumer Secret''' fields names and labels: | ||
# Copy the following updater file to your site and place it in your 'customcf' directiry: | # Copy the following updater file to your site and place it in your 'customcf' directiry: |
Revision as of 21:09, 21 October 2014
Back to PT Social Media
Contents
Overview
The following guide is upgrading from v2.1 to v2.2.
Custom Element Updates
ptSocialMedia Configuration
Due to misnamed twitter API Consumer fields in the ptSocialMedia Configuration custom element you will need to run the Social Media App Updater Custom Script.
IMPORTANT: It is a good idea to backup your CommonSpot Site Database before running the SocialMediaAppUpdate script
Use these steps to update the 'Customer Key' and 'Customer Secret' fields to be updated to the correct Consumer Key and Consumer Secret fields names and labels:
- Copy the following updater file to your site and place it in your 'customcf' directiry:
- '/ADF/apps/pt_social_media/site-files/customcf/SocialMediaAppUpdate.cfm'
- View the PT Social Media App Update menu page by going to the URL:
- The following updater script with be displayed with [PREVIEW] and [RUN] options
- schema-update-for-2.2
- First, click on the [PREVIEW] option
- If the message reads "No Fields need to be updated at this time!" you are done!
- If the message displays the "Old Field" and the "New Field" update info, go back to the updater menu.
- Once back at the updater menu, click the [RUN] option.
- When the script has finished running it should display the messages:
- The field "apiTwitterConsumerKey" in the ptSocialMedia Configuration element was updated!
- The field "apiTwitterCustomerSecret" in the ptSocialMedia Configuration element was updated!
- Now go to the CommonSpot Site Admin.
- Go to the "Elements" menu item under "Elements & Forms".
- From the list of elements in the "Manage Elements" dialog find the "ptSocialMedia Configuration" custom element.
- Select the "Field Definitions" menu option for the "ptSocialMedia Configuration" element under the pencil icon.
- When the "Custom Element Field Definitions" dialog click on the pencil icon to edit the updated field
- Without making any other changes hit the "save" option to save the field.
- The field should then reflect the changes.
- Close the "Manage Elements" windows.
Your Fields should now be updated!
Application Code
- Rename directory "/ADF/apps/pt_socialmedia/" to "/ADF/apps/pt_socialmedia_v2_1/".
- Rename file "/ADF/apps/pt_socialmedia_v2_1/appBeanConfig.cfm" to "/ADF/apps/pt_socialmedia_v2_1/appBeanConfig.cfm.old".
- Download the PT Social Media v2.2 and copy the extracted files into the "/ADF/apps/pt_socialmedia/" directory.
Reset the ADF for the server and site.
Site Customizations
During the application implementation customizations may have been created. Check under the "/_cs_apps/pt_socialmedia/" directory under you site to see if any customizations exists. If you do have site customizations, you'll need to update these accordingly.