Difference between revisions of "PT Social Media Version 2.0 Upgrade"
From ADF Docs
Gcronkright (talk | contribs) (→Overview) |
Gcronkright (talk | contribs) (→Application Code) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Back to [[PT_Social_Media|PT Social Media]] | Back to [[PT_Social_Media|PT Social Media]] | ||
| − | |||
== Overview == | == Overview == | ||
The following guide is upgrading from v1.2 to v2.0. | The following guide is upgrading from v1.2 to v2.0. | ||
| + | |||
| + | == Custom Element Updates == | ||
| + | |||
| + | === PTSocialMedia Configuration === | ||
| + | Add the following new fields to the '''Twitter API''' tab of the ptSocialMedia Configuration element: | ||
| + | #a Tweet URL text field | ||
| + | ##Type: text | ||
| + | ##Field Name: apiTwitterTweetURL | ||
| + | ##Field Label: apiTwitterTweetURL | ||
| + | ##Description: <nowiki>Twitter Tweet page URL. Use {{screenname}} for the screen name variable. And use {{twitterid}} for the twitter data identifier variable.</nowiki> | ||
| + | ##Required: No | ||
| + | ##Properties: | ||
| + | ###Size: 60 | ||
| + | ###Default Value: <nowiki>http://twitter.com/{{screenname}}/status/{{twitterid}}</nowiki> | ||
| + | |||
| + | === App Configuration Updates === | ||
| + | After the new fields have been added to the PTSocialMedia Configuration element: | ||
| + | # Go to the Social Media App Configuration Manager and click the '''"Edit Configuration"''' button. | ||
| + | # When the configuration form opens, add the '''default values''' from the list above as values for the new fields. | ||
| + | # Then click "Submit". | ||
| + | # When the configuration page reloads click the '''"Reset ADF / App Configuration"''' button. | ||
== Application Code == | == Application Code == | ||
# Rename directory "/ADF/apps/pt_socialmedia/" to "/ADF/apps/pt_socialmedia_v1_2/". | # Rename directory "/ADF/apps/pt_socialmedia/" to "/ADF/apps/pt_socialmedia_v1_2/". | ||
# Rename file "/ADF/apps/pt_socialmedia_v1_2/appBeanConfig.cfm" to "/ADF/apps/pt_socialmedia_v1_2/appBeanConfig.cfm.old". | # Rename file "/ADF/apps/pt_socialmedia_v1_2/appBeanConfig.cfm" to "/ADF/apps/pt_socialmedia_v1_2/appBeanConfig.cfm.old". | ||
| − | # Download the PT Social Media v2.0 and | + | # Download the PT Social Media v2.0 and import into the "/ADF/apps/pt_socialmedia/" directory. |
[[Reset ADF|Reset the ADF]] for the server and site. | [[Reset ADF|Reset the ADF]] for the server and site. | ||
Latest revision as of 15:16, 2 May 2014
Back to PT Social Media
Contents
Overview
The following guide is upgrading from v1.2 to v2.0.
Custom Element Updates
PTSocialMedia Configuration
Add the following new fields to the Twitter API tab of the ptSocialMedia Configuration element:
- a Tweet URL text field
- Type: text
- Field Name: apiTwitterTweetURL
- Field Label: apiTwitterTweetURL
- Description: Twitter Tweet page URL. Use {{screenname}} for the screen name variable. And use {{twitterid}} for the twitter data identifier variable.
- Required: No
- Properties:
- Size: 60
- Default Value: http://twitter.com/{{screenname}}/status/{{twitterid}}
App Configuration Updates
After the new fields have been added to the PTSocialMedia Configuration element:
- Go to the Social Media App Configuration Manager and click the "Edit Configuration" button.
- When the configuration form opens, add the default values from the list above as values for the new fields.
- Then click "Submit".
- When the configuration page reloads click the "Reset ADF / App Configuration" button.
Application Code
- Rename directory "/ADF/apps/pt_socialmedia/" to "/ADF/apps/pt_socialmedia_v1_2/".
- Rename file "/ADF/apps/pt_socialmedia_v1_2/appBeanConfig.cfm" to "/ADF/apps/pt_socialmedia_v1_2/appBeanConfig.cfm.old".
- Download the PT Social Media v2.0 and import 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.
