http://community.paperthin.com/adf-docs/api.php?action=feedcontributions&user=Mcarroll&feedformat=atomADF Docs - User contributions [en]2024-03-29T07:27:21ZUser contributionsMediaWiki 1.29.0http://community.paperthin.com/adf-docs/index.php?title=PT_Blog_v3.1_Change_Log&diff=6550PT Blog v3.1 Change Log2013-05-21T17:31:57Z<p>Mcarroll: Created page with "r124 | mcarroll | 2013-05-21 13:23:15 EDT Changed paths: M /branches/3.1/components/App.cfc M /branches/3.1/components/commentsDAO.cfc Function: commentsDAO.getCommentsByCo..."</p>
<hr />
<div>r124 | mcarroll | 2013-05-21 13:23:15 EDT<br />
Changed paths:<br />
M /branches/3.1/components/App.cfc<br />
M /branches/3.1/components/commentsDAO.cfc<br />
<br />
Function: commentsDAO.getCommentsByContentID<br />
Description: Added param to return only the approved comments.<br />
----------------------------------------------------------------------------<br />
r123 | mcarroll | 2013-05-21 12:04:34 EDT<br />
Changed paths:<br />
M /branches/3.1/renderhandlers/blog_post_display.cfm<br />
<br />
Updated to add boolean to the "getCommentsByContentID" function.<br />
----------------------------------------------------------------------------<br />
r122 | mcarroll | 2013-04-30 14:10:53 EDT<br />
Changed paths:<br />
M /branches/3.1/components/App.cfc<br />
M /branches/3.1/appBeanConfig.cfm<br />
M /branches/3.1/components/commentsService.cfc<br />
<br />
Function: getDashboardData<br />
Description: Added "Delete Comment" link into the comment display.<br />
<br />
Updated the App Bean Config to include the ui_1_0 library.<br />
----------------------------------------------------------------------------<br />
r121 | mcarroll | 2013-04-29 16:00:55 EDT<br />
Changed paths:<br />
M /branches/3.1/appBeanConfig.cfm<br />
M /branches/3.1/components/App.cfc<br />
<br />
Added "apiKeywords_1_0" into the App Bean Config.<br />
----------------------------------------------------------------------------<br />
r120 | mcarroll | 2013-04-29 16:00:28 EDT<br />
Changed paths:<br />
M /branches/3.1/components/App.cfc<br />
M /branches/3.1/components/postDAO.cfc<br />
<br />
Function: createPost<br />
Description: Commented out the unique page name and title function calls. Added call to create the keywords for the page.<br />
<br />
Function: saveInfoPost, renamePost<br />
Description: Created Functions.<br />
----------------------------------------------------------------------------<br />
r119 | mcarroll | 2013-04-29 15:58:17 EDT<br />
Changed paths:<br />
M /branches/3.1/components/postService.cfc<br />
M /branches/3.1/components/App.cfc<br />
<br />
Function: syncPost<br />
Description: Rebuilt the sync process to check if any existing post page exists and update the page metadata and/or rename the page. <br />
<br />
Function: createPostPage<br />
Description: Updated to use the "buildPageMetadata" function.<br />
<br />
Function: saveInfoPostPage, renamePostPage, buildPageMetadata<br />
Description: Created functions.<br />
----------------------------------------------------------------------------<br />
r118 | mcarroll | 2013-04-26 15:05:32 EDT<br />
Changed paths:<br />
M /branches/3.1/renderhandlers/blog_posts_rss_feed.cfm<br />
M /branches/3.1/components/postDAO.cfc<br />
M /branches/3.1/components/postService.cfc<br />
M /branches/3.1/components/commentsService.cfc<br />
M /branches/3.1/components/blogService.cfc<br />
M /branches/3.1/components/App.cfc<br />
M /branches/3.1/datasheet-modules/blog_edit_delete.cfm<br />
<br />
Replaced any reference to "application.ADF" with "application.ptBlog2".<br />
----------------------------------------------------------------------------<br />
r117 | mcarroll | 2013-04-26 15:01:25 EDT<br />
Changed paths:<br />
M /branches/3.1/appBeanConfig.cfm<br />
M /branches/3.1/components/App.cfc<br />
<br />
Rolled back CEData to v1.1 for issue with the "formid" field in the Comments2 element.<br />
----------------------------------------------------------------------------<br />
r116 | mcarroll | 2013-04-26 15:00:48 EDT<br />
Changed paths:<br />
M /branches/3.1/renderhandlers/blog_post_display.cfm<br />
M /branches/3.1/renderhandlers/blog_post_short.cfm<br />
<br />
Added check to validate that the metadata form field exists.<br />
----------------------------------------------------------------------------<br />
r115 | mcarroll | 2013-03-15 14:05:00 EDT<br />
Changed paths:<br />
A /branches/3.1<br />
<br />
Created development branch v3.1.<br />
----------------------------------------------------------------------------</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Release_Notes_v3.1&diff=6549PT Blog Release Notes v3.12013-05-21T17:31:45Z<p>Mcarroll: Created page with "We are proud to release v3 to the Community. Version 3.1 is compatible with the ADF v1.6. If installing the PT Blog app for the first time, please follow the v3.1 Install Gu..."</p>
<hr />
<div>We are proud to release v3 to the Community.<br />
<br />
Version 3.1 is compatible with the ADF v1.6.<br />
<br />
If installing the PT Blog app for the first time, please follow the v3.1 Install Guide.<br />
<br />
If upgrading from a version 3 or earlier, please complete the v2.0 - v3.0 Upgrade Guides in order.<br />
<br />
=== Enhancements ===<br />
* Added "apiKeywords_1_0" into the App Bean Config.<br />
* Updated the App Bean Config to include the ui_1_0 library.<br />
* commentsDAO.getCommentsByContentID - Added param to return only the approved comments.<br />
<br />
=== Bug Fixes ===<br />
* Rolled back CEData to v1.1 for issue with the "formid" field in the Comments2 element.<br />
* Replaced any reference to "application.ADF" with "application.ptBlog2".<br />
* Updates to the render handler files to check to validate that the metadata form field exists.<br />
<br />
=== SVN Change Log ===<br />
For detailed SVN repository updates for the v3, please see the [[PT_Blog_v3.1_Change_Log|PT Blog v3.1 Change Log]].</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Install_v3.1&diff=6548PT Blog Install v3.12013-05-21T17:28:38Z<p>Mcarroll: Created page with "Please follow the PT Blog v2.2 Install Guide."</p>
<hr />
<div>Please follow the [[PT_Blog_Version_2.2_Install|PT Blog v2.2 Install Guide]].</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Upgrade_v3.1&diff=6547PT Blog Upgrade v3.12013-05-21T17:28:12Z<p>Mcarroll: </p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the PT Blog v3.1 application. If upgrading from a lower version than v3, please follow the [[PT_Blog_Version_2.2_Install|Version 2.2 Install Guide]] to validate your installation.<br />
<br />
== Application Code ==<br />
# Renamed directory "/ADF/apps/pt_blog" to "/ADF/apps/pt_blog_v3_0".<br />
# Renamed file "/ADF/apps/pt_blog_v3_0/appBeanConfig.cfm" to "/ADF/apps/pt_blog_v3_0/appBeanConfig.cfm.old".<br />
# Downloaded the PT Blog v3.1 and exported into the "/ADF/apps/pt_blog/" directory.<br />
<br />
== Reset the ADF ==<br />
[[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
== Site Level Customizations Review ==<br />
This is only for reviewing the site level customizations in the "/_cs_apps/pt_blog/" directory, not in the ADF directory.<br />
<br />
# Analyze the updated app code compared to the app customization code on your server.<br />
## Identify any customizations that you have made to the application code to make sure these are updated with any functionality.<br />
## Again, Beyond Compare is a good tool to compare the new and current file to identify the exact lines of code that have been changed. <br />
## This is important for components that have customized functions to the site level "/_cs_apps/". The best practice is to identify the function that have been customized and compare with the new app function to identify any updates. A good help is to check the function comment header to see if any updates have been made.<br />
# Once completed, Reset the ADF.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Upgrade_v3.1&diff=6546PT Blog Upgrade v3.12013-05-21T17:27:52Z<p>Mcarroll: /* Application Code */</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the PT Blog v3.1 application. If upgrading from a lower version than v3, please follow the [[PT_Blog_Version_2.2_Install|Version 2.2 Install Guide]] to validate your installation.<br />
<br />
== Application Code ==<br />
# Renamed directory "/ADF/apps/pt_blog" to "/ADF/apps/pt_blog_v3_0".<br />
# Renamed file "/ADF/apps/pt_blog_v3_0/appBeanConfig.cfm" to "/ADF/apps/pt_blog_v3_0/appBeanConfig.cfm.old".<br />
# Downloaded the PT Blog v3.1 and exported into the "/ADF/apps/pt_blog/" directory.<br />
<br />
== Reset the ADF ==<br />
[[Reset ADF|Reset the ADF]] for the server and site.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Blogs&diff=6545Blogs2013-05-21T17:27:18Z<p>Mcarroll: /* Installation Guides */</p>
<hr />
<div>=Overview=<br />
PT Blogs ADF application provides a simple and easy blog management solution within CommonSpot.<br />
<br />
Users are able to add/modify/delete and reuse blog content easily. Numerous features have been developed into the latest version of this application to provide a flexibility solution for all users.<br />
<br />
== Installation Guides ==<br />
Current Release v3.1:<br />
* [[PT_Blog_Release_Notes_v3.1|Release Notes]]<br />
* [[PT_Blog_Install_v3.1|Install Guide]]<br />
* [[PT_Blog_Upgrade_v3.1|Upgrade Guide]]<br />
<br />
Previous Versions:<br />
* v3.0:<br />
** [[PT_Blog_Release_Notes_v3|Release Notes]]<br />
** [[PT_Blog_Install_v3|Install Guide]]<br />
** [[PT_Blog_Upgrade_v3|Upgrade Guide]]<br />
*v2.3:<br />
** [[PT_Blog_Release_Notes_v2.3|Release Notes]]<br />
** [[PT_Blog_Install_v2.3|Install Guide]]<br />
** [[PT_Blog_Upgrade_v2.3|Upgrade Guide]]<br />
* v2.2:<br />
** [[PT_Blog_Version_2.2_Release_Notes|Release Notes]]<br />
** [[PT_Blog_Version_2.2_Install|Install Guide]]<br />
** [[PT_Blog_Version_2.2_Upgrade|Upgrade Guide]]<br />
* v2.1:<br />
** [[PT_Blog_Version_2.1_Install|Install Guide]]<br />
** [[PT_Blog_Version_2.1_Upgrade|Upgrade Guide]]<br />
* v2.0<br />
** [[PT_Blog_Version_2.0_Install|Install Guide]]<br />
** [[PT_Blog_Version_2.0_Upgrade|Upgrade Guide]]<br />
<br />
== Getting Started ==<br />
* [[PT_Blog_Getting_Started_Guide|Getting Started Guide]]<br />
<br />
== Features ==<br />
v2 Features<br />
*[[PT_Blogs_Feature_Tags|PT Tags Integration]]<br />
*[[PT_Blogs_Feature_Landing_Page|Auto Create Blog Landing Page]]<br />
*[[PT_Blogs_Feature_Date_Subsite|Enable/Disable the Date Subsite Mask]]<br />
*[[PT_Blogs_Feature_RSS_Feed|Blog RSS Feeds]]<br />
<br />
<br />
[[Category:Project]]<br />
[[Category:Blogs]]</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Blogs&diff=6544Blogs2013-05-21T17:27:06Z<p>Mcarroll: /* Installation Guides */</p>
<hr />
<div>=Overview=<br />
PT Blogs ADF application provides a simple and easy blog management solution within CommonSpot.<br />
<br />
Users are able to add/modify/delete and reuse blog content easily. Numerous features have been developed into the latest version of this application to provide a flexibility solution for all users.<br />
<br />
== Installation Guides ==<br />
Current Release v3.1:<br />
* [[PT_Blog_Release_Notes_v3.1|Release Notes]]<br />
* [[PT_Blog_Install_v3.1|Install Guide]]<br />
* [[PT_Blog_Upgrade_v3.1|Upgrade Guide]]<br />
<br />
Previous Versions:<br />
* v3.0:<br />
* [[PT_Blog_Release_Notes_v3|Release Notes]]<br />
* [[PT_Blog_Install_v3|Install Guide]]<br />
* [[PT_Blog_Upgrade_v3|Upgrade Guide]]<br />
*v2.3:<br />
** [[PT_Blog_Release_Notes_v2.3|Release Notes]]<br />
** [[PT_Blog_Install_v2.3|Install Guide]]<br />
** [[PT_Blog_Upgrade_v2.3|Upgrade Guide]]<br />
* v2.2:<br />
** [[PT_Blog_Version_2.2_Release_Notes|Release Notes]]<br />
** [[PT_Blog_Version_2.2_Install|Install Guide]]<br />
** [[PT_Blog_Version_2.2_Upgrade|Upgrade Guide]]<br />
* v2.1:<br />
** [[PT_Blog_Version_2.1_Install|Install Guide]]<br />
** [[PT_Blog_Version_2.1_Upgrade|Upgrade Guide]]<br />
* v2.0<br />
** [[PT_Blog_Version_2.0_Install|Install Guide]]<br />
** [[PT_Blog_Version_2.0_Upgrade|Upgrade Guide]]<br />
<br />
== Getting Started ==<br />
* [[PT_Blog_Getting_Started_Guide|Getting Started Guide]]<br />
<br />
== Features ==<br />
v2 Features<br />
*[[PT_Blogs_Feature_Tags|PT Tags Integration]]<br />
*[[PT_Blogs_Feature_Landing_Page|Auto Create Blog Landing Page]]<br />
*[[PT_Blogs_Feature_Date_Subsite|Enable/Disable the Date Subsite Mask]]<br />
*[[PT_Blogs_Feature_RSS_Feed|Blog RSS Feeds]]<br />
<br />
<br />
[[Category:Project]]<br />
[[Category:Blogs]]</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6.1&diff=6543Upgrade Guide v1.6.12013-05-21T16:55:36Z<p>Mcarroll: Created page with "== Current Version == Follow the guide below if you are upgrading to ADF v1.6.1. Before upgrading, please review the [http://community.paperthin.com/projects/ADF/docs/Release..."</p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.1.<br />
<br />
Before upgrading, please review the [http://community.paperthin.com/projects/ADF/docs/Release-Notes-v1-6-1.cfm v1.6.1 Release Notes]<br />
<br />
If you are upgrading from ADF v1.6 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.6|1.6 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6.1 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "/ADF/" directory to "/ADF-1.6.0/".<br />
# Create a new "/ADF/" directory. Setup any neccessary security or permissions for the new "/ADF/" directory.<br />
# Export the download ADF zip folder into the "/ADF/" directory.<br />
# Copy the contents of the "/ADF_1.6.0/apps/" directory into the "/ADF/apps/" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6.1 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.1.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6.1<br />
# Upgrade was successful and you are running the ADF v1.6.1.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=MediaWiki:Sidebar&diff=6535MediaWiki:Sidebar2013-05-16T17:41:18Z<p>Mcarroll: </p>
<hr />
<div>*Community<br />
**http://community.paperthin.com|Home<br />
**http://community.paperthin.com/projects/|Projects<br />
**http://community.paperthin.com/articles/|Articles<br />
**http://community.paperthin.com/profiles/|Profiles<br />
**http://community.paperthin.com/forums/|Forums<br />
**http://community.paperthin.com/blog/|Blog<br />
**http://community.paperthin.com/projects/ADF|ADF<br />
<br />
<br />
*SEARCH<br />
Browse | Advanced<br />
<br />
<br />
*About the Framework<br />
**Overview|Overview<br />
**Architecture|Architecture<br />
**Security|Security<br />
**Glossary|Glossary<br />
<br />
*Using the ADF<br />
**Installation|Installation<br />
**Getting Started|Getting Started<br />
**Library|Library (API)<br />
**Category:How-to_Guide|How-to Guides<br />
**Troubleshooting|Troubleshooting<br />
<br />
*Projects<br />
**Blogs|Blogs<br />
**CCAPI_Library_Component|CCAPI<br />
**Forums|Forums<br />
**PT Photo_Gallery|Photo Gallery<br />
**Profiles|Profiles<br />
**View_All|View All Projects<br />
<br />
*About the Wiki<br />
**About|About<br />
**Contributing|Contributing<br />
**Templates|Templates<br />
**Special:Categories|Categories<br />
**Special:UserLogin|Login/Create an Account<br />
<br />
<br />
<!--* navigation --><br />
<!--** mainpage|mainpage-description --><br />
<!--** portal-url|portal--><br />
<!--** currentevents-url|currentevents--><br />
<!--** recentchanges-url|recentchanges--><br />
<!--** randompage-url|randompage--><br />
<!--** helppage|help--></div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=MediaWiki:Sidebar&diff=6534MediaWiki:Sidebar2013-05-16T17:40:24Z<p>Mcarroll: </p>
<hr />
<div>*Community<br />
**http://community.paperthin.com|Home<br />
**http://community.paperthin.com/projects/|Projects<br />
**http://community.paperthin.com/articles/|Articles<br />
**http://community.paperthin.com/profiles/|Profiles<br />
**http://community.paperthin.com/forums/|Forums<br />
**http://community.paperthin.com/blog/|Blog<br />
**http://community.paperthin.com/projects/ADF|ADF<br />
<br />
<br />
*Main_Page|ADF Docs Home<br />
<br />
*SEARCH<br />
Browse | Advanced<br />
<br />
<br />
*About the Framework<br />
**Overview|Overview<br />
**Architecture|Architecture<br />
**Security|Security<br />
**Glossary|Glossary<br />
<br />
*Using the ADF<br />
**Installation|Installation<br />
**Getting Started|Getting Started<br />
**Library|Library (API)<br />
**Category:How-to_Guide|How-to Guides<br />
**Troubleshooting|Troubleshooting<br />
<br />
*Projects<br />
**Blogs|Blogs<br />
**CCAPI_Library_Component|CCAPI<br />
**Forums|Forums<br />
**PT Photo_Gallery|Photo Gallery<br />
**Profiles|Profiles<br />
**View_All|View All Projects<br />
<br />
*About the Wiki<br />
**About|About<br />
**Contributing|Contributing<br />
**Templates|Templates<br />
**Special:Categories|Categories<br />
**Special:UserLogin|Login/Create an Account<br />
<br />
<br />
<!--* navigation --><br />
<!--** mainpage|mainpage-description --><br />
<!--** portal-url|portal--><br />
<!--** currentevents-url|currentevents--><br />
<!--** recentchanges-url|recentchanges--><br />
<!--** randompage-url|randompage--><br />
<!--** helppage|help--></div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=MediaWiki:Sidebar&diff=6533MediaWiki:Sidebar2013-05-16T17:39:53Z<p>Mcarroll: </p>
<hr />
<div>*Community<br />
**http://community.paperthin.com|Home<br />
**[http://community.paperthin.com/projects/ Projects]<br />
**[http://community.paperthin.com/articles/ Articles]<br />
**[http://community.paperthin.com/profiles/ Profiles]<br />
**[http://community.paperthin.com/forums/ Forums]<br />
**[http://community.paperthin.com/blog/ Blog]<br />
**[http://community.paperthin.com/projects/ADF ADF]<br />
<br />
<br />
*Main_Page|ADF Docs Home<br />
<br />
*SEARCH<br />
Browse | Advanced<br />
<br />
<br />
*About the Framework<br />
**Overview|Overview<br />
**Architecture|Architecture<br />
**Security|Security<br />
**Glossary|Glossary<br />
<br />
*Using the ADF<br />
**Installation|Installation<br />
**Getting Started|Getting Started<br />
**Library|Library (API)<br />
**Category:How-to_Guide|How-to Guides<br />
**Troubleshooting|Troubleshooting<br />
<br />
*Projects<br />
**Blogs|Blogs<br />
**CCAPI_Library_Component|CCAPI<br />
**Forums|Forums<br />
**PT Photo_Gallery|Photo Gallery<br />
**Profiles|Profiles<br />
**View_All|View All Projects<br />
<br />
*About the Wiki<br />
**About|About<br />
**Contributing|Contributing<br />
**Templates|Templates<br />
**Special:Categories|Categories<br />
**Special:UserLogin|Login/Create an Account<br />
<br />
<br />
<!--* navigation --><br />
<!--** mainpage|mainpage-description --><br />
<!--** portal-url|portal--><br />
<!--** currentevents-url|currentevents--><br />
<!--** recentchanges-url|recentchanges--><br />
<!--** randompage-url|randompage--><br />
<!--** helppage|help--></div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=MediaWiki:Sidebar&diff=6532MediaWiki:Sidebar2013-05-16T17:36:13Z<p>Mcarroll: </p>
<hr />
<div>*Community<br />
**[http://community.paperthin.com Home]<br />
**[http://community.paperthin.com/projects/ Projects]<br />
**[http://community.paperthin.com/articles/ Articles]<br />
**[http://community.paperthin.com/profiles/ Profiles]<br />
**[http://community.paperthin.com/forums/ Forums]<br />
**[http://community.paperthin.com/blog/ Blog]<br />
**[http://community.paperthin.com/projects/ADF ADF]<br />
<br />
<br />
*Main_Page|ADF Docs Home<br />
<br />
*SEARCH<br />
Browse | Advanced<br />
<br />
<br />
*About the Framework<br />
**Overview|Overview<br />
**Architecture|Architecture<br />
**Security|Security<br />
**Glossary|Glossary<br />
<br />
*Using the ADF<br />
**Installation|Installation<br />
**Getting Started|Getting Started<br />
**Library|Library (API)<br />
**Category:How-to_Guide|How-to Guides<br />
**Troubleshooting|Troubleshooting<br />
<br />
*Projects<br />
**Blogs|Blogs<br />
**CCAPI_Library_Component|CCAPI<br />
**Forums|Forums<br />
**PT Photo_Gallery|Photo Gallery<br />
**Profiles|Profiles<br />
**View_All|View All Projects<br />
<br />
*About the Wiki<br />
**About|About<br />
**Contributing|Contributing<br />
**Templates|Templates<br />
**Special:Categories|Categories<br />
**Special:UserLogin|Login/Create an Account<br />
<br />
<br />
<!--* navigation --><br />
<!--** mainpage|mainpage-description --><br />
<!--** portal-url|portal--><br />
<!--** currentevents-url|currentevents--><br />
<!--** recentchanges-url|recentchanges--><br />
<!--** randompage-url|randompage--><br />
<!--** helppage|help--></div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Upgrade_v3.1&diff=6520PT Blog Upgrade v3.12013-05-01T17:54:10Z<p>Mcarroll: Created page with '== Overview == This guide is to upgrade the PT Blog v3.1 application. If upgrading from a lower version than v3, please follow the [[PT_Blog_Version_2.2_Install|Version 2.2 Inst…'</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the PT Blog v3.1 application. If upgrading from a lower version than v3, please follow the [[PT_Blog_Version_2.2_Install|Version 2.2 Install Guide]] to validate your installation.<br />
<br />
== Application Code ==<br />
# Renamed directory "/ADF/apps/pt_blog" to "/ADF/apps/pt_blog_v3_0".<br />
# Renamed file "/ADF/apps/pt_blog_v3_0/appBeanConfig.cfm" to "/ADF/apps/pt_blog_v3_0/appBeanConfig.cfm.old".<br />
# Downloaded the PT Blog v3 and exported into the "/ADF/apps/pt_blog/" directory.<br />
<br />
<br />
<br />
<br />
== Reset the ADF ==<br />
[[Reset ADF|Reset the ADF]] for the server and site.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Upgrade_v3&diff=6519PT Blog Upgrade v32013-04-26T18:05:16Z<p>Mcarroll: /* Landing Page Template */</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the PT Blog v2.3 application. If upgrading from a lower version than v2.3, please follow the [[PT_Blog_Version_2.2_Install|Version 2.2 Install Guide]] to validate your installation.<br />
<br />
== Application Code ==<br />
# Renamed directory "/ADF/apps/pt_blog" to "/ADF/apps/pt_blog_v2_3".<br />
# Renamed file "/ADF/apps/pt_blog_v2_3/appBeanConfig.cfm" to "/ADF/apps/pt_blog_v2_3/appBeanConfig.cfm.old".<br />
# Downloaded the PT Blog v3 and exported into the "/ADF/apps/pt_blog/" directory.<br />
<br />
== Custom Elements ==<br />
<br />
=== Blog2 ===<br />
Add the following new fields:<br />
# Name: notificationFrom<br />
## Tab: Notifications<br />
### Move this field to the first field in the Notifications tab.<br />
## Label: From Email Address <br />
## Type: Email<br />
## Description: Email address to be used as the FROM email for the notification emails.<br />
## Properties:<br />
### Size: 40<br />
<br />
== Templates ==<br />
<br />
=== Blog Post Template ===<br />
Navigate to the Blog Post template that was created from the installation. Rename the page to add "template" into the title for easy recognition. <br />
<br />
On the page, open the dialog "Actions > Rename Page..". Update the form fields with the following:<br />
# Name: template-blog-post-template<br />
# Title: Blog Post Template<br />
# Title Bar Caption: Blog Post Template<br />
<br />
=== Landing Page Template ===<br />
Navigate to the Landing Page template that was created from the installation. Rename the page to add "template" into the title for easy recognition. <br />
<br />
On the page, open the dialog "Actions > Rename Page..". Update the form fields with the following:<br />
# Name: template-blog-landing-template<br />
# Title: Blog Landing Template<br />
# Title Bar Caption: Blog Landing Template<br />
<br />
== Blog Manager ==<br />
<br />
Navigate to the Blog Manager page. Edit each blog record to assign a value into the "notificationFrom" field. If no value is assigned, then the CommonSpot site administrator email will be used as the from address for notification emails.<br />
<br />
After modifying the template names above, please edit and review the settings for the for the "Edit App Configuration" form fields for the template select are correct. Additionally, edit and review the blog records to make sure the "Blog Post Template" select field has the correct template selected.<br />
<br />
== Site Level Customizations Review ==<br />
This is only for reviewing the site level customizations in the "/_cs_apps/pt_blog/" directory, not in the ADF directory.<br />
<br />
# Analyze the updated app code compared to the app customization code on your server.<br />
## Identify any customizations that you have made to the application code to make sure these are updated with any functionality.<br />
## Again, Beyond Compare is a good tool to compare the new and current file to identify the exact lines of code that have been changed. <br />
## This is important for components that have customized functions to the site level "/_cs_apps/". The best practice is to identify the function that have been customized and compare with the new app function to identify any updates. A good help is to check the function comment header to see if any updates have been made.<br />
# Once completed, Reset the ADF.<br />
<br />
== Reset the ADF ==<br />
[[Reset ADF|Reset the ADF]] for the server and site.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Upgrade_v3&diff=6518PT Blog Upgrade v32013-04-26T18:03:15Z<p>Mcarroll: /* Landing Page Template */</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the PT Blog v2.3 application. If upgrading from a lower version than v2.3, please follow the [[PT_Blog_Version_2.2_Install|Version 2.2 Install Guide]] to validate your installation.<br />
<br />
== Application Code ==<br />
# Renamed directory "/ADF/apps/pt_blog" to "/ADF/apps/pt_blog_v2_3".<br />
# Renamed file "/ADF/apps/pt_blog_v2_3/appBeanConfig.cfm" to "/ADF/apps/pt_blog_v2_3/appBeanConfig.cfm.old".<br />
# Downloaded the PT Blog v3 and exported into the "/ADF/apps/pt_blog/" directory.<br />
<br />
== Custom Elements ==<br />
<br />
=== Blog2 ===<br />
Add the following new fields:<br />
# Name: notificationFrom<br />
## Tab: Notifications<br />
### Move this field to the first field in the Notifications tab.<br />
## Label: From Email Address <br />
## Type: Email<br />
## Description: Email address to be used as the FROM email for the notification emails.<br />
## Properties:<br />
### Size: 40<br />
<br />
== Templates ==<br />
<br />
=== Blog Post Template ===<br />
Navigate to the Blog Post template that was created from the installation. Rename the page to add "template" into the title for easy recognition. <br />
<br />
On the page, open the dialog "Actions > Rename Page..". Update the form fields with the following:<br />
# Name: template-blog-post-template<br />
# Title: Blog Post Template<br />
# Title Bar Caption: Blog Post Template<br />
<br />
=== Landing Page Template ===<br />
Navigate to the Landing Page template that was created from the installation. Rename the page to add "template" into the title for easy recognition. <br />
<br />
On the page, open the dialog "Actions > Rename Page..". Update the form fields with the following:<br />
# Name: template-blog-landing-Template<br />
# Title: Blog Landing Template<br />
# Title Bar Caption: Blog Landing Template<br />
<br />
== Blog Manager ==<br />
<br />
Navigate to the Blog Manager page. Edit each blog record to assign a value into the "notificationFrom" field. If no value is assigned, then the CommonSpot site administrator email will be used as the from address for notification emails.<br />
<br />
After modifying the template names above, please edit and review the settings for the for the "Edit App Configuration" form fields for the template select are correct. Additionally, edit and review the blog records to make sure the "Blog Post Template" select field has the correct template selected.<br />
<br />
== Site Level Customizations Review ==<br />
This is only for reviewing the site level customizations in the "/_cs_apps/pt_blog/" directory, not in the ADF directory.<br />
<br />
# Analyze the updated app code compared to the app customization code on your server.<br />
## Identify any customizations that you have made to the application code to make sure these are updated with any functionality.<br />
## Again, Beyond Compare is a good tool to compare the new and current file to identify the exact lines of code that have been changed. <br />
## This is important for components that have customized functions to the site level "/_cs_apps/". The best practice is to identify the function that have been customized and compare with the new app function to identify any updates. A good help is to check the function comment header to see if any updates have been made.<br />
# Once completed, Reset the ADF.<br />
<br />
== Reset the ADF ==<br />
[[Reset ADF|Reset the ADF]] for the server and site.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation&diff=6517OHSU Navigation2013-04-24T17:22:24Z<p>Mcarroll: /* Installation Guides */</p>
<hr />
<div>== About Navigation App ==<br />
The [http://community.paperthin.com/projects/ohsu_navigation/ OHSU Navigation] application is built in the [[Overview|Application Development Framework (ADF)]].<br />
<br />
== Overview ==<br />
The OHSU Navigation app handles your site navigation with ease. On page creation a metadata form allows the user to add their page to navigation and through an intuitive drag and drop interface move the page into their desired order. The navigation system handles navigation nesting (trees) by default through the use of subsites.<br />
<br />
== Pre-installation Considerations ==<br />
The [[Overview|ADF]] must be setup and configured on the server for the site that will be implementing the Navigation application. For detailed instructions follow the [[Overview|ADF Overview]] wiki page for Site Configurations.<br />
<br />
This installation guide assumes that you have no Custom Elements/Metadata Forms with the names above. Before the install, remove any Custom Elements/Metadata Forms with the names listed in the "Contents" section above. (If you do not remove existing elements with these names, you may have difficulties during the installation.)<br />
<br />
CommonSpot Required Features:<br />
* Simple Forms/Datasheets<br />
* Custom Metadata<br />
* CCAPI<br />
<br />
The ADF must be configured correctly for your site. The [[Site Configuration (ADF.cfc)]] wiki page has instructions for configuration.<br />
<br />
The Content Creation API (CCAPI) must be configured for your site. The [[CCAPI_Config|CCAPI Configuration]] wiki page has instructions for configuration.<br />
<br />
== Installation Guides ==<br />
Current Release v2.0:<br />
* [[OHSU_Navigation_Release_Notes_v2.0|Release Notes]]<br />
* [[OHSU_Navigation_Install_v2.0|Install Guide]]<br />
* [[OHSU_Navigation_Upgrade_v2.0|Upgrade Guide]]<br />
<br />
Previous Releases:<br />
* v1.0:<br />
** [[OHSU_Navigation_Install_v1.0|Install Guide]]<br />
<br />
== Guides ==<br />
* [[Using the Navigation Application]]<br />
* [[Customizing Navigation Rendering]]<br />
* [[Navigation Element Best Practices]]<br />
<br />
== Known Issues/Bugs ==<br />
* Visit the [http://community.paperthin.com/projects/ohsu_nav/ OHSU Navigation] project page in the Community site.<br />
<br />
[[Category:Project]][[Category:OHSU Navigation]]</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Main_Page&diff=6515Main Page2013-04-11T19:43:03Z<p>Mcarroll: /* What is the ADF? */</p>
<hr />
<div><!-- // Hide the table of contents for the home page --><br />
__NOTOC__<br />
<br />
<big>'''Application Development Framework (ADF) Wiki'''</big><br />
<br />
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.<br />
<br />
== What is the ADF? ==<br />
The ADF is an Open Source framework that connects into your CommonSpot installation to allow you to develop applications and extend your CommonSpot site easily. The ADF is:<br />
<br />
* A set of utilities (e.g. application.ADF.csData.getPageMetadata(pageID) )<br />
* A methodology for developing portable CommonSpot applications<br />
* Programmatic access to more CommonSpot data then ever before<br />
* Easily installable<br />
* Easily upgradeable<br />
* FUN!<br />
<br />
<h4>[[Overview|Get a detailed overview of the ADF here]]</h4><br />
<br />
<div class="float_box fixed"><br />
<h3>Haven't installed yet</h3><br />
* [[Overview | Overview ]]<br />
* [[Architecture | Architecture ]]<br />
* [[Download | Download]]<br />
* [[Installation|Installation]]<br />
* [[Upgrade|Upgrade]]<br />
* [[View All| View All Projects]]<br />
* [[Starter App | Install the Starter App]]<br />
</div><br />
<br />
<div class="float_box fixed"><br />
<h3>Installed and ready to go</h3><br />
* [[Getting Started | Getting Started with the ADF]]<br />
* [http://community.paperthin.com/projects/ADF/docs/library/ Library (API)]<br />
* [http://community.paperthin.com/projects/ADF/forum Forums]<br />
* [[Ajax]]<br />
* [[Architecture ]]<br />
<br />
</div><br />
<br />
<div class="float_box fixed"><br />
<h3>Building Applications and extending</h3><br />
* [[ADF Applications |Creating a new application]]<br />
* [[Add_ADF_Library_Components_into_App|Loading ADF Library Components into your application ]]<br />
* [http://community.paperthin.com/projects/ADF/forum Forums]<br />
</div><br />
<br />
<div style="clear:both;"><br />
&nbsp;<br />
</div></div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Main_Page&diff=6514Main Page2013-04-11T19:42:51Z<p>Mcarroll: /* What is the ADF? */</p>
<hr />
<div><!-- // Hide the table of contents for the home page --><br />
__NOTOC__<br />
<br />
<big>'''Application Development Framework (ADF) Wiki'''</big><br />
<br />
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.<br />
<br />
== What is the ADF? ==<br />
The ADF is an Open Source framework that connects into your CommonSpot installation to allow you to develop applications and extend your CommonSpot site easily. The ADF is:<br />
<br />
* A set of utilities (e.g. application.ADF.csData.getPageMetadata(pageID) )<br />
* A methodology for developing portable CommonSpot applications<br />
* Programmatic access to more CommonSpot data then ever before<br />
* Easily installable<br />
* Easily upgradeable<br />
* FUN!<br />
<br />
<h4>[[Overview|Get a detailed overview of the ADF here]]</h4><br />
<br />
<div class="float_box fixed"><br />
<h3>Haven't installed yet</h3><br />
* [[Overview | Overview ]]<br />
* [[Architecture | Architecture ]]<br />
* [[Download | Download]]<br />
* [[Installation|Installation]]<br />
* [[Upgrade|Upgrade]]<br />
* [[View All| View All Projects]]<br />
* [[Starter App | Install the Starter App]]<br />
</div><br />
<br />
<div class="float_box fixed"><br />
<h3>Installed and ready to go</h3><br />
* [[Getting Started | Getting Started with the ADF]]<br />
* [http://community.paperthin.com/projects/ADF/docs/library/ | Library (API)]<br />
* [http://community.paperthin.com/projects/ADF/forum Forums]<br />
* [[Ajax]]<br />
* [[Architecture ]]<br />
<br />
</div><br />
<br />
<div class="float_box fixed"><br />
<h3>Building Applications and extending</h3><br />
* [[ADF Applications |Creating a new application]]<br />
* [[Add_ADF_Library_Components_into_App|Loading ADF Library Components into your application ]]<br />
* [http://community.paperthin.com/projects/ADF/forum Forums]<br />
</div><br />
<br />
<div style="clear:both;"><br />
&nbsp;<br />
</div></div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Page_Rating&diff=6513PT Page Rating2013-04-09T18:45:03Z<p>Mcarroll: /* Installation/Setup */</p>
<hr />
<div>== Overview ==<br />
This application provides the ability for your site visitors to rate the usefulness of your page.<br />
<br />
The ADF Page Rating Application is built in the [[Overview|Application Development Framework (ADF)]].<br />
<br />
== Pre-installation Considerations ==<br />
[[Overview|Application Development Framework (ADF)]] must be setup and configured on the server for the site. For detailed instructions, see the [[Overview|Application Development Framework (ADF)]] wiki page for Site Configurations.<br />
<br />
== Installation/Setup ==<br />
'''Current Release:'''<br />
* v2.1:<br />
** [[PT_Page_Rating_Release_Notes_v2|Release Notes]]<br />
** [[PT_Page_Rating_Install_v2|Install Guide]]<br />
** [[PT_Page_Rating_Upgrade_v2|Upgrade Guide]]<br />
<br />
'''Previous Version:'''<br />
* v1.0<br />
** [[PT_Page_Rating_1.0_Install|Version 1.0 Install Guide]]<br />
<br />
<!--<br />
'''Current Development Build:'''<br />
* v2.1:<br />
* [[PT_Page_Rating_Release_Notes_v2.1|Release Notes]]<br />
* [[PT_Page_Rating_Install_v2.1|Install Guide]]<br />
* [[PT_Page_Rating_Upgrade_v2.1|Upgrade Guide]]<br />
--><br />
<br />
== Getting Started==<br />
* [[PT_Page_Rating_Getting_Started|Getting Started]]</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments_Install_v2.1&diff=6512PT Comments Install v2.12013-04-09T18:27:51Z<p>Mcarroll: </p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.1.<br />
<br />
For v2.1, the primary change that occurred was a bug fix requiring updates to potentially the .HEAD file and to a filter on pages where the Comment element exists.<br />
<br />
If you added the following code to your site's .HEAD file:<br />
<br />
<cfset request.params.comments.contentDataPageID = request.page.id> <br />
<br />
you will need to modify the .HEAD and change the code to the following:<br />
<br />
<cfset request.comments.contentDataPageID = request.page.id><br />
<br />
Next, you will need to change the render mode filter on any page or template where the comments element is used:<br />
<br />
<br />
# Update the render mode on the Comments element<br />
## Select "Display existing element data (content reuse)"<br />
## Select "Render results dynamically based on a filter, or display all records."<br />
## click on filter<br />
## select "Subset of records"<br />
## in the dropdown select Comments.contentDataPageID<br />
## Set the comparison to equals<br />
## click the ... next to the value<br />
## change request.params.comments.contentDataPageID to request.comments.contentDataPageID<br />
## Sort Order: dateTimePosted ASCENDING<br />
## click save<br />
# submit your page</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments&diff=6511PT Comments2013-04-09T18:27:38Z<p>Mcarroll: /* Installation/Setup */</p>
<hr />
<div>== Overview ==<br />
The Comments application provides the flexibility to add comments to any custom element within the CommonSpot site. Functionality to dynamically add a comments block to news articles, publications, etc. <br />
<br />
The Comments application is built in the [[Overview|Application Development Framework (ADF)]].<br />
<br />
== Pre-installation Considerations ==<br />
[[Overview|Application Development Framework (ADF)]] must be setup and configured on the server for the site. For detailed instructions, see the [[Overview|Application Development Framework (ADF)]] wiki page for Site Configurations.<br />
<br />
The CCAPI must be configured for the site. Follow the steps to set up the [[CCAPI Config|CCAPI Config]] file for the site.<br />
<br />
== Installation/Setup ==<br />
Each of the following steps should be completed fully and in the order presented:<br />
<br />
Current Release v2.1:<br />
* [[PT_Comments_Install_v2|Upgrade Guide]]<br />
<br />
Previous Release v1.0:<br />
* [[PT_Comments_Release_Notes_v1|Release Notes]]<br />
* [[PT_Comments_Install_v1|Install Guide]]<br />
<br />
== Contents ==<br />
The Comments Application contains the following:<br />
* '''Custom Elements:'''<br />
** [[PT_Comments_Custom_Element|Comment]] - Custom Element<br />
<br />
Note: Elements may contain one or more: Render Handlers, Display Templates, or Custom Field Types<br />
<br />
== Going Further ==<br />
* [[PT_Comments_Going_Further|Going Further]] - Guide to using comments for more than just a page.<br />
<br />
[[Category:Project]]<br />
[[Category:Comments]]</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Photo_Gallery_Overview&diff=6486PT Photo Gallery Overview2013-03-15T17:45:43Z<p>Mcarroll: /* Installation Guides */</p>
<hr />
<div>== About Photo Gallery App ==<br />
The Photo Gallery application is built in the [[Overview|Application Development Framework (ADF)]].<br />
<br />
== Overview ==<br />
The Photo Gallery provides the ability to set dimension requirements for the uploaded image and to resize according to the sizes selected for the category. <br />
<br />
A Photo Category is associated with Photo Size elements. The selections are the dimensions required for the initial upload and the resize processing dimensions. The fields in the element define the category title and the directory to store the category's upload images.<br />
<br />
The Photo Size element provides a collection of predefined dimensions and directory names. Elements are selected and associated with the Photo Category. <br />
<br />
The Photo element stores the information for the uploaded photo. This element stores the path to the original photo and the category for the photo. Combining these fields, we are able to return the size breakdowns for the photo category.<br />
<br />
== Pre-installation Considerations ==<br />
[[Overview|Application Development Framework (ADF)]] must be setup and configured on the server for the site that will be implementing the Photo Gallery application. For detailed instructions, see the [[Overview|Application Development Framework (ADF)]] wiki page for Site Configurations.<br />
<br />
== Installation Guides ==<br />
Current Release v3.0:<br />
* [[PT_Photo_Gallery_Release_Notes_v3.0|Release Notes]]<br />
* [[PT_Photo_Gallery_Install_v3.0|Install Guide]]<br />
* [[PT_Photo_Gallery_Upgrade_v3.0|Upgrade Guide]]<br />
<br />
Previous Versions:<br />
* v2.3:<br />
** [[PT_Photo_Gallery_Version_2.3_Release_Notes|Release Notes]]<br />
** [[PT_Photo_Gallery_Version_2.3_Install|Install Guide]]<br />
** [[PT_Photo_Gallery_Version_2.3_Upgrade|Upgrade Guide]]<br />
* v2.2<br />
** [[PT_Photo_Gallery_Version_2.2_Release_Notes|Version 2.2 Release Notes]]<br />
** [[PT_Photo_Gallery_Version_2.2_Install|Version 2.2 Install Guide]]<br />
** [[PT_Photo_Gallery_Version_2.2_Upgrade|Version 2.2 Upgrade Guide]]<br />
* v2.1<br />
** [[PT_Photo_Gallery_Version_2.1_Release_Notes|Version 2.1 Release Notes]]<br />
** [[PT_Photo_Gallery_Version_2.1_Install|Version 2.1 Install Guide]]<br />
** [[PT_Photo_Gallery_Version_2.1_Upgrade|Version 2.1 Upgrade Guide]]<br />
* v2.0<br />
** [[PT_Photo_Gallery_Version_2.0_Install|Version 2.0 Install Guide]]<br />
** [[PT_Photo_Gallery_Version_2.0_Upgrade|Version 2.0 Upgrade Guide]]<br />
* v1.2<br />
** [[PT_Photo_Gallery_Version_1.2_Install | Install v1.2 ]]<br />
<br />
== Getting Started==<br />
* [[PT_Photo_Gallery_Getting_Started|Getting Started]] - Guide to set up the photo sizes and categories.<br />
<br />
== Features ==<br />
The photo gallery application provides the following features:<br />
* [[PT_Photo_Gallery_Gallery_Element|Gallery Element]]<br />
* [[PT_Photo_Gallery_Upload_Link_CFT|Upload Link Custom Field Type]]<br />
* [[PT_Photo_Gallery_CS_Image_Gallery|Integration with CS Image Gallery]]<br />
* [[PT_Photo_Gallery_Photo_Manager_Styles|Customize Photo Manager Styles]]<br />
* [[PT_Photo_Gallery_Photo_Size_Types|Photo Size Types]]<br />
* [[PT_Photo_Gallery_Cropper_Field|Photo Cropper Custom Field]]<br />
<br />
== Troubleshooting ==<br />
<br />
== Known Issues/Bugs ==<br />
Found a bug? View the [[Photo Gallery Known_Issues_Bugs|Known Issues/Bugs]] wiki page. Your issue not on the list? Post it so the issue can be addressed.<br />
<br />
[[Category:Project]]<br />
[[Category:Photo Gallery]]</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade&diff=6485Upgrade2013-03-15T17:42:59Z<p>Mcarroll: /* Overview */</p>
<hr />
<div>== Overview ==<br />
The upgrade guides are below for the specific ADF versions.<br />
<br />
[[Upgrade_Guide_v1.6|1.6 Upgrade Guide]]<br />
<br />
[[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
<br />
[[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
<br />
[[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Download&diff=6484Download2013-03-15T17:42:29Z<p>Mcarroll: /* Releases */</p>
<hr />
<div>== Download ==<br />
This is the recommended versions of the ADF to use for your CommonSpot sites and ADF applications.<br />
<br />
The code in here should be stable and usable.<br />
<br />
== Releases ==<br />
=== Current Release ===<br />
* 1.6 ([http://community.paperthin.com/projects/ADF/docs/Release-Notes-v1-6.cfm Release Notes])<br />
[http://community.paperthin.com/projects/ADF/svn/index.cfm Download]<br />
<br />
=== Past Release ===<br />
* 1.5.2 ([http://community.paperthin.com/projects/ADF/docs/Release-Notes-v1-5-2.cfm Release Notes])<br />
* 1.5.1 ([[Release_Notes_v1.5.1|Release Notes]])<br />
* 1.5 ([[Release_Notes_v1.5|Release Notes]])<br />
* 1.0 ([http://community.paperthin.com/projects/ADF/blog/2010/version-1-0-release-notes.cfm Release Notes])<br />
<br />
[http://community.paperthin.com/projects/ADF/svn/index.cfm All Downloads]<br />
<br />
== SVN ==<br />
SVN repository is available for the ADF for downloading. The SVN repository URL and packaged zip downloads are available on the [http://community.paperthin.com/projects/ADF/svn/index.cfm ADF Project Page].</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6483Upgrade Guide v1.62013-03-13T17:29:41Z<p>Mcarroll: </p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "/ADF/" directory to "/ADF-1.5/".<br />
# Create a new "/ADF/" directory. Setup any neccessary security or permissions for the new "/ADF/" directory.<br />
# Export the download ADF zip folder into the "/ADF/" directory.<br />
# Copy the contents of the "/ADF_1.5.2/apps/" directory into the "/ADF/apps/" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
<br />
== Post Upgrade Steps ==<br />
<br />
=== Library Updates ===<br />
The following library component functions were moved to the correct component version. If you have custom code referencing these functions within the specific library component, then you'll need to update your library component reference. If you are referencing these functions through the ADF application space, then no updates are needed.<br />
<br />
Lib Components Updates:<br />
* CSData 1.1 functions moved to CSData 1.2:<br />
** getUserNameFromUserID<br />
** getCustomMetadataFieldParamValue<br />
** getCustomMetadatawithFieldLabelsKeys<br />
* CSSecurity 1.1 functions moved to CSSecurity 1.2:<br />
** isValidAuthToken<br />
* Scripts 1.1 functions moved to Scripts 1.2:<br />
** loadFileUploader<br />
** loadJSONJS<br />
** loadJQueryCapty<br />
** loadJQueryMultiselect<br />
** loadJQueryPlupload<br />
** loadJQuerySWFUpload<br />
** loadJQueryTemplates<br />
** loadJQueryUIForm<br />
** loadMathUUID<br />
** loadTipsy<br />
** loadJQueryEasing<br />
** loadJQueryFancyBox<br />
** loadJQueryMouseWheel<br />
* Utils 1.0 functions moved to Utils 1.2:<br />
** pageRedirect<br />
** buildPaginationStruct<br />
** fileLastModifiedDateTime<br />
<br />
=== Forms Library ===<br />
If your site is running CommonSpot 8.0.1 or higher, then you'll need to make sure any custom code utilizing the Forms library calling the "renderAddEditForm" function has been updated for the 8.0.1 security enhancements. The 8.0.1 security enhancements are documented in the [http://www.paperthin.com/support/knowledgebase/doclibrary/index.cfm Summer 2012 SP1 Release Notes].<br />
<br />
This security updates prevents JavaScript "alert" or "confirm" commands to be passed into the Forms.renderAddEditForm "customizedFinalHtml" argument string. <br />
<br />
For example, the following code will '''not''' work: <br />
<source lang="cfm"><br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<script type="text/javascript"><br />
alert("Form Submitted Alert Message");<br />
</script><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
</source><br />
<br />
For example, the following code will work: <br />
<br />
<source lang="cfm"><br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
</source><br />
<br />
Please check your custom code and custom ADF applications to resolve any errors from this security enhancement.<br />
<br />
The ADF v1.6 and the latest ADF application versions have been updated for this security enhancement. You may need to upgrade your ADF applications.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6482Upgrade Guide v1.62013-03-13T17:28:40Z<p>Mcarroll: /* Forms Library */</p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "/ADF/" directory to "/ADF-1.5/".<br />
# Create a new "/ADF/" directory. Setup any neccessary security or permissions for the new "/ADF/" directory.<br />
# Export the download ADF zip folder into the "/ADF/" directory.<br />
# Copy the contents of the "/ADF_1.5.2/apps/" directory into the "/ADF/apps/" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
<br />
== Post Upgrade Steps ==<br />
<br />
=== Library Updates ===<br />
The following library component functions were moved to the correct component version. If you have custom code referencing these functions within the specific library component, then you'll need to update your library component reference. If you are referencing these functions through the ADF application space, then no updates are needed.<br />
<br />
Lib Components Updates:<br />
* CSData 1.1 functions moved to CSData 1.2:<br />
** getUserNameFromUserID<br />
** getCustomMetadataFieldParamValue<br />
** getCustomMetadatawithFieldLabelsKeys<br />
* CSSecurity 1.1 functions moved to CSSecurity 1.2:<br />
** isValidAuthToken<br />
* Scripts 1.1 functions moved to Scripts 1.2:<br />
** loadFileUploader<br />
** loadJSONJS<br />
** loadJQueryCapty<br />
** loadJQueryMultiselect<br />
** loadJQueryPlupload<br />
** loadJQuerySWFUpload<br />
** loadJQueryTemplates<br />
** loadJQueryUIForm<br />
** loadMathUUID<br />
** loadTipsy<br />
** loadJQueryEasing<br />
** loadJQueryFancyBox<br />
** loadJQueryMouseWheel<br />
* Utils 1.0 functions moved to Utils 1.2:<br />
** pageRedirect<br />
** buildPaginationStruct<br />
** fileLastModifiedDateTime<br />
<br />
=== Forms Library ===<br />
If your site is running CommonSpot 8.0.1 or higher, then you'll need to make sure any custom code utilizing the Forms library calling the "renderAddEditForm" function has been updated for the 8.0.1 security enhancements. The 8.0.1 security enhancements are documented in the [http://www.paperthin.com/support/knowledgebase/doclibrary/index.cfm Summer 2012 SP1 Release Notes].<br />
<br />
This security updates prevents JavaScript "alert" or "confirm" commands to be passed into the Forms.renderAddEditForm "customizedFinalHtml" argument string. <br />
<br />
For example, the following code will '''not''' work: <br />
<source lang="java"><br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<script type="text/javascript"><br />
alert("Form Submitted Alert Message");<br />
</script><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
</source><br />
<br />
For example, the following code will work: <br />
<br />
<source lang="java"><br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
</source><br />
<br />
Please check your custom code and custom ADF applications to resolve any errors from this security enhancement.<br />
<br />
The ADF v1.6 and the latest ADF application versions have been updated for this security enhancement. You may need to upgrade your ADF applications.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6481Upgrade Guide v1.62013-03-13T17:26:41Z<p>Mcarroll: /* Forms Library */</p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "/ADF/" directory to "/ADF-1.5/".<br />
# Create a new "/ADF/" directory. Setup any neccessary security or permissions for the new "/ADF/" directory.<br />
# Export the download ADF zip folder into the "/ADF/" directory.<br />
# Copy the contents of the "/ADF_1.5.2/apps/" directory into the "/ADF/apps/" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
<br />
== Post Upgrade Steps ==<br />
<br />
=== Library Updates ===<br />
The following library component functions were moved to the correct component version. If you have custom code referencing these functions within the specific library component, then you'll need to update your library component reference. If you are referencing these functions through the ADF application space, then no updates are needed.<br />
<br />
Lib Components Updates:<br />
* CSData 1.1 functions moved to CSData 1.2:<br />
** getUserNameFromUserID<br />
** getCustomMetadataFieldParamValue<br />
** getCustomMetadatawithFieldLabelsKeys<br />
* CSSecurity 1.1 functions moved to CSSecurity 1.2:<br />
** isValidAuthToken<br />
* Scripts 1.1 functions moved to Scripts 1.2:<br />
** loadFileUploader<br />
** loadJSONJS<br />
** loadJQueryCapty<br />
** loadJQueryMultiselect<br />
** loadJQueryPlupload<br />
** loadJQuerySWFUpload<br />
** loadJQueryTemplates<br />
** loadJQueryUIForm<br />
** loadMathUUID<br />
** loadTipsy<br />
** loadJQueryEasing<br />
** loadJQueryFancyBox<br />
** loadJQueryMouseWheel<br />
* Utils 1.0 functions moved to Utils 1.2:<br />
** pageRedirect<br />
** buildPaginationStruct<br />
** fileLastModifiedDateTime<br />
<br />
=== Forms Library ===<br />
If your site is running CommonSpot 8.0.1 or higher, then you'll need to make sure any custom code utilizing the Forms library calling the "renderAddEditForm" function has been updated for the 8.0.1 security enhancements. The 8.0.1 security enhancements are documented in the Summer 2012 SP1 Release Notes.<br />
<br />
This security updates prevents JavaScript "alert" or "confirm" commands to be passed into the Forms.renderAddEditForm "customizedFinalHtml" argument string. <br />
<br />
For example, the following code will '''not''' work: <br />
<source lang="java"><br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<script type="text/javascript"><br />
alert("Form Submitted Alert Message");<br />
</script><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
</source><br />
<br />
For example, the following code will work: <br />
<br />
<source lang="java"><br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
</source><br />
<br />
Please check your custom code and custom ADF applications to resolve any errors from this security enhancement.<br />
<br />
The ADF v1.6 and the latest ADF application versions have been updated for this security enhancement. You may need to upgrade your ADF applications.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6480Upgrade Guide v1.62013-03-13T17:24:37Z<p>Mcarroll: /* Forms Library */</p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "/ADF/" directory to "/ADF-1.5/".<br />
# Create a new "/ADF/" directory. Setup any neccessary security or permissions for the new "/ADF/" directory.<br />
# Export the download ADF zip folder into the "/ADF/" directory.<br />
# Copy the contents of the "/ADF_1.5.2/apps/" directory into the "/ADF/apps/" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
<br />
== Post Upgrade Steps ==<br />
<br />
=== Library Updates ===<br />
The following library component functions were moved to the correct component version. If you have custom code referencing these functions within the specific library component, then you'll need to update your library component reference. If you are referencing these functions through the ADF application space, then no updates are needed.<br />
<br />
Lib Components Updates:<br />
* CSData 1.1 functions moved to CSData 1.2:<br />
** getUserNameFromUserID<br />
** getCustomMetadataFieldParamValue<br />
** getCustomMetadatawithFieldLabelsKeys<br />
* CSSecurity 1.1 functions moved to CSSecurity 1.2:<br />
** isValidAuthToken<br />
* Scripts 1.1 functions moved to Scripts 1.2:<br />
** loadFileUploader<br />
** loadJSONJS<br />
** loadJQueryCapty<br />
** loadJQueryMultiselect<br />
** loadJQueryPlupload<br />
** loadJQuerySWFUpload<br />
** loadJQueryTemplates<br />
** loadJQueryUIForm<br />
** loadMathUUID<br />
** loadTipsy<br />
** loadJQueryEasing<br />
** loadJQueryFancyBox<br />
** loadJQueryMouseWheel<br />
* Utils 1.0 functions moved to Utils 1.2:<br />
** pageRedirect<br />
** buildPaginationStruct<br />
** fileLastModifiedDateTime<br />
<br />
=== Forms Library ===<br />
If your site is running CommonSpot 8.0.1 or higher, then you'll need to make sure any custom code utilizing the Forms library calling the "renderAddEditForm" function has been updated for the 8.0.1 security enhancements. The 8.0.1 security enhancements are documented in the Summer 2012 SP1 Release Notes.<br />
<br />
This security updates prevents JavaScript "alert" or "confirm" commands to be passed into the Forms.renderAddEditForm "customizedFinalHtml" argument string. <br />
<br />
For example, the following code will '''not''' work: <br />
<source lang="java"><br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<script type="text/javascript"><br />
alert("Form Submitted Alert Message");<br />
</script><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
</source><br />
<br />
For example, the following code will work: <br />
<br />
<source lang="java"><br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
</source><br />
<br />
Thanks for upgrading and start enjoying the ADF!</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6479Upgrade Guide v1.62013-03-13T17:24:13Z<p>Mcarroll: /* Forms Library */</p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "/ADF/" directory to "/ADF-1.5/".<br />
# Create a new "/ADF/" directory. Setup any neccessary security or permissions for the new "/ADF/" directory.<br />
# Export the download ADF zip folder into the "/ADF/" directory.<br />
# Copy the contents of the "/ADF_1.5.2/apps/" directory into the "/ADF/apps/" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
<br />
== Post Upgrade Steps ==<br />
<br />
=== Library Updates ===<br />
The following library component functions were moved to the correct component version. If you have custom code referencing these functions within the specific library component, then you'll need to update your library component reference. If you are referencing these functions through the ADF application space, then no updates are needed.<br />
<br />
Lib Components Updates:<br />
* CSData 1.1 functions moved to CSData 1.2:<br />
** getUserNameFromUserID<br />
** getCustomMetadataFieldParamValue<br />
** getCustomMetadatawithFieldLabelsKeys<br />
* CSSecurity 1.1 functions moved to CSSecurity 1.2:<br />
** isValidAuthToken<br />
* Scripts 1.1 functions moved to Scripts 1.2:<br />
** loadFileUploader<br />
** loadJSONJS<br />
** loadJQueryCapty<br />
** loadJQueryMultiselect<br />
** loadJQueryPlupload<br />
** loadJQuerySWFUpload<br />
** loadJQueryTemplates<br />
** loadJQueryUIForm<br />
** loadMathUUID<br />
** loadTipsy<br />
** loadJQueryEasing<br />
** loadJQueryFancyBox<br />
** loadJQueryMouseWheel<br />
* Utils 1.0 functions moved to Utils 1.2:<br />
** pageRedirect<br />
** buildPaginationStruct<br />
** fileLastModifiedDateTime<br />
<br />
=== Forms Library ===<br />
If your site is running CommonSpot 8.0.1 or higher, then you'll need to make sure any custom code utilizing the Forms library calling the "renderAddEditForm" function has been updated for the 8.0.1 security enhancements. The 8.0.1 security enhancements are documented in the Summer 2012 SP1 Release Notes.<br />
<br />
This security updates prevents JavaScript "alert" or "confirm" commands to be passed into the Forms.renderAddEditForm "customizedFinalHtml" argument string. <br />
<br />
For example, the following code will not work: <br />
<source lang="java"><br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<script type="text/javascript"><br />
alert("Form Submitted Alert Message");<br />
</script><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
</source><br />
<br />
For example, the following code will work: <br />
<br />
<source lang="java"><br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
</source><br />
<br />
Thanks for upgrading and start enjoying the ADF!</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6478Upgrade Guide v1.62013-03-13T17:23:27Z<p>Mcarroll: /* Post Upgrade Steps */</p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "/ADF/" directory to "/ADF-1.5/".<br />
# Create a new "/ADF/" directory. Setup any neccessary security or permissions for the new "/ADF/" directory.<br />
# Export the download ADF zip folder into the "/ADF/" directory.<br />
# Copy the contents of the "/ADF_1.5.2/apps/" directory into the "/ADF/apps/" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
<br />
== Post Upgrade Steps ==<br />
<br />
=== Library Updates ===<br />
The following library component functions were moved to the correct component version. If you have custom code referencing these functions within the specific library component, then you'll need to update your library component reference. If you are referencing these functions through the ADF application space, then no updates are needed.<br />
<br />
Lib Components Updates:<br />
* CSData 1.1 functions moved to CSData 1.2:<br />
** getUserNameFromUserID<br />
** getCustomMetadataFieldParamValue<br />
** getCustomMetadatawithFieldLabelsKeys<br />
* CSSecurity 1.1 functions moved to CSSecurity 1.2:<br />
** isValidAuthToken<br />
* Scripts 1.1 functions moved to Scripts 1.2:<br />
** loadFileUploader<br />
** loadJSONJS<br />
** loadJQueryCapty<br />
** loadJQueryMultiselect<br />
** loadJQueryPlupload<br />
** loadJQuerySWFUpload<br />
** loadJQueryTemplates<br />
** loadJQueryUIForm<br />
** loadMathUUID<br />
** loadTipsy<br />
** loadJQueryEasing<br />
** loadJQueryFancyBox<br />
** loadJQueryMouseWheel<br />
* Utils 1.0 functions moved to Utils 1.2:<br />
** pageRedirect<br />
** buildPaginationStruct<br />
** fileLastModifiedDateTime<br />
<br />
=== Forms Library ===<br />
If your site is running CommonSpot 8.0.1 or higher, then you'll need to make sure any custom code utilizing the Forms library calling the "renderAddEditForm" function has been updated for the 8.0.1 security enhancements. The 8.0.1 security enhancements are documented in the Summer 2012 SP1 Release Notes.<br />
<br />
This security updates prevents JavaScript "alert" or "confirm" commands to be passed into the Forms.renderAddEditForm "customizedFinalHtml" argument string. <br />
<br />
For example, the following code will not work: <br />
<br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<script type="text/javascript"><br />
alert("Form Submitted Alert Message");<br />
</script><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
<br />
For example, the following code will work: <br />
<br />
<cfsavecontent variable="returnHMTL"><br />
<cfoutput><br />
<p>Thank You for submitting the form.</p><br />
</cfoutput><br />
</cfsavecontent><br />
<cfoutput><br />
#application.ADF.forms.renderAddEditForm(formID=myCEFormID,<br />
dataPageId=meCEDataPageID,<br />
customizedFinalHtml=returnHMTL)#<br />
</cfoutput><br />
<br />
<br />
Thanks for upgrading and start enjoying the ADF!</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6477Upgrade Guide v1.62013-03-13T17:12:11Z<p>Mcarroll: /* Post Upgrade Steps */</p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "/ADF/" directory to "/ADF-1.5/".<br />
# Create a new "/ADF/" directory. Setup any neccessary security or permissions for the new "/ADF/" directory.<br />
# Export the download ADF zip folder into the "/ADF/" directory.<br />
# Copy the contents of the "/ADF_1.5.2/apps/" directory into the "/ADF/apps/" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
<br />
== Post Upgrade Steps ==<br />
<br />
=== Library Updates ===<br />
The following library component functions were moved to the correct component version. If you have custom code referencing these functions within the specific library component, then you'll need to update your library component reference. If you are referencing these functions through the ADF application space, then no updates are needed.<br />
<br />
Lib Components Updates:<br />
* CSData 1.1 functions moved to CSData 1.2:<br />
** getUserNameFromUserID<br />
** getCustomMetadataFieldParamValue<br />
** getCustomMetadatawithFieldLabelsKeys<br />
* CSSecurity 1.1 functions moved to CSSecurity 1.2:<br />
** isValidAuthToken<br />
* Scripts 1.1 functions moved to Scripts 1.2:<br />
** loadFileUploader<br />
** loadJSONJS<br />
** loadJQueryCapty<br />
** loadJQueryMultiselect<br />
** loadJQueryPlupload<br />
** loadJQuerySWFUpload<br />
** loadJQueryTemplates<br />
** loadJQueryUIForm<br />
** loadMathUUID<br />
** loadTipsy<br />
** loadJQueryEasing<br />
** loadJQueryFancyBox<br />
** loadJQueryMouseWheel<br />
* Utils 1.0 functions moved to Utils 1.2:<br />
** pageRedirect<br />
** buildPaginationStruct<br />
** fileLastModifiedDateTime<br />
<br />
<br />
<br />
<br />
<br />
<br />
Thanks for upgrading and start enjoying the ADF!</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6476Upgrade Guide v1.62013-03-13T17:08:25Z<p>Mcarroll: /* Post Upgrade Steps */</p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "/ADF/" directory to "/ADF-1.5/".<br />
# Create a new "/ADF/" directory. Setup any neccessary security or permissions for the new "/ADF/" directory.<br />
# Export the download ADF zip folder into the "/ADF/" directory.<br />
# Copy the contents of the "/ADF_1.5.2/apps/" directory into the "/ADF/apps/" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
<br />
== Post Upgrade Steps ==<br />
<br />
=== Library Updates ===<br />
The following library component functions were moved to the correct component version:<br />
<br />
Lib Components Updates:<br />
<br />
* CSData 1.1 functions moved to CSData 1.2:<br />
** getUserNameFromUserID<br />
** getCustomMetadataFieldParamValue<br />
** getCustomMetadatawithFieldLabelsKeys<br />
* CSSecurity 1.1 functions moved to CSSecurity 1.2:<br />
** isValidAuthToken<br />
* Scripts 1.1 functions moved to Scripts 1.2:<br />
** loadFileUploader<br />
** loadJSONJS<br />
** loadJQueryCapty<br />
** loadJQueryMultiselect<br />
** loadJQueryPlupload<br />
** loadJQuerySWFUpload<br />
** loadJQueryTemplates<br />
** loadJQueryUIForm<br />
** loadMathUUID<br />
** loadTipsy<br />
** loadJQueryEasing<br />
** loadJQueryFancyBox<br />
** loadJQueryMouseWheel<br />
* Utils 1.0 functions moved to Utils 1.2:<br />
** pageRedirect<br />
** buildPaginationStruct<br />
** fileLastModifiedDateTime<br />
<br />
<br />
<br />
<br />
<br />
<br />
Thanks for upgrading and start enjoying the ADF!</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6475Upgrade Guide v1.62013-03-13T15:23:10Z<p>Mcarroll: </p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "/ADF/" directory to "/ADF-1.5/".<br />
# Create a new "/ADF/" directory. Setup any neccessary security or permissions for the new "/ADF/" directory.<br />
# Export the download ADF zip folder into the "/ADF/" directory.<br />
# Copy the contents of the "/ADF_1.5.2/apps/" directory into the "/ADF/apps/" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
<br />
== Post Upgrade Steps ==<br />
<br />
<br />
<br />
Thanks for upgrading and start enjoying the ADF!</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6474Upgrade Guide v1.62013-03-13T15:22:39Z<p>Mcarroll: </p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "/ADF/" directory to "/ADF-1.5/".<br />
# Create a new "/ADF/" directory. Setup any neccessary security or permissions for the new "/ADF/" directory.<br />
# Export the download ADF zip folder into the "/ADF/" directory.<br />
# Copy the contents of the "/ADF_1.5.2/apps/" directory into the "/ADF/apps/" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
Thanks for upgrading and start enjoying the ADF!</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6473Upgrade Guide v1.62013-03-13T15:20:57Z<p>Mcarroll: </p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "ADF" directory to "ADF-1.5".<br />
# Unzip the ADF v1.6 download and make sure is named as "ADF" on your server. <br />
# Copy all the applications from the "/ADF-1.5/apps/" directory to the "/ADF/apps" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
Thanks for upgrading and start enjoying the ADF!</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6472Upgrade Guide v1.62013-03-13T15:20:42Z<p>Mcarroll: </p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "ADF" directory to "ADF-1.5".<br />
# Unzip the ADF v1.6 download and make sure is named as "ADF" on your server. <br />
# Copy all the applications from the "/ADF-1.5/apps/" directory to the "/ADF/apps" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
Thanks for upgrading and start enjoying the ADF!</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6471Upgrade Guide v1.62013-03-13T15:20:29Z<p>Mcarroll: </p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.6 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "ADF" directory to "ADF-1.5".<br />
# Unzip the ADF v1.6 download and make sure is named as "ADF" on your server. <br />
# Copy all the applications from the "/ADF-1.5/apps/" directory to the "/ADF/apps" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new. <br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.6 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.6<br />
# Upgrade was successful and you are running the ADF v1.6.<br />
<br />
Thanks for upgrading and start enjoying the ADF now!</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade_Guide_v1.6&diff=6470Upgrade Guide v1.62013-03-13T15:14:06Z<p>Mcarroll: Created page with '== Current Version == Follow the guide below if you are upgrading to ADF v1.6. If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF vers…'</p>
<hr />
<div>== Current Version ==<br />
Follow the guide below if you are upgrading to ADF v1.6.<br />
<br />
If you are upgrading from ADF v1.5 or eariler, then please follow the guides for previous ADF versions:<br />
* [[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
* [[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]<br />
<br />
<br />
== Upgrade ==<br />
Follow the steps below to upgrade the ADF directory:<br />
# Download the ADF v1.5.2 from the [http://community.paperthin.com/projects/ADF/ Community site project page].<br />
# On your server, rename the "ADF" directory to "ADF-1.5.1".<br />
# Unzip the ADF v1.5.2 download and make sure is named as "ADF" on your server. <br />
# Copy all the applications from the "/ADF-1.5.1/apps/" directory to the "/ADF/apps" directory.<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
<br />
== Validate Upgrade ==<br />
There are 2 methods to validate the ADF upgrade.<br />
=== ADF Reset ===<br />
# Reset the ADF through the web browser with the following URL parameter:<br />
## ?resetADF=1<br />
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:<br />
## ADF v1.5.2 has been reset successfully!<br />
# Upgrade was successful and you are running the ADF v1.5.2.<br />
<br />
=== ADF Version Output ===<br />
# In the browser, add the following URL parameter:<br />
## ?ADFDumpVar=application.ADF.version<br />
# This command with output the ADF version at the top of the page. If you see the following text:<br />
## 1.5.2<br />
# Upgrade was successful and you are running the ADF v1.5.2.<br />
<br />
Thanks for upgrading and start enjoying the ADF now!</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade&diff=6469Upgrade2013-03-13T15:11:25Z<p>Mcarroll: </p>
<hr />
<div>== Overview ==<br />
The upgrade guides are below for the specific ADF versions.<br />
<br />
[[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
<br />
[[Upgrade_Guide_v1.5.1|1.5.1 Upgrade Guide]]<br />
<br />
[[Upgrade_Guide_v1.5|1.5.0 Upgrade Guide]]</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Upgrade&diff=6468Upgrade2013-03-13T15:10:50Z<p>Mcarroll: </p>
<hr />
<div>== Overview ==<br />
The upgrade guides are below for the specific ADF versions.<br />
<br />
[[Upgrade_Guide_v1.5.2|1.5.2 Upgrade Guide]]<br />
<br />
[http://community.paperthin.com/adf-docs/index.php/Upgrade_Guide_v1.5.1 1.5.1 Upgrade Guide]<br />
<br />
[http://community.paperthin.com/adf-docs/index.php/Upgrade_Guide_v1.5 1.5.0 Upgrade Guide]</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Download&diff=6467Download2013-03-08T18:55:20Z<p>Mcarroll: /* Releases */</p>
<hr />
<div>== Download ==<br />
This is the recommended versions of the ADF to use for your CommonSpot sites and ADF applications.<br />
<br />
The code in here should be stable and usable.<br />
<br />
== Releases ==<br />
=== Current Release ===<br />
* 1.5.2 ([http://community.paperthin.com/projects/ADF/docs/Release-Notes-v1-5-2.cfm Release Notes])<br />
[http://community.paperthin.com/projects/ADF/svn/index.cfm Download]<br />
<br />
=== Development Build ===<br />
* 1.6 ([http://community.paperthin.com/projects/ADF/docs/Release-Notes-v1-6.cfm Release Notes])<br />
<br />
=== Past Release ===<br />
* 1.5.1 ([[Release_Notes_v1.5.1|Release Notes]])<br />
* 1.5 ([[Release_Notes_v1.5|Release Notes]])<br />
* 1.0 ([http://community.paperthin.com/projects/ADF/blog/2010/version-1-0-release-notes.cfm Release Notes])<br />
<br />
[http://community.paperthin.com/projects/ADF/svn/index.cfm All Downloads]<br />
<br />
== SVN ==<br />
SVN repository is available for the ADF for downloading. The SVN repository URL and packaged zip downloads are available on the [http://community.paperthin.com/projects/ADF/svn/index.cfm ADF Project Page].</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=Download&diff=6466Download2013-03-08T18:55:07Z<p>Mcarroll: /* Releases */</p>
<hr />
<div>== Download ==<br />
This is the recommended versions of the ADF to use for your CommonSpot sites and ADF applications.<br />
<br />
The code in here should be stable and usable.<br />
<br />
== Releases ==<br />
=== Current Release ===<br />
* 1.5.2 ([[http://community.paperthin.com/projects/ADF/docs/Release-Notes-v1-5-2.cfm Release Notes]])<br />
[http://community.paperthin.com/projects/ADF/svn/index.cfm Download]<br />
<br />
=== Development Build ===<br />
* 1.6 ([[http://community.paperthin.com/projects/ADF/docs/Release-Notes-v1-6.cfm Release Notes]])<br />
<br />
=== Past Release ===<br />
* 1.5.1 ([[Release_Notes_v1.5.1|Release Notes]])<br />
* 1.5 ([[Release_Notes_v1.5|Release Notes]])<br />
* 1.0 ([http://community.paperthin.com/projects/ADF/blog/2010/version-1-0-release-notes.cfm Release Notes])<br />
<br />
[http://community.paperthin.com/projects/ADF/svn/index.cfm All Downloads]<br />
<br />
== SVN ==<br />
SVN repository is available for the ADF for downloading. The SVN repository URL and packaged zip downloads are available on the [http://community.paperthin.com/projects/ADF/svn/index.cfm ADF Project Page].</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Release_Notes_v3&diff=6357PT Blog Release Notes v32013-02-27T17:46:16Z<p>Mcarroll: </p>
<hr />
<div>We are proud to release v3 to the Community.<br />
<br />
Version 3 is compatible with the ADF v1.6.<br />
<br />
If installing the PT Blog app for the first time, please follow the v3 Install Guide.<br />
<br />
If upgrading from a version 2 or earlier, please complete the v2.0 - v2.3 Upgrade Guides in order.<br />
<br />
=== Enhancements ===<br />
* Updated the App Bean Config v3.0 to support ADF v1.6.<br />
* Updated the RSS generator to support Railo.<br />
* Updated the page standard and custom metadata for the APIPage 1.0 library.<br />
* Updated the delete page to use the API 1.0 Library.<br />
* Added call to stripHTMLtags to remove any HTML added to the blog comment.<br />
* Updated use of notificationEmails and added logic to send mail only if there are "to" and "from" email addresses specififed in the blog configuration. Updated the exported object for the Blog2 custom element.<br />
<br />
=== Bug Fixes ===<br />
* Updated the CSContent to reference from the app bean config.<br />
* Removed any JavaScript "alert" statements that were not used to prevent CommonSpot form errors.<br />
* Updated logic to call "createUniquePageName" and "createUniquePageTitle" to create a page with a unique name and title.<br />
* Added logic to check if the blogURL is a full URL and adds "http://" if it's missing<br />
<br />
=== SVN Change Log ===<br />
For detailed SVN repository updates for the v3, please see the [[PT_Blog_v3_Change_Log|PT Blog v3 Change Log]].</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_v3_Change_Log&diff=6356PT Blog v3 Change Log2013-02-27T17:45:44Z<p>Mcarroll: Created page with 'r112 | mcarroll | 2013-02-27 11:48:38 EST Changed paths: M /branches/3.0/components/App.cfc M /branches/3.0/exported-objects/Blog2-Custom-Element.zip Updated the exported obje…'</p>
<hr />
<div>r112 | mcarroll | 2013-02-27 11:48:38 EST<br />
Changed paths:<br />
M /branches/3.0/components/App.cfc<br />
M /branches/3.0/exported-objects/Blog2-Custom-Element.zip<br />
<br />
Updated the exported object for the Blog2 custom element.<br />
----------------------------------------------------------------------------<br />
r111 | mcarroll | 2013-02-27 11:30:50 EST<br />
Changed paths:<br />
M /branches/3.0/components/App.cfc<br />
<br />
Updated the svn build number for the latest updates committed.<br />
----------------------------------------------------------------------------<br />
r107 | ssmith | 2013-02-25 17:03:26 EST<br />
Changed paths:<br />
M /branches/3.0/exported-objects/Blog2-Custom-Element.zip<br />
<br />
New exported version of Blog2 Custom Element with "Notification From" field included.<br />
----------------------------------------------------------------------------<br />
r106 | ssmith | 2013-02-25 16:53:08 EST<br />
Changed paths:<br />
M /branches/3.0/components/postService.cfc<br />
<br />
postNotification - Updated use of notificationEmails and added logic to send mail only if there are "to" and "from" email addresses specififed in the blog configuration.<br />
----------------------------------------------------------------------------<br />
r105 | ssmith | 2013-02-25 16:52:33 EST<br />
Changed paths:<br />
M /branches/3.0/components/commentsService.cfc<br />
<br />
commentNotification - Updated use of notificationEmails and added logic to send mail only if there are "to" and "from" email addresses specififed in the blog configuration.<br />
----------------------------------------------------------------------------<br />
r104 | ssmith | 2013-02-25 16:52:05 EST<br />
Changed paths:<br />
M /branches/3.0/components/blogService.cfc<br />
<br />
getNotificationEmails - Updated use of getNotificationData since it now returns a struct of email instead of just a string.<br />
<br />
getNotificationData - Updated to return a struct of email addresses (to and from) from blog2 custom element instead of just the "to" addresses.<br />
----------------------------------------------------------------------------<br />
r103 | ssmith | 2013-02-25 16:16:06 EST<br />
Changed paths:<br />
M /branches/3.0/datasheet-modules/delete_element_handler_posts2.cfm<br />
<br />
Fixed comment typos<br />
----------------------------------------------------------------------------<br />
r102 | ssmith | 2013-02-21 15:59:10 EST<br />
Changed paths:<br />
M /branches/3.0/components/postDAO.cfc<br />
<br />
deletePostPage - Now returns the resulting struct from the deletePage call instead of a boolean.<br />
----------------------------------------------------------------------------<br />
r101 | ssmith | 2013-02-21 15:58:39 EST<br />
Changed paths:<br />
M /branches/3.0/components/commentsService.cfc<br />
<br />
getCommentsHTML - Added logic to check if the blogURL is a full URL and adds "http://" if it's missing.<br />
handleCommentsSubmit - Added call to stripHTMLtags to remove any HTML added to the blog comment.<br />
----------------------------------------------------------------------------<br />
r95 | mcarroll | 2013-02-12 11:15:18 EST<br />
Changed paths:<br />
M /branches/3.0/appBeanConfig.cfm<br />
M /branches/3.0/components/postService.cfc<br />
M /branches/3.0/components/postDAO.cfc<br />
M /branches/3.0/components/blogDAO.cfc<br />
M /branches/3.0/components/blogService.cfc<br />
M /branches/3.0/components/App.cfc<br />
M /branches/3.0/renderhandlers/blog_post_short.cfm<br />
<br />
Updated logic to call "createUniquePageName" and "createUniquePageTitle" to create a page with a unique name and title.<br />
Updated the page standard and custom metadata for the APIPage 1.0 library.<br />
Updated the delete page to use the API 1.0 Library.<br />
Updated the RSS generator to support Railo.<br />
----------------------------------------------------------------------------<br />
r94 | mcarroll | 2013-02-08 13:27:01 EST<br />
Changed paths:<br />
M /branches/3.0/components/blogDAO.cfc<br />
M /branches/3.0/components/App.cfc<br />
<br />
Function: createBlogIndexPage, createTagsListingPage<br />
Description: Updated to call the App Bean Config loaded "csContent".<br />
----------------------------------------------------------------------------<br />
r93 | mcarroll | 2013-02-08 13:24:14 EST<br />
Changed paths:<br />
M /branches/3.0/components/postDAO.cfc<br />
<br />
Function: updatePost<br />
Description: Updated to call the App Bean Config loaded "csContent".<br />
----------------------------------------------------------------------------<br />
r92 | mcarroll | 2013-02-06 15:21:59 EST<br />
Changed paths:<br />
M /branches/3.0/customfields/post_page_render.cfm<br />
M /branches/3.0/customcf/manageBlog.cfm<br />
M /branches/3.0/components/App.cfc<br />
M /branches/3.0/customfields/post_page_props.cfm<br />
<br />
Removed any JavaScript "alert" statements that were not used.<br />
----------------------------------------------------------------------------<br />
r91 | mcarroll | 2013-01-24 10:38:21 EST<br />
Changed paths:<br />
M /branches/3.0/appBeanConfig.cfm<br />
M /branches/3.0/components/App.cfc<br />
<br />
Updated App Bean Config to support ADF v1.6.<br />
----------------------------------------------------------------------------<br />
r90 | mcarroll | 2013-01-24 10:23:40 EST<br />
Changed paths:<br />
A /branches/3.0<br />
<br />
Created development branch v3.0 for compatibility with the ADF v1.6.<br />
----------------------------------------------------------------------------</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Release_Notes_v3&diff=6355PT Blog Release Notes v32013-02-27T17:45:36Z<p>Mcarroll: </p>
<hr />
<div>We are proud to release v3 to the Community.<br />
<br />
Version 3 is compatible with the ADF v1.6.<br />
<br />
If installing the PT Blog app for the first time, please follow the v3 Install Guide.<br />
<br />
If upgrading from a version 2 or earlier, please complete the v2.0 - v2.3 Upgrade Guides in order.<br />
<br />
=== Enhancements ===<br />
* Updated the App Bean Config v3.0 to support ADF v1.6.<br />
* Updated the RSS generator to support Railo.<br />
* Updated the page standard and custom metadata for the APIPage 1.0 library.<br />
* Updated the delete page to use the API 1.0 Library.<br />
* Added call to stripHTMLtags to remove any HTML added to the blog comment.<br />
* Updated use of notificationEmails and added logic to send mail only if there are "to" and "from" email addresses specififed in the blog configuration. Updated the exported object for the Blog2 custom element.<br />
<br />
=== Bug Fixes ===<br />
* Updated the CSContent to reference from the app bean config.<br />
* Removed any JavaScript "alert" statements that were not used to prevent CommonSpot form errors.<br />
* Updated logic to call "createUniquePageName" and "createUniquePageTitle" to create a page with a unique name and title.<br />
* Added logic to check if the blogURL is a full URL and adds "http://" if it's missing<br />
<br />
<br />
=== SVN Change Log ===<br />
For detailed SVN repository updates for the v3, please see the [[PT_Blog_v3_Change_Log|PT Blog v3 Change Log]].</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Release_Notes_v3&diff=6344PT Blog Release Notes v32013-02-27T17:10:40Z<p>Mcarroll: Created page with 'We are proud to release v3 to the Community. Version 3 is compatible with the ADF v1.6. If installing the PT Blog app for the first time, please follow the v3 Install Guide. I…'</p>
<hr />
<div>We are proud to release v3 to the Community.<br />
<br />
Version 3 is compatible with the ADF v1.6.<br />
<br />
If installing the PT Blog app for the first time, please follow the v3 Install Guide.<br />
<br />
If upgrading from a version 2 or earlier, please complete the v2.0 - v2.3 Upgrade Guides in order.<br />
<br />
=== Enhancements ===<br />
* Updated the App Bean Config v3.0 to support ADF v1.6.<br />
<br />
=== Bug Fixes ===<br />
* Updated the CSContent to reference from the app bean config.<br />
<br />
=== SVN Change Log ===<br />
For detailed SVN repository updates for the v3, please see the [[PT_Blog_v3_Change_Log|PT Blog v3 Change Log]].</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Upgrade_v3&diff=6341PT Blog Upgrade v32013-02-27T17:07:02Z<p>Mcarroll: /* Custom Elements */</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the PT Blog v2.3 application. If upgrading from a lower version than v2.3, please follow the [[PT_Blog_Version_2.2_Install|Version 2.2 Install Guide]] to validate your installation.<br />
<br />
== Application Code ==<br />
# Renamed directory "/ADF/apps/pt_blog" to "/ADF/apps/pt_blog_v2_3".<br />
# Renamed file "/ADF/apps/pt_blog_v2_3/appBeanConfig.cfm" to "/ADF/apps/pt_blog_v2_3/appBeanConfig.cfm.old".<br />
# Downloaded the PT Blog v3 and exported into the "/ADF/apps/pt_blog/" directory.<br />
<br />
== Custom Elements ==<br />
<br />
=== Blog2 ===<br />
Add the following new fields:<br />
# Name: notificationFrom<br />
## Tab: Notifications<br />
### Move this field to the first field in the Notifications tab.<br />
## Label: From Email Address <br />
## Type: Email<br />
## Description: Email address to be used as the FROM email for the notification emails.<br />
## Properties:<br />
### Size: 40<br />
<br />
== Templates ==<br />
<br />
=== Blog Post Template ===<br />
Navigate to the Blog Post template that was created from the installation. Rename the page to add "template" into the title for easy recognition. <br />
<br />
On the page, open the dialog "Actions > Rename Page..". Update the form fields with the following:<br />
# Name: template-blog-post-template<br />
# Title: Blog Post Template<br />
# Title Bar Caption: Blog Post Template<br />
<br />
=== Landing Page Template ===<br />
Navigate to the Landing Page template that was created from the installation. Rename the page to add "template" into the title for easy recognition. <br />
<br />
On the page, open the dialog "Actions > Rename Page..". Update the form fields with the following:<br />
# Name: template-Blog-Landing-Template<br />
# Title: Blog Landing Template<br />
# Title Bar Caption: Blog Landing Template<br />
<br />
== Blog Manager ==<br />
<br />
Navigate to the Blog Manager page. Edit each blog record to assign a value into the "notificationFrom" field. If no value is assigned, then the CommonSpot site administrator email will be used as the from address for notification emails.<br />
<br />
After modifying the template names above, please edit and review the settings for the for the "Edit App Configuration" form fields for the template select are correct. Additionally, edit and review the blog records to make sure the "Blog Post Template" select field has the correct template selected.<br />
<br />
== Site Level Customizations Review ==<br />
This is only for reviewing the site level customizations in the "/_cs_apps/pt_blog/" directory, not in the ADF directory.<br />
<br />
# Analyze the updated app code compared to the app customization code on your server.<br />
## Identify any customizations that you have made to the application code to make sure these are updated with any functionality.<br />
## Again, Beyond Compare is a good tool to compare the new and current file to identify the exact lines of code that have been changed. <br />
## This is important for components that have customized functions to the site level "/_cs_apps/". The best practice is to identify the function that have been customized and compare with the new app function to identify any updates. A good help is to check the function comment header to see if any updates have been made.<br />
# Once completed, Reset the ADF.<br />
<br />
== Reset the ADF ==<br />
[[Reset ADF|Reset the ADF]] for the server and site.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Upgrade_v3&diff=6340PT Blog Upgrade v32013-02-27T17:06:56Z<p>Mcarroll: /* Blog Manager */</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the PT Blog v2.3 application. If upgrading from a lower version than v2.3, please follow the [[PT_Blog_Version_2.2_Install|Version 2.2 Install Guide]] to validate your installation.<br />
<br />
== Application Code ==<br />
# Renamed directory "/ADF/apps/pt_blog" to "/ADF/apps/pt_blog_v2_3".<br />
# Renamed file "/ADF/apps/pt_blog_v2_3/appBeanConfig.cfm" to "/ADF/apps/pt_blog_v2_3/appBeanConfig.cfm.old".<br />
# Downloaded the PT Blog v3 and exported into the "/ADF/apps/pt_blog/" directory.<br />
<br />
== Custom Elements ==<br />
<br />
=== Blog2 ===<br />
Add the following new fields:<br />
# Name: notificationFrom<br />
## Tab: Notifications<br />
### Move this field to the first field in the Notifications tab.<br />
## Label: From Email Address <br />
## Type: Email<br />
## Description: Email address to be used as the FROM email for the notification emails.<br />
## Properties:<br />
### Size: 40<br />
<br />
<br />
<br />
== Templates ==<br />
<br />
=== Blog Post Template ===<br />
Navigate to the Blog Post template that was created from the installation. Rename the page to add "template" into the title for easy recognition. <br />
<br />
On the page, open the dialog "Actions > Rename Page..". Update the form fields with the following:<br />
# Name: template-blog-post-template<br />
# Title: Blog Post Template<br />
# Title Bar Caption: Blog Post Template<br />
<br />
=== Landing Page Template ===<br />
Navigate to the Landing Page template that was created from the installation. Rename the page to add "template" into the title for easy recognition. <br />
<br />
On the page, open the dialog "Actions > Rename Page..". Update the form fields with the following:<br />
# Name: template-Blog-Landing-Template<br />
# Title: Blog Landing Template<br />
# Title Bar Caption: Blog Landing Template<br />
<br />
== Blog Manager ==<br />
<br />
Navigate to the Blog Manager page. Edit each blog record to assign a value into the "notificationFrom" field. If no value is assigned, then the CommonSpot site administrator email will be used as the from address for notification emails.<br />
<br />
After modifying the template names above, please edit and review the settings for the for the "Edit App Configuration" form fields for the template select are correct. Additionally, edit and review the blog records to make sure the "Blog Post Template" select field has the correct template selected.<br />
<br />
== Site Level Customizations Review ==<br />
This is only for reviewing the site level customizations in the "/_cs_apps/pt_blog/" directory, not in the ADF directory.<br />
<br />
# Analyze the updated app code compared to the app customization code on your server.<br />
## Identify any customizations that you have made to the application code to make sure these are updated with any functionality.<br />
## Again, Beyond Compare is a good tool to compare the new and current file to identify the exact lines of code that have been changed. <br />
## This is important for components that have customized functions to the site level "/_cs_apps/". The best practice is to identify the function that have been customized and compare with the new app function to identify any updates. A good help is to check the function comment header to see if any updates have been made.<br />
# Once completed, Reset the ADF.<br />
<br />
== Reset the ADF ==<br />
[[Reset ADF|Reset the ADF]] for the server and site.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Upgrade_v3&diff=6336PT Blog Upgrade v32013-02-27T17:04:26Z<p>Mcarroll: </p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the PT Blog v2.3 application. If upgrading from a lower version than v2.3, please follow the [[PT_Blog_Version_2.2_Install|Version 2.2 Install Guide]] to validate your installation.<br />
<br />
== Application Code ==<br />
# Renamed directory "/ADF/apps/pt_blog" to "/ADF/apps/pt_blog_v2_3".<br />
# Renamed file "/ADF/apps/pt_blog_v2_3/appBeanConfig.cfm" to "/ADF/apps/pt_blog_v2_3/appBeanConfig.cfm.old".<br />
# Downloaded the PT Blog v3 and exported into the "/ADF/apps/pt_blog/" directory.<br />
<br />
== Custom Elements ==<br />
<br />
=== Blog2 ===<br />
Add the following new fields:<br />
# Name: notificationFrom<br />
## Tab: Notifications<br />
### Move this field to the first field in the Notifications tab.<br />
## Label: From Email Address <br />
## Type: Email<br />
## Description: Email address to be used as the FROM email for the notification emails.<br />
## Properties:<br />
### Size: 40<br />
<br />
<br />
<br />
== Templates ==<br />
<br />
=== Blog Post Template ===<br />
Navigate to the Blog Post template that was created from the installation. Rename the page to add "template" into the title for easy recognition. <br />
<br />
On the page, open the dialog "Actions > Rename Page..". Update the form fields with the following:<br />
# Name: template-blog-post-template<br />
# Title: Blog Post Template<br />
# Title Bar Caption: Blog Post Template<br />
<br />
=== Landing Page Template ===<br />
Navigate to the Landing Page template that was created from the installation. Rename the page to add "template" into the title for easy recognition. <br />
<br />
On the page, open the dialog "Actions > Rename Page..". Update the form fields with the following:<br />
# Name: template-Blog-Landing-Template<br />
# Title: Blog Landing Template<br />
# Title Bar Caption: Blog Landing Template<br />
<br />
== Blog Manager ==<br />
<br />
Navigate to the Blog Manager page. Edit each blog record to assign a value into the "notificationFrom" field. If no value is assigned, then the CommonSpot site administrator email will be used as the from address for notification emails.<br />
<br />
<br />
== Site Level Customizations Review ==<br />
This is only for reviewing the site level customizations in the "/_cs_apps/pt_blog/" directory, not in the ADF directory.<br />
<br />
# Analyze the updated app code compared to the app customization code on your server.<br />
## Identify any customizations that you have made to the application code to make sure these are updated with any functionality.<br />
## Again, Beyond Compare is a good tool to compare the new and current file to identify the exact lines of code that have been changed. <br />
## This is important for components that have customized functions to the site level "/_cs_apps/". The best practice is to identify the function that have been customized and compare with the new app function to identify any updates. A good help is to check the function comment header to see if any updates have been made.<br />
# Once completed, Reset the ADF.<br />
<br />
== Reset the ADF ==<br />
[[Reset ADF|Reset the ADF]] for the server and site.</div>Mcarrollhttp://community.paperthin.com/adf-docs/index.php?title=PT_Blog_Version_2.2_Install&diff=6334PT Blog Version 2.2 Install2013-02-27T17:00:06Z<p>Mcarroll: /* Landing Page Template */</p>
<hr />
<div>== Download ==<br />
Download the Blog Application from the [http://community.paperthin.com/projects/pt_blog/index.cfm Community Site Project] or from the SVN Repository. <br />
<br />
Extract the zip files into the following directory:<br />
'''/ADF/apps/pt_blog/''' <br />
<br />
== Site Configuration ==<br />
* Make sure the ADF is setup and running on the site. If the ADF is not setup, then follow the instructions for ADF [[Installation]].<br />
* Open the sites 'ADF.cfc' ([[Site Configuration (ADF.cfc) | See Site Configuration (ADF.cfc) for more info]]) file in a text editor. Locate the ''Load the ADF Application into application space'' comment in the file. Add the following command under the comment section:<br />
<source lang="java"><br />
loadApp("ptBlog2");<br />
</source><br />
* [[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
== Import Custom Elements ==<br />
Create a "PT Blog Elements" category and import all portions of each component in the order listed.<br />
<br />
'''Import Custom Element:'''<br />
<br />
# [[PT_Blog_Blog2_Fields_v2.2|Blog2]] (Blog2-Custom-Element.zip)<br />
# [[PT_Blog_Posts2_Fields_v2.2|Posts2]] (Posts2-Custom-Element.zip)<br />
# [[PT_Blog_Comments2_Fields_v2.2|Comments2]] (Comments2-Custom-Element.zip)<br />
# [[PT_Blog_Blog2_Feature_Data_Fields_v2.2|Blog2 Feature Data]] (Blog2-Feature-Data-Custom-Element.zip)<br />
# [[PT_Blog_PTBlog2_Configuration_Fields_v2.2|PTBlog2 Configuration]] (PTBlog2-Configuration-Custom-Element.zip)<br />
<br />
'''Import Metadata:'''<br />
<br />
# Blogs2 (Blogs2-Metadata-Form.zip)<br />
<br />
=== Verify Imports ===<br />
<br />
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. <br />
<br />
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/".<br />
<br />
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.<br />
<br />
== Subsites ==<br />
It is '''highly recommended''' this Blog Web Admin subsite for administrators and a Blog Lightbox subsite for the lightbox pages. This allows security to be setup for the subsite to allow only administrators access for the webadmin and the CS toolbar turned off for the lightbox pages.<br />
<br />
Your site may already have a ''webadmin'' and/or ''lightbox'' subsite. The steps below will add a ''blogs'' subsite into the ''webadmin'' and ''lightbox'' subsites.<br />
<br />
=== Web Admin ===<br />
# Create a new subsite under the site root called ''webadmin''.<br />
# Create a new subsite under ''webadmin'' called ''blogs''.<br />
# Configure the ''/webadmin/blogs/'' subsite Content Security to give 'No Rights' to 'Anonymous Users' and 'Authenticated Users'. <br />
# Configure the ''/webadmin/blogs/'' subsite Content Security to give permissions to the group of administrators who will manage the Blogs.<br />
<br />
=== Blogs ===<br />
The subsite for the blog pages must be created manually. This subsite is custom to your implementation and can be any subsite within the site. <br />
If you don't have a specific subsite then create a ''Blogs'' subsite under the site root.<br />
<br />
== Templates ==<br />
<br />
=== Blog Post Template ===<br />
The Blog Post Template is the template that all the blog post pages are created from.<br />
To construct your Blog Post Template complete the following steps. <br />
<br />
# Create a CommonSpot page called 'Blog Post Template' from the Base Plus One template. (The subsite for this is not critical but it is a good idea to create this page in a subsite that has been created for the Blogs.) <br />
# Place the ''Posts2'' 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 ''PostID'' field. <br />
### Select the operator as ''Equals''.<br />
### Click the '...' button to open the ColdFusion expression window.<br />
### Enter the text ''request.page.metadata.blogs2.postID'' 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 />
### Ignore the error message for 'Error: Error evaluating a user-defined expresssion'.<br />
# Click ''More'' in the element interface. Then the ''Custom Render Handlers'' menu option, and choose the ''Main Display'' Render Handler. (You may see an error on this page with the Render Handler. That is OK at this point.)<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 ''Blogs2'' metadata form to this new ''Blog Post Template''.<br />
<br />
=== Landing Page Template ===<br />
# Create a CommonSpot page called 'Blog Landing Template' from the Base Plus One template. (The subsite for this is not critical but it is a good idea to create this page in a subsite that has been created for the Blogs.) <br />
# Add the "Posts2" custom element to the page.<br />
# Set the render mode for the following:<br />
## Rendering Mode: "Display existing element data (content reuse)" and "Render results dynamically based on a filter, or display all records.".<br />
## Filter:<br />
### Filter: Subset of records<br />
### Post2.blogID Equals {request.page.metadata.blogs2.blogID} (this is a ColdFusion expression)<br />
#### Make sure to check "Force Cache".<br />
#### Sort Order: "Date Posted" and "Descending"<br />
### Save Render Mode<br />
##Ignore the error message for "Error evaluating a user-defined expresssion".<br />
# Change the custom render handler to "Home Page Display".<br />
# Publish the page.<br />
# Save the page as a template and submit the template for public use.<br />
# Go to the Site Administrator and metadata forms. Add a new binding for the "Blogs2" form to the "Blog Landing" template.<br />
<br />
== CCAPI Configuration ==<br />
The Blog Application uses the [[CCAPI|ADF CCAPI]] to populate blog post records. This needs to be configured for the site and blog 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 Blog App. Make sure to update the ''wsVars'' section with the correct URL's and username/password.<br />
<br />
# Create a new page called 'ccapi' under the root subsite and from the base plus one template. When creating the page, disable the standard metadata 'Include In' fields for 'Page Indexes' and 'Full Text and Search Element Results'. This page may already exist within your site, if it does, then continue to the next steps.<br />
# Add the 'Posts2' element to the page.<br />
## Select the 'Posts2' element indicator and go to 'more...'. Select 'Name' from the menu.<br />
## In the Element Name field, enter the text 'ccapiPosts2Element'.<br />
# Add the 'Comments2' element to the page.<br />
## Select the 'Comments2' element indicator and go to 'more...'. Select 'Name' from the menu.<br />
## In the Element Name field, enter the text 'ccapiComments2Element'.<br />
# Add the 'Blog2 Feature Data' element to the page.<br />
## Select the 'Blog2 Feature Data' element indicator and go to 'more...'. Select 'Name' from the menu.<br />
## In the Element Name field, enter the text 'ccapiBlog2FeatureData'.<br />
# Add the 'Blog2' element to the page.<br />
## Select the 'Blog2' element indicator and go to 'more...'. Select 'Name' from the menu.<br />
## In the Element Name field, enter the text 'ccapiBlog2'.<br />
# Publish this page and put in read mode.<br />
# Edit the 'ccapi.cfm' file (it may be ccapi.xml) for the site and add the following xml block into the <elements> section:<br />
<source lang="xml"><br />
<BlogPost><br />
<pageID>#####</pageID><br />
<subsiteID>##</subsiteID><br />
<elementType>custom</elementType><br />
<controlName>ccapiPosts2Element</controlName><br />
</BlogPost><br />
<Comments><br />
<pageID>#####</pageID><br />
<subsiteID>##</subsiteID><br />
<elementType>custom</elementType><br />
<controlName>ccapiComments2Element</controlName><br />
</Comments><br />
<BlogFeatureData><br />
<pageID>#####</pageID><br />
<subsiteID>##</subsiteID><br />
<elementType>custom</elementType><br />
<controlName>ccapiBlog2FeatureData</controlName><br />
</BlogFeatureData><br />
<Blog><br />
<pageID>#####</pageID><br />
<subsiteID>##</subsiteID><br />
<elementType>custom</elementType><br />
<controlName>ccapiBlog2</controlName><br />
</Blog><br />
</source><br />
<br />
# To populate the <pageID> and <subsiteID> tags, view the source code for the 'ccapiBlog' page that was just created. <br />
# Identify the following line in the source code and enter this numeric value into the <subsiteID> tag:<br />
<source lang="java"><br />
var jsSubSiteID = ##;<br />
</source><br />
# Identify the following line in the source code and enter this numeric value into the <pageID> tag:<br />
<source lang="java"><br />
var jsPageID = ####;<br />
</source><br />
<br />
[[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
== Proxywhitelist Updates ==<br />
A security feature within the ADF prevents unauthorized methods from being called. The Blog Application requires certain methods to be authorized by updating the proxyWhiteList.xml file located within your site's _cs_apps/config directory. If there is no proxyWhiteList.xml file located within that directory, you may copy the file from /ADF/apps/pt_blog/components into the _cs_apps/config directory and then reset the ADF. If there is already a proxyWhiteList.xml file located in your config directory, then add the following lines to it:<br />
<source lang="java"><br />
<blogForms>renderPostForm,renderDeleteForm,renderBlogForm,renderBlogDeleteForm</blogForms><br />
<commentsService>handleCommentsSubmit,getDashboardData</commentsService><br />
<PostService>syncPost,createPostPage</PostService><br />
<blogService>handleBlogUpdate</blogService><br />
<blogsUserGroupsGC>controller</blogsUserGroupsGC><br />
</source> <br />
<br />
The above must be placed between the beginning and ending SETTINGS tags. After adding the above lines, reset the ADF.<br />
<br />
== Create Blog Management Page ==<br />
This page will be used to manage the blogs for the site. <br />
<br />
# Create page from the Base Plus One template called "Blog Manager" in the ''/webadmin/blogs/'' subsite.<br />
# Place Custom Script on the page<br />
# Select the "/ADF/apps/pt_blog/customcf/all_blogs_manager.cfm" script.<br />
# Define a View for the Datasheet Element for this page - call it "All Blogs"<br />
# Leave the View Source as the Default: Form Result/Custom Element Sheet<br />
# Select the "Blog2" Custom Element and select the following columns: blogID, Name, SubsiteURL, DateCreated, and Active.<br />
# Edit the datasheet columns.<br />
## Edit the blogID column, change the render handler to: <br />
### /ADF/apps/pt_blog/datasheet-modules/blog_edit_delete.cfm''<br />
### Change the header text to "Edit/Delete".<br />
# Edit the datasheet layout<br />
## Set default sorting to "Name" field.<br />
## Set Results Per Page to "50".<br />
## Uncheck "Show Alphabet Characters for Filtering"<br />
## Uncheck "Allow JavaScript data sorting"<br />
# Publish the Blogs Management page.<br />
<br />
== Create Blog Configuration Record ==<br />
We are creating a single Blog Configuration element record to be used within the application. <br />
<br />
Go to the Blogs Management Page and select the ''Edit App Configuration'' link. In the form, select the CommonSpot pages that were created in the previous steps. <br />
<br />
[[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
== Create Blog Dashboard Page==<br />
This page will be used to manage the blog post and comments for each blog. Each Blog will share this Dashboard Page.<br />
# Create page from the Base Plus One template called "Blog Dashboard" in the ''/webadmin/blogs/'' subsite.<br />
# Place Custom Script on the page<br />
# Enter the explicit path for the following custom script:<br />
## /ADF/apps/pt_blog/customcf/blog_dashboard.cfm<br />
# Define a View for the Datasheet Element called "All Blog Posts"<br />
## Leave the View Source as the Default: Form Result/Custom Element Sheet<br />
## Select the "Posts2" Custom Element and select the following columns: PostID, PostPageID, Title, Created By, and Date Posted.<br />
## On the Datasheet, click on the "Filter" and apply the following filter: Field = BlogID; Operator = "equals"; Value = "request.params.blogID" (note: use the UDE button)<br />
# Edit the datasheet columns.<br />
## Edit the PostID column, change the render handler to:<br />
### /ADF/apps/pt_blog/datasheet-modules/lightbox_edit_delete_post.cfm<br />
### Change the header text to "Edit/Delete/Comments".<br />
## Edit the PostPageID column, change the render handler to: <br />
### /ADF/apps/pt_blog/datasheet-modules/post_page_url.cfm<br />
### Change the header text to "View Post Page".<br />
## Edit the CreatedBy column, change the render handler to:<br />
### /ADF/extensions/datasheet-modules/1.0/userID-to-name.cfm<br />
## Edit the DatePosted column, make the following settings:<br />
### Format Mask: Date/Time<br />
### Date/Time Format: 07/24/00<br />
# Edit the datasheet layout<br />
## Set default sorting to "Title" field.<br />
## Set Results Per Page to "50".<br />
## Uncheck "Show Alphabet Characters for Filtering"<br />
## Uncheck "Allow JavaScript data sorting"<br />
## Click "Save"<br />
# Submit and publish the page.<br />
<br />
== Create Blog Feature Data Management Page ==<br />
This page will be used to manage the blog feature data records for the site.<br />
<br />
# Create page from the Base Plus One template called "Blog Feature Data" in the ''/webadmin/blogs/'' subsite.<br />
# Add a Datasheet element into the page.<br />
## Define a View for the Datasheet Element called "Blog Feature Data"<br />
## Leave the View Source as the Default: Form Result/Custom Element Sheet<br />
## Select the "Blog2 Feature Data" Custom Element and select the following columns: BlogID, FeatureType, FeatureCSPageID, and Last Date Modified.<br />
# Add a new action column for "delete".<br />
# Publish the page.<br />
<br />
== Update Blog Configuration Record ==<br />
Go to the Blogs Management Page and select the ''Edit App Configuration'' link. In the form, select the CommonSpot pages that were created in the previous steps. <br />
<br />
[[Reset ADF|Reset the ADF]] for the server and site.<br />
[[Category:Blogs]]</div>Mcarroll