http://community.paperthin.com/adf-docs/api.php?action=feedcontributions&user=Dbeckstrom&feedformat=atomADF Docs - User contributions [en]2024-03-28T23:12:22ZUser contributionsMediaWiki 1.29.0http://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation_Upgrade_v3.0&diff=6975OHSU Navigation Upgrade v3.02015-11-18T23:03:03Z<p>Dbeckstrom: Created page with "== Site Configuration == Copy the version 3 OHSUNav files into the /ADF/apps/ohsu_nav/ directory and overwrite the existing files. The application uses the new CommonSpot 10 ..."</p>
<hr />
<div>== Site Configuration ==<br />
Copy the version 3 OHSUNav files into the /ADF/apps/ohsu_nav/ directory and overwrite the existing files.<br />
<br />
The application uses the new CommonSpot 10 resource loading. Go to Site Admin > Resources/Libraries and open the Registered Resources/Libraries dialog. Click on the Secondary tab and on the bottom of the dialog select the "Add Resource/Library" link. For the Resource Name enter: OHSUNavCSS Leave the Resource Category radio button set to Secondary. For the description enter: "Loads the OHSUNav Interface Style Sheet". Then click on the "Resource URLS" tab and on the top of the dialog where it says "Early Loading" enter URL: "/ADF/apps/ohsu_nav/style/interface.css" leave the type set to "Stylesheet" and then hit the "Add" button. At the bottom of this dialog select the "Save" button. <br />
<br />
The custom field has been upgraded for CommonSpot 10. Go to Site Admin > Elements & Forms and select the Field Types and Masks option from the left menu. Scroll down until you find the Navigation custom field. Click on the pencil icon to the right of the field name and select "edit" from the pop-up menu. Click on the Render Component tab and for the Explicit Render Component Path enter URL: /ADF/apps/ohsu_nav/customfields/nav_element_render.cfc<br />
<br />
Reset the ADF.</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation&diff=6974OHSU Navigation2015-11-18T22:59:44Z<p>Dbeckstrom: /* 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 v3.0:<br />
* [[OHSU_Navigation_Release_Notes_v3.0|Release Notes]]<br />
* [[OHSU_Navigation_Install_v3.0|Install Guide]]<br />
* [[OHSU_Navigation_Upgrade_v3.0|Upgrade Guide]]<br />
<br />
Previous Releases:<br />
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 />
* 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>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation_Install_v3.0&diff=6973OHSU Navigation Install v3.02015-11-18T22:58:51Z<p>Dbeckstrom: /* Site Configuration */</p>
<hr />
<div>Please follow the [[OHSU_Navigation_Install_v2.0|OHSU Navigation Install Guide v2.0]] steps. <br />
<br />
Once completed with the v2.0 install guide, please add the next steps to the installation.<br />
<br />
== Site Configuration ==<br />
Copy the version 3 OHSUNav files into the /ADF/apps/ohsu_nav/ directory and overwrite the existing files.<br />
<br />
The application uses the new CommonSpot 10 resource loading. Go to Site Admin > Resources/Libraries and open the Registered Resources/Libraries dialog. Click on the Secondary tab and on the bottom of the dialog select the "Add Resource/Library" link. For the Resource Name enter: OHSUNavCSS Leave the Resource Category radio button set to Secondary. For the description enter: "Loads the OHSUNav Interface Style Sheet". Then click on the "Resource URLS" tab and on the top of the dialog where it says "Early Loading" enter URL: "/ADF/apps/ohsu_nav/style/interface.css" leave the type set to "Stylesheet" and then hit the "Add" button. At the bottom of this dialog select the "Save" button. <br />
<br />
Before using the App, don't forget to reset the ADF.<br />
<br />
== Reset the ADF ==<br />
[[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
[[Category:OHSU Navigation]]</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation_Install_v3.0&diff=6972OHSU Navigation Install v3.02015-11-18T22:55:58Z<p>Dbeckstrom: Created page with "Please follow the OHSU Navigation Install Guide v2.0 steps. Once completed with the v2.0 install guide, please add the next steps to the in..."</p>
<hr />
<div>Please follow the [[OHSU_Navigation_Install_v2.0|OHSU Navigation Install Guide v2.0]] steps. <br />
<br />
Once completed with the v2.0 install guide, please add the next steps to the installation.<br />
<br />
== Site Configuration ==<br />
The application uses the new CommonSpot 10 resource loading. Go to Site Admin > Resources/Libraries and open the Registered Resources/Libraries dialog. Click on the Secondary tab and on the bottom of the dialog select the "Add Resource/Library" link. For the Resource Name enter: OHSUNavCSS Leave the Resource Category radio button set to Secondary. For the description enter: "Loads the OHSUNav Interface Style Sheet". Then click on the "Resource URLS" tab and on the top of the dialog where it says "Early Loading" enter URL: "/ADF/apps/ohsu_nav/style/interface.css" leave the type set to "Stylesheet" and then hit the "Add" button. At the bottom of this dialog select the "Save" button. <br />
<br />
The fields for the configuration fields are defined below.<br />
<br />
To allow each site to have its own configuration:<br />
* Locate the ''/_cs_apps'' directory in your site. If a ''/_cs_apps/config/'' directory does not exists, then create the directory.<br />
* Place a file in this directory called "ohsuNav.xml". This file can be found in the ''/ohsu_nav/site-files/_cs_apps/config/ohsuNav.xml''.<br />
* Verify the tag field data with the descriptions of the tags below.<br />
<br />
=== XML Tags ===<br />
The following are the tags of the OHSU Nav XML Config file:<br />
# '''registeredURLs''' - Registered URL settings.<br />
## '''openInNewWindow''' - Open Registered URLS in a new window (or tab) - adds: target="_blank" to the link.<br />
## '''excludedDomains''' - Comma delimited list of domains to exclude from the openInNewWindow config option.<br />
<br />
== Reset the ADF ==<br />
[[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
[[Category:OHSU Navigation]]</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation&diff=6971OHSU Navigation2015-11-18T22:47:58Z<p>Dbeckstrom: /* 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 v3.0:<br />
* [[OHSU_Navigation_Release_Notes_v3.0|Release Notes]]<br />
* [[OHSU_Navigation_Install_v3.0|Install Guide]]<br />
* [[OHSU_Navigation_Upgrade_v2.0|Upgrade Guide]]<br />
<br />
Previous Releases:<br />
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 />
* 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>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation_Install_v2.0&diff=6970OHSU Navigation Install v2.02015-11-18T22:47:14Z<p>Dbeckstrom: </p>
<hr />
<div>Please follow the [[OHSU_Navigation_Install_v2.0|OHSU Navigation Install Guide v2.0]] steps. <br />
<br />
Once completed with the v1.0 install guide, please add the next steps to the installation.<br />
<br />
== Site Configuration ==<br />
The application uses an XML file to manage the site specific configurations. <br />
<br />
The fields for the configuration fields are defined below.<br />
<br />
To allow each site to have its own configuration:<br />
* Locate the ''/_cs_apps'' directory in your site. If a ''/_cs_apps/config/'' directory does not exists, then create the directory.<br />
* Place a file in this directory called "ohsuNav.xml". This file can be found in the ''/ohsu_nav/site-files/_cs_apps/config/ohsuNav.xml''.<br />
* Verify the tag field data with the descriptions of the tags below.<br />
<br />
=== XML Tags ===<br />
The following are the tags of the OHSU Nav XML Config file:<br />
# '''registeredURLs''' - Registered URL settings.<br />
## '''openInNewWindow''' - Open Registered URLS in a new window (or tab) - adds: target="_blank" to the link.<br />
## '''excludedDomains''' - Comma delimited list of domains to exclude from the openInNewWindow config option.<br />
<br />
== Reset the ADF ==<br />
[[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
[[Category:OHSU Navigation]]</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation_Release_Notes_v3.0&diff=6969OHSU Navigation Release Notes v3.02015-11-18T22:44:40Z<p>Dbeckstrom: /* Overview */</p>
<hr />
<div>=== Overview ===<br />
OHSUNav will be deprecated and no longer supported. Instead, customers should use the new Tree Element introduced with CommonSpot 9. However, this version of OHSUNav was made available to ease the customer migration effort when upgrading from CommonSpot 9 to CommonSpot 10. <br />
<br />
This version will enable OHSUNav to continue working with CommonSpot 10 thus allowing customers time to migrate to the Tree element later.<br />
<br />
=== Enhancements ===<br />
* Updated the App Bean Config to support ADF v2.0.<br />
* Converted the custom field to a cfc to be compatible with CommonSpot 10.<br />
* Updated the style sheet to properly render the metadata form.</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation_Release_Notes_v3.0&diff=6968OHSU Navigation Release Notes v3.02015-11-18T22:43:41Z<p>Dbeckstrom: /* Overview */</p>
<hr />
<div>=== Overview ===<br />
OHSUNav will be deprecated and no longer supported. Instead, customers should use the new Tree Element introduced with CommonSpot 9. However, this version of OHSUNav was made available to ease customer migration effort from CommonSpot 9 to CommonSpot 10. This version will enable OHSUNav to continue working with CommonSpot 10 thus allowing customers time to migrate to the Tree element later.<br />
<br />
=== Enhancements ===<br />
* Updated the App Bean Config to support ADF v2.0.<br />
* Converted the custom field to a cfc to be compatible with CommonSpot 10.<br />
* Updated the style sheet to properly render the metadata form.</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation_Release_Notes_v3.0&diff=6967OHSU Navigation Release Notes v3.02015-11-18T22:43:27Z<p>Dbeckstrom: /* Enhancements */</p>
<hr />
<div>=== Overview ===<br />
* OHSUNav will be deprecated and no longer supported. Instead, customers should use the new Tree Element introduced with CommonSpot 9. However, this version of OHSUNav was made available to ease customer migration effort from CommonSpot 9 to CommonSpot 10. This version will enable OHSUNav to continue working with CommonSpot 10 thus allowing customers time to migrate to the Tree element later.<br />
=== Enhancements ===<br />
* Updated the App Bean Config to support ADF v2.0.<br />
* Converted the custom field to a cfc to be compatible with CommonSpot 10.<br />
* Updated the style sheet to properly render the metadata form.</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation_Release_Notes_v3.0&diff=6966OHSU Navigation Release Notes v3.02015-11-18T22:40:35Z<p>Dbeckstrom: Created page with "=== Enhancements === * Updated the App Bean Config to support ADF v2.0. * Converted the custom field to a cfc to be compatible with CommonSpot 10. * Updated the style sheet to..."</p>
<hr />
<div>=== Enhancements ===<br />
* Updated the App Bean Config to support ADF v2.0.<br />
* Converted the custom field to a cfc to be compatible with CommonSpot 10.<br />
* Updated the style sheet to properly render the metadata form.</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation&diff=6965OHSU Navigation2015-11-18T22:38:22Z<p>Dbeckstrom: /* 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 v3.0:<br />
* [[OHSU_Navigation_Release_Notes_v3.0|Release Notes]]<br />
* [[OHSU_Navigation_Install_v2.0|Install Guide]]<br />
* [[OHSU_Navigation_Upgrade_v2.0|Upgrade Guide]]<br />
<br />
Previous Releases:<br />
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 />
* 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>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=OHSU_Navigation&diff=6964OHSU Navigation2015-11-18T22:36:38Z<p>Dbeckstrom: /* 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 v3.0:<br />
* [[OHSU_Navigation_Install_v2.0|Install Guide]]<br />
* [[OHSU_Navigation_Upgrade_v2.0|Upgrade Guide]]<br />
<br />
Previous Releases:<br />
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 />
* 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>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments_Install_v2.1&diff=6510PT Comments Install v2.12013-04-01T18:59:50Z<p>Dbeckstrom: /* Overview */</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.0.<br />
<br />
For v2.0, 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>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments_Install_v2.1&diff=6509PT Comments Install v2.12013-04-01T18:59:13Z<p>Dbeckstrom: /* Overview */</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.0.<br />
<br />
For v2.0, 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 this 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>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments_Install_v2.1&diff=6508PT Comments Install v2.12013-04-01T18:58:45Z<p>Dbeckstrom: /* Overview */</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.0.<br />
<br />
For v2.0, 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 this 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>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments_Install_v2.1&diff=6507PT Comments Install v2.12013-04-01T18:58:13Z<p>Dbeckstrom: /* Overview */</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.0.<br />
<br />
For v2.0, 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 this 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>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments_Install_v2.1&diff=6506PT Comments Install v2.12013-04-01T18:57:00Z<p>Dbeckstrom: /* Overview */</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.0.<br />
<br />
For v2.0, 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 this 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>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments_Install_v2.1&diff=6505PT Comments Install v2.12013-04-01T18:48:11Z<p>Dbeckstrom: Created page with '== Overview == This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.0. For v2.0, the primary change that occurred was a bug…'</p>
<hr />
<div>== Overview ==<br />
This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.0.<br />
<br />
For v2.0, 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></div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments&diff=6504PT Comments2013-04-01T18:30:25Z<p>Dbeckstrom: /* 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.0:<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>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments&diff=6503PT Comments2013-04-01T18:30:08Z<p>Dbeckstrom: /* 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.0:<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>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments_Install_v1&diff=6502PT Comments Install v12013-04-01T18:21:56Z<p>Dbeckstrom: /* Adding comments to your page */</p>
<hr />
<div>== Download ==<br />
Download the Comments Application from the Community Site or from the [http://community.paperthin.com/svn/pt_comments/trunk/ SVN Repository]. <br />
<br />
Extract the zip files into the following directory:<br />
'''/ADF/apps/pt_comments/''' <br />
<br />
== ADF 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 (located in your site's /_cs_apps/ directory) in a text editor. Locate the ''Load the ADF Application into application space'' comment in the file. Add (or uncomment) the following command under the comment section:<br />
<source lang="java"><br />
loadApp("ptComments");<br />
</source><br />
* [[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
== Import Elements ==<br />
The Comments Application has a single Global Custom Element defined within CommonSpot. The element has been exported and is available in the Comments's "exported-objects" folder located at the root of the Comments application directory (e.g. /ADF/apps/pt_comments/exported-objects/)<br />
<br />
Optional: You may want to create a new category within the CommonSpot Element Gallery for 'Comments Elements'.<br />
<br />
To import these objects, you will need to be an administrator for your site. If you are not a site administrator, consult your Server administrator for more information.<br />
<br />
=== Import ===<br />
<br />
Import the Custom Element: <br />
<br />
# Comments (Comments-Custom-Element.zip)<br />
<br />
=== Verify Import ===<br />
<br />
The render handler path for the imported "comments" element must be verified that it has the correct path. During the import process, the render handler path may have been changed to reflect the current site's path. <br />
<br />
Review and update the path to reference the ADF path. In most cases, this will just require the element to be unlocked and a change in the path from the site name to 'ADF'. Check the path for the [[PT_Comments#Contents|custom field types that were imported]] with the custom element by unlocking it and fixing the explicit path to point to "/ADF/extensions/".<br />
<br />
== Subsites ==<br />
It is '''highly recommended''' that a Comments subsite is created for administrators. This allows security to be setup for the subsite to allow only administrators access for the webadmin.<br />
<br />
Your site may already have a ''webadmin'' subsite. The steps below will add a ''comments'' subsite into the ''webadmin'' subsite.<br />
<br />
=== Web Admin ===<br />
# Create a new subsite under the site root called ''webadmin''.<br />
# Create a new subsite under ''webadmin'' called ''comments''.<br />
# Configure the ''/webadmin/comments/'' subsite Content Security to give 'No Rights' to 'Anonymous Users' and 'Authenticated Users'. <br />
# Configure the ''/webadmin/comments/'' subsite Content Security to give permissions to the group of administrators who will manage the Comments.<br />
<br />
== Comments Manager ==<br />
This page will be used to manage the Comments custom element data records for the site.<br />
<br />
# Create page with the name "index" and title is "Comments Manager" in the ''/webadmin/comments/'' subsite.<br />
# Add a Datasheet element into the page.<br />
## Define a View for the Datasheet Element called "All Comments"<br />
## Leave the View Source as the Default: Form Result/Custom Element Sheet<br />
## Select the "Comments" Custom Element and select the following columns: <br />
### UID, DateTimePosted, and Name<br />
## Edit the column for the "UID" field and make the following changes:<br />
### Header: Edit/Delete<br />
### Render Handler: /ADF/extensions/datasheet-modules/1.0/edit-delete.cfm<br />
## Edit the Layout properties for the datasheet:<br />
### Default Sorting: DateTimePosted DESCENDING<br />
### Results Per Page: 50<br />
### Allow JavaScript data sorting: Uncheck<br />
# Publish the page.<br />
<br />
== Site Configuration ==<br />
<br />
=== Installing cfformprotect ===<br />
CF Form Protect helps to protect your form from spam. It allows the comments that users enter to have some verification of who is entering the data and makes sure that robots do not submit bogus comments.<br />
<br />
# Copy cffp.ini.cfm from /ADF/thirdParty/cfformprotect/ into your /_cs_apps/config directory<br />
# Edit the parameters as you see fit. Please note the email settings.<br />
<br />
=== Adding comments to your page ===<br />
The comments element, which will be configured in a step below, requires a variable called "request.comments.contentDataPageID". This variable does not exist and will throw an error unless one of two things are done. First, you can add a script to the page directly above where you place the comments element. The script (pageComments.cfm) will define the variable needed by the comments element.<br />
<br />
Alternatively, you can add the following line of code:<br />
<br />
<cfset request.comments.contentDataPageID = request.page.id><br />
<br />
to a template-basepage.head file in the site's /templates directory. If you add the line of code to your template-basepage.head file, then it is not necessary to place a custom script element on every page where you wish to use comments. Adding this code to your template-basepage.head is the preferred installation method. If your site does not have a template-basepage.head file, you may create one. The Commonspot developer's guide explains the requirements for creating the .head file.<br />
<br />
# Edit your page<br />
# '''Optional''' -- Add a custom script to your page<br />
#* /ADF/apps/pt_comments/customcf/pageComments.cfm<br />
# Add the comments element to your page<br />
# Update the render mode on this 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 />
## enter: request.comments.contentDataPageID<br />
## Sort Order: dateTimePosted ASCENDING<br />
## click save<br />
# submit your page<br />
<br />
<br />
* [[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
[[Category:Comments]]</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments_Install_v1&diff=6501PT Comments Install v12013-04-01T18:21:26Z<p>Dbeckstrom: /* Adding comments to your page */</p>
<hr />
<div>== Download ==<br />
Download the Comments Application from the Community Site or from the [http://community.paperthin.com/svn/pt_comments/trunk/ SVN Repository]. <br />
<br />
Extract the zip files into the following directory:<br />
'''/ADF/apps/pt_comments/''' <br />
<br />
== ADF 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 (located in your site's /_cs_apps/ directory) in a text editor. Locate the ''Load the ADF Application into application space'' comment in the file. Add (or uncomment) the following command under the comment section:<br />
<source lang="java"><br />
loadApp("ptComments");<br />
</source><br />
* [[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
== Import Elements ==<br />
The Comments Application has a single Global Custom Element defined within CommonSpot. The element has been exported and is available in the Comments's "exported-objects" folder located at the root of the Comments application directory (e.g. /ADF/apps/pt_comments/exported-objects/)<br />
<br />
Optional: You may want to create a new category within the CommonSpot Element Gallery for 'Comments Elements'.<br />
<br />
To import these objects, you will need to be an administrator for your site. If you are not a site administrator, consult your Server administrator for more information.<br />
<br />
=== Import ===<br />
<br />
Import the Custom Element: <br />
<br />
# Comments (Comments-Custom-Element.zip)<br />
<br />
=== Verify Import ===<br />
<br />
The render handler path for the imported "comments" element must be verified that it has the correct path. During the import process, the render handler path may have been changed to reflect the current site's path. <br />
<br />
Review and update the path to reference the ADF path. In most cases, this will just require the element to be unlocked and a change in the path from the site name to 'ADF'. Check the path for the [[PT_Comments#Contents|custom field types that were imported]] with the custom element by unlocking it and fixing the explicit path to point to "/ADF/extensions/".<br />
<br />
== Subsites ==<br />
It is '''highly recommended''' that a Comments subsite is created for administrators. This allows security to be setup for the subsite to allow only administrators access for the webadmin.<br />
<br />
Your site may already have a ''webadmin'' subsite. The steps below will add a ''comments'' subsite into the ''webadmin'' subsite.<br />
<br />
=== Web Admin ===<br />
# Create a new subsite under the site root called ''webadmin''.<br />
# Create a new subsite under ''webadmin'' called ''comments''.<br />
# Configure the ''/webadmin/comments/'' subsite Content Security to give 'No Rights' to 'Anonymous Users' and 'Authenticated Users'. <br />
# Configure the ''/webadmin/comments/'' subsite Content Security to give permissions to the group of administrators who will manage the Comments.<br />
<br />
== Comments Manager ==<br />
This page will be used to manage the Comments custom element data records for the site.<br />
<br />
# Create page with the name "index" and title is "Comments Manager" in the ''/webadmin/comments/'' subsite.<br />
# Add a Datasheet element into the page.<br />
## Define a View for the Datasheet Element called "All Comments"<br />
## Leave the View Source as the Default: Form Result/Custom Element Sheet<br />
## Select the "Comments" Custom Element and select the following columns: <br />
### UID, DateTimePosted, and Name<br />
## Edit the column for the "UID" field and make the following changes:<br />
### Header: Edit/Delete<br />
### Render Handler: /ADF/extensions/datasheet-modules/1.0/edit-delete.cfm<br />
## Edit the Layout properties for the datasheet:<br />
### Default Sorting: DateTimePosted DESCENDING<br />
### Results Per Page: 50<br />
### Allow JavaScript data sorting: Uncheck<br />
# Publish the page.<br />
<br />
== Site Configuration ==<br />
<br />
=== Installing cfformprotect ===<br />
CF Form Protect helps to protect your form from spam. It allows the comments that users enter to have some verification of who is entering the data and makes sure that robots do not submit bogus comments.<br />
<br />
# Copy cffp.ini.cfm from /ADF/thirdParty/cfformprotect/ into your /_cs_apps/config directory<br />
# Edit the parameters as you see fit. Please note the email settings.<br />
<br />
=== Adding comments to your page ===<br />
The comments element, which will be configured in a step below, requires a variable called "request.comments.contentDataPageID". This variable does not exist and will throw an error unless one of two things are done. First, you can add a script to the page directly above where you place the comments element. The script (pageComments.cfm) will define the variable needed by the comments element.<br />
<br />
Alternatively, you can add the following line of code:<br />
<br />
<cfset request.comments.contentDataPageID = request.page.id><br />
<br />
to a template-basepage.head file in the site's /templates directory. If you add the line of code to your template-basepage.head file, then it is not necessary to place a custom script element on every page where you wish to use comments. Adding this code to your template-basepage.head is the preferred installation method. If your site does not have a template-basepage.head file, you may create one. The Commonspot developer's guide explains the requirements for creating the .head file.<br />
<br />
# Edit your page<br />
# '''Optional''' -- Add a custom script to your page<br />
#* /ADF/apps/pt_comments/customcf/pageComments.cfm<br />
# Add the comments element to your page<br />
# Update the render mode on this 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 />
## enter: request.params.comments.contentDataPageID<br />
## Sort Order: dateTimePosted ASCENDING<br />
## click save<br />
# submit your page<br />
<br />
<br />
* [[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
[[Category:Comments]]</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Comments_Install_v1&diff=6500PT Comments Install v12013-04-01T18:20:55Z<p>Dbeckstrom: /* Adding comments to your page */</p>
<hr />
<div>== Download ==<br />
Download the Comments Application from the Community Site or from the [http://community.paperthin.com/svn/pt_comments/trunk/ SVN Repository]. <br />
<br />
Extract the zip files into the following directory:<br />
'''/ADF/apps/pt_comments/''' <br />
<br />
== ADF 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 (located in your site's /_cs_apps/ directory) in a text editor. Locate the ''Load the ADF Application into application space'' comment in the file. Add (or uncomment) the following command under the comment section:<br />
<source lang="java"><br />
loadApp("ptComments");<br />
</source><br />
* [[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
== Import Elements ==<br />
The Comments Application has a single Global Custom Element defined within CommonSpot. The element has been exported and is available in the Comments's "exported-objects" folder located at the root of the Comments application directory (e.g. /ADF/apps/pt_comments/exported-objects/)<br />
<br />
Optional: You may want to create a new category within the CommonSpot Element Gallery for 'Comments Elements'.<br />
<br />
To import these objects, you will need to be an administrator for your site. If you are not a site administrator, consult your Server administrator for more information.<br />
<br />
=== Import ===<br />
<br />
Import the Custom Element: <br />
<br />
# Comments (Comments-Custom-Element.zip)<br />
<br />
=== Verify Import ===<br />
<br />
The render handler path for the imported "comments" element must be verified that it has the correct path. During the import process, the render handler path may have been changed to reflect the current site's path. <br />
<br />
Review and update the path to reference the ADF path. In most cases, this will just require the element to be unlocked and a change in the path from the site name to 'ADF'. Check the path for the [[PT_Comments#Contents|custom field types that were imported]] with the custom element by unlocking it and fixing the explicit path to point to "/ADF/extensions/".<br />
<br />
== Subsites ==<br />
It is '''highly recommended''' that a Comments subsite is created for administrators. This allows security to be setup for the subsite to allow only administrators access for the webadmin.<br />
<br />
Your site may already have a ''webadmin'' subsite. The steps below will add a ''comments'' subsite into the ''webadmin'' subsite.<br />
<br />
=== Web Admin ===<br />
# Create a new subsite under the site root called ''webadmin''.<br />
# Create a new subsite under ''webadmin'' called ''comments''.<br />
# Configure the ''/webadmin/comments/'' subsite Content Security to give 'No Rights' to 'Anonymous Users' and 'Authenticated Users'. <br />
# Configure the ''/webadmin/comments/'' subsite Content Security to give permissions to the group of administrators who will manage the Comments.<br />
<br />
== Comments Manager ==<br />
This page will be used to manage the Comments custom element data records for the site.<br />
<br />
# Create page with the name "index" and title is "Comments Manager" in the ''/webadmin/comments/'' subsite.<br />
# Add a Datasheet element into the page.<br />
## Define a View for the Datasheet Element called "All Comments"<br />
## Leave the View Source as the Default: Form Result/Custom Element Sheet<br />
## Select the "Comments" Custom Element and select the following columns: <br />
### UID, DateTimePosted, and Name<br />
## Edit the column for the "UID" field and make the following changes:<br />
### Header: Edit/Delete<br />
### Render Handler: /ADF/extensions/datasheet-modules/1.0/edit-delete.cfm<br />
## Edit the Layout properties for the datasheet:<br />
### Default Sorting: DateTimePosted DESCENDING<br />
### Results Per Page: 50<br />
### Allow JavaScript data sorting: Uncheck<br />
# Publish the page.<br />
<br />
== Site Configuration ==<br />
<br />
=== Installing cfformprotect ===<br />
CF Form Protect helps to protect your form from spam. It allows the comments that users enter to have some verification of who is entering the data and makes sure that robots do not submit bogus comments.<br />
<br />
# Copy cffp.ini.cfm from /ADF/thirdParty/cfformprotect/ into your /_cs_apps/config directory<br />
# Edit the parameters as you see fit. Please note the email settings.<br />
<br />
=== Adding comments to your page ===<br />
The comments element, which will be configured in a step below, requires a variable called "request.params.comments.contentDataPageID". This variable does not exist and will throw an error unless one of two things are done. First, you can add a script to the page directly above where you place the comments element. The script (pageComments.cfm) will define the variable needed by the comments element.<br />
<br />
Alternatively, you can add the following line of code:<br />
<br />
<cfset request.comments.contentDataPageID = request.page.id><br />
<br />
to a template-basepage.head file in the site's /templates directory. If you add the line of code to your template-basepage.head file, then it is not necessary to place a custom script element on every page where you wish to use comments. Adding this code to your template-basepage.head is the preferred installation method. If your site does not have a template-basepage.head file, you may create one. The Commonspot developer's guide explains the requirements for creating the .head file.<br />
<br />
# Edit your page<br />
# '''Optional''' -- Add a custom script to your page<br />
#* /ADF/apps/pt_comments/customcf/pageComments.cfm<br />
# Add the comments element to your page<br />
# Update the render mode on this 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 />
## enter: request.params.comments.contentDataPageID<br />
## Sort Order: dateTimePosted ASCENDING<br />
## click save<br />
# submit your page<br />
<br />
<br />
* [[Reset ADF|Reset the ADF]] for the server and site.<br />
<br />
[[Category:Comments]]</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Install_v2.0&diff=6463PT Multimedia Install v2.02013-03-06T00:21:49Z<p>Dbeckstrom: </p>
<hr />
<div>The [[PT_Multimedia_Version_1.0_Install|PT Multimedia 1.0 Install]] guide may be used for installing version 2. However, there are a few install tasks that have been updated for V2.<br />
<br />
=== Import ===<br />
<br />
Import Custom Elements in this order: <br />
# Multimedia Category (Multimedia-Category -Custom-Element.zip)<br />
# Multimedia Category Gallery (Multimedia-Category –Gallery-Custom-Element.zip)<br />
# Multimedia (Multimedia- Custom-Element.zip)<br />
# Multimedia Series (Multimedia-Series -Custom-Element.zip)<br />
# Multimedia Series Gallery (Multimedia-Series -Gallery-Custom-Element.zip)<br />
# Multimedia Configuration (ptMultiMedia-Configuration-Custom-Element.zip)<br />
# Multimedia Single Chooser (Multimedia-Single-Chooser-Custom-Element.zip)<br />
<br />
<br />
Import Metadata form:<br />
<br />
# Multimedia Display Format (MultimediaDisplayFormat -Metadata-Form.zip)<br />
## Bind this form to the following Handlers:<br />
### Multimedia (multimedia_rh.cfm) - which is bound to the Multimedia Element<br />
### Multimedia (multimedia_rh.cfm) - which is bound to the Multimedia Category Gallery Element<br />
### Multimedia (multimedia_rh.cfm) - which is bound to the Multimedia Series Gallery Element<br />
### Multimedia Search Results (multimediaSearchResults_rh.cfm) - which is bound to the Multimedia Element</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Install_v2.0&diff=6462PT Multimedia Install v2.02013-03-06T00:19:15Z<p>Dbeckstrom: </p>
<hr />
<div>The [[PT_Multimedia_Version_1.0_Install|PT Multimedia 1.0 Install]] guide may be used for installing version 2. However, there are a few install tasks that have been updated for V2.<br />
<br />
=== Import ===<br />
<br />
Import Custom Elements in this order: <br />
# Multimedia Category (Multimedia-Category -Custom-Element.zip)<br />
# Multimedia Category Gallery (Multimedia-Category –Gallery-Custom-Element.zip)<br />
# Multimedia (Multimedia- Custom-Element.zip)<br />
# Multimedia Series (Multimedia-Series -Custom-Element.zip)<br />
# Multimedia Series Gallery (Multimedia-Series -Gallery-Custom-Element.zip)<br />
# Multimedia Configuration (ptMultiMedia-Configuration-Custom-Element.zip)<br />
# Multimedia Single Chooser (Multimedia-Single-Chooser-Custom-Element.zip)<br />
<br />
<br />
Import Metadata form:<br />
<br />
# Multimedia Display Format (MultimediaDisplayFormat -Metadata-Form.zip)<br />
## Bind this form to the following Handlers:<br />
### Multimedia - Multimedia Element<br />
### Multimedia - Multimedia Category Gallery Element<br />
### Multimedia - Multimedia Series Gallery Element<br />
### Multimedia Search Results - Multimedia Element</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Install_v2.0&diff=6461PT Multimedia Install v2.02013-03-06T00:15:30Z<p>Dbeckstrom: </p>
<hr />
<div>The [[PT_Multimedia_Version_1.0_Install|PT Multimedia 1.0 Install]] guide may be used for installing version 2. However, there are a few install tasks that have been updated for V2.<br />
<br />
Import Metadata form:<br />
<br />
# Multimedia Display Format (MultimediaDisplayFormat -Metadata-Form.zip)<br />
## Bind this form to the following Handlers:<br />
### Multimedia - Multimedia Element<br />
### Multimedia - Multimedia Category Gallery Element<br />
### Multimedia - Multimedia Series Gallery Element<br />
### Multimedia Search Results - Multimedia Element</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Install_v2.0&diff=6460PT Multimedia Install v2.02013-03-06T00:15:02Z<p>Dbeckstrom: </p>
<hr />
<div>The [[PT_Multimedia_Version_1.0_Install|PT Multimedia 1.0 Install]] guide may be used for installing version 2. However, there are a few install tasks that have been updated for V2.<br />
<br />
Import Metadata form:<br />
<br />
# Multimedia Display Format (MultimediaDisplayFormat -Metadata-Form.zip)<br />
## Bind this form to the following Handlers"<br />
### Multimedia - Multimedia Element<br />
### Multimedia - Multimedia Category Gallery Element<br />
### Multimedia - Multimedia Series Gallery Element<br />
### Multimedia Search Results - Multimedia Element</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Install_v2.0&diff=6459PT Multimedia Install v2.02013-03-06T00:13:58Z<p>Dbeckstrom: </p>
<hr />
<div>The [[PT_Multimedia_Version_1.0_Install|PT Multimedia 1.0 Install]] guide may be used for installing version 2. However, there are a few install tasks that have been updated for V2.<br />
<br />
Import Metadata form:<br />
<br />
# Multimedia Display Format (MultimediaDisplayFormat -Metadata-Form.zip)<br />
## Bind this form to the following Multimedia Render Handler<br />
### Multimedia - Multimedia Element<br />
### Multimedia - Multimedia Category Gallery Element<br />
### Multimedia - Multimedia Series Gallery Element<br />
### Multimedia Search Results</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Install_v2.0&diff=6444PT Multimedia Install v2.02013-03-05T21:52:43Z<p>Dbeckstrom: </p>
<hr />
<div>The [[PT_Multimedia_Version_1.0_Install|PT Multimedia 1.0 Install]] guide may be used for installing version 2. However, there are a few install tasks that have been updated for V2.<br />
<br />
Import Metadata form:<br />
<br />
# Multimedia Display Format (MultimediaDisplayFormat -Metadata-Form.zip)<br />
## Bind this form to the following Multimedia Render Handler<br />
### Multimedia<br />
### Multimedia Search Results</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Install_v2.0&diff=6443PT Multimedia Install v2.02013-03-05T21:46:48Z<p>Dbeckstrom: Created page with 'The PT Multimedia 1.0 Install guide may be used for installing version 2.'</p>
<hr />
<div>The [[PT_Multimedia_Version_1.0_Install|PT Multimedia 1.0 Install]] guide may be used for installing version 2.</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Release_Notes_v2.0&diff=6442PT Multimedia Release Notes v2.02013-03-05T21:44:09Z<p>Dbeckstrom: /* Enhancements */</p>
<hr />
<div>=== Enhancements ===<br />
* Updated app for ADF v1.6.<br />
* Added support for entering either a youtube video ID or the entire embed code.<br />
* Dropped support of Yahoo videos after Yahoo stopped providing an API to their videos.<br />
* Added support for rendering Multimedia using the Multimedia Element which is new in this version. The prior version rendered Multimedia from the Category Gallery Element and the Series Gallery Elements.<br />
<br />
=== Bug Fixes ===<br />
* Fixed app to work on unix systems and removed extra "new and original" files.<br />
* Updated to handle malformed urls from youtube.<br />
* Added output=false to getAppconfig function to fix issue on Railo.<br />
* Fixed typo for the script tag in the media uploader props file.<br />
* Added logic to remove the ADD new config option after the element has one record.<br />
* Added an end quote to properly terminate the paramFields string.<br />
* Fixed formatting issue due to a missing end DIV tag.<br />
=== SVN Change Log ===<br />
For detailed SVN repository updates for the v2.0, please see the [[PT_Multimedia_Version_2.0_Change_Log|PT Multimedia v2.0 Change Log]].</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Release_Notes_v2.0&diff=6441PT Multimedia Release Notes v2.02013-03-05T21:43:52Z<p>Dbeckstrom: /* Enhancements */</p>
<hr />
<div>=== Enhancements ===<br />
* Updated app for ADF v1.6.<br />
* Added support for entering either a youtube video ID or the entire embed code.<br />
* Dropped support of Yahoo videos after Yahoo stopped providing an API to their videos.<br />
* Added support for rendering Multimedia using the Multimedia element which is new in this version. The prior version rendered Multimedia from the Category Gallery Element and the Series Gallery Elements.<br />
<br />
=== Bug Fixes ===<br />
* Fixed app to work on unix systems and removed extra "new and original" files.<br />
* Updated to handle malformed urls from youtube.<br />
* Added output=false to getAppconfig function to fix issue on Railo.<br />
* Fixed typo for the script tag in the media uploader props file.<br />
* Added logic to remove the ADD new config option after the element has one record.<br />
* Added an end quote to properly terminate the paramFields string.<br />
* Fixed formatting issue due to a missing end DIV tag.<br />
=== SVN Change Log ===<br />
For detailed SVN repository updates for the v2.0, please see the [[PT_Multimedia_Version_2.0_Change_Log|PT Multimedia v2.0 Change Log]].</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia&diff=6440PT Multimedia2013-03-05T21:40:09Z<p>Dbeckstrom: /* Overview */</p>
<hr />
<div>== About Multimedia App ==<br />
The Multimedia application is built in the [[Overview|Application Development Framework (ADF)]].<br />
<br />
== Overview ==<br />
The multimedia application seamlessly integrates both locally hosted audio and video <br />
into your web site as well as multimedia from 3rd party sites such as youtube and Vimeo.<br />
<br />
Multimedia is displayed by first choosing a category or series, which filters media to determine it's eligibility for display, and then by selecting the display format in which to present the media.<br />
<br />
Multimedia is managed through an administrative page containing the multimedia manager.<br />
<br />
More details for the PT Multimedia can be found in the [[PT_Multimedia_Overview|overview page]].<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 multimedia application. For detailed instructions, see the [[Overview|Application Development Framework (ADF)]] 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 installation of PT Multimedia, remove any Custom Elements/Metadata Forms with the names contained in the "Contents" section above (see exception below). If you do not remove existing elements with these names, you may have difficulties during the installation. <br />
<br />
'''Exception''' - The Custom Text Area Field is part of the ADF extensions and not specific to the PT Multimedia application. Do not remove this field if it is already registered as a custom field for your site.<br />
<br />
== Installation Guides ==<br />
Current Release v1.0:<br />
* [[PT_Multimedia_Version_1.0_Install|Install Guide]]<br />
<br />
Current Development v2.0:<br />
* [[PT_Multimedia_Release_Notes_v2.0|Release Notes]]<br />
* [[PT_Multimedia_Install_v2.0|Install Guide]]<br />
* [[PT_Multimedia_Upgrade_v2.0|Upgrade Guide]]<br />
<br />
== Getting Started==<br />
* [[PT_Multimedia_Getting_Started|Getting Started]] - Guide to using the Multimedia application.<br />
== Troubleshooting ==<br />
== Known Issues/Bugs ==<br />
Found a bug? View the [[Multimedia 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:Multimedia]]</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Version_2.0_Change_Log&diff=6439PT Multimedia Version 2.0 Change Log2013-03-04T19:32:47Z<p>Dbeckstrom: Created page with 'Revision: 55 Author: mcarroll Date: 2:26:26 PM, Wednesday, February 06, 2013 Message: Removed any JavaScript "alert" statements that were not used in components and custom script…'</p>
<hr />
<div>Revision: 55<br />
Author: mcarroll<br />
Date: 2:26:26 PM, Wednesday, February 06, 2013<br />
Message:<br />
Removed any JavaScript "alert" statements that were not used in components and custom scripts.<br />
----<br />
Modified : /branches/2.0/components/App.cfc<br />
Modified : /branches/2.0/customcf/handle_media_add.cfm<br />
<br />
Revision: 54<br />
Author: mcarroll<br />
Date: 10:12:45 AM, Wednesday, February 06, 2013<br />
Message:<br />
Updated app for ADF v1.6.<br />
----<br />
Modified : /branches/2.0/appBeanConfig.cfm<br />
Modified : /branches/2.0/components/App.cfc<br />
Deleted : /branches/2.0/lib<br />
<br />
Revision: 51<br />
Author: mcarroll<br />
Date: 8:45:28 AM, Monday, September 10, 2012<br />
Message:<br />
Updated the app SVN version.<br />
----<br />
Modified : /branches/2.0/components/App.cfc<br />
<br />
Revision: 50<br />
Author: mcarroll<br />
Date: 8:44:40 AM, Monday, September 10, 2012<br />
Message:<br />
Updated html with DIV clears for CS Work Mode spacing.<br />
----<br />
Modified : /branches/2.0/renderhandlers/multimediaSearchResults_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_categoryname_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_seriesname_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_single_embedded_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_single_rh.cfm<br />
<br />
Revision: 49<br />
Author: mcarroll<br />
Date: 4:03:11 PM, Thursday, September 06, 2012<br />
Message:<br />
Updated to load the LB header and footers.<br />
Formatted code to remove the "writeoutput" blocks. <br />
----<br />
Modified : /branches/2.0/appBeanConfig.cfm<br />
Modified : /branches/2.0/components/mediaService.cfc<br />
Modified : /branches/2.0/customcf/media_lightbox_player.cfm<br />
<br />
Revision: 48<br />
Author: mcarroll<br />
Date: 3:19:58 PM, Thursday, September 06, 2012<br />
Message:<br />
Removed load JQuery version to load from the ADF default.<br />
----<br />
Modified : /branches/2.0/components/App.cfc<br />
Modified : /branches/2.0/customcf/multimedia_config_admin_ds.cfm<br />
Modified : /branches/2.0/customfields/media_host_select_field_render.cfm<br />
Modified : /branches/2.0/customfields/media_type_select_field_render.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_single_rh.cfm<br />
<br />
Revision: 47<br />
Author: mcarroll<br />
Date: 3:16:12 PM, Thursday, September 06, 2012<br />
Message:<br />
Updated the app for ADF v1.5.<br />
Updated the styles to not load into site wide and made style IDs and Classes unique.<br />
----<br />
Modified : /branches/2.0/appBeanConfig.cfm<br />
Modified : /branches/2.0/components/App.cfc<br />
Modified : /branches/2.0/components/mediaCategoryGC.cfc<br />
Modified : /branches/2.0/components/mediaDAO.cfc<br />
Modified : /branches/2.0/components/mediaGC.cfc<br />
Modified : /branches/2.0/components/mediaRenderService.cfc<br />
Modified : /branches/2.0/components/mediaSeriesGC.cfc<br />
Modified : /branches/2.0/components/mediaService.cfc<br />
Modified : /branches/2.0/components/mediaSingleGC.cfc<br />
Modified : /branches/2.0/customcf/handle_media_add.cfm<br />
Modified : /branches/2.0/customcf/handle_media_upload.cfm<br />
Modified : /branches/2.0/customcf/media_lightbox_player.cfm<br />
Modified : /branches/2.0/customcf/multimedia_config_admin_ds.cfm<br />
Modified : /branches/2.0/lib/ceData_1_1.cfc<br />
Modified : /branches/2.0/renderhandlers/multimediaSearchResults_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_categoryname_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_seriesname_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_single_embedded_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_single_rh.cfm<br />
Modified : /branches/2.0/style/ptmultimedia.css<br />
<br />
Revision: 46<br />
Author: dbeckstrom<br />
Date: 10:03:22 AM, Wednesday, August 15, 2012<br />
Message:<br />
Dave B 08/15/2012 - Added lightbox header and footer scripts to include into lightbox pages.<br />
----<br />
Added : /branches/2.0/customcf/ADF_lightbox_footer.cfm<br />
Added : /branches/2.0/customcf/ADF_lightbox_header.cfm<br />
<br />
Revision: 45<br />
Author: dbeckstrom<br />
Date: 9:59:39 AM, Wednesday, August 15, 2012<br />
Message:<br />
Dave B 08/15/2102 - Added output=false to getAppconfig function to fix issue on Railo.<br />
----<br />
Modified : /branches/2.0/components/App.cfc<br />
<br />
Revision: 42<br />
Author: mcarroll<br />
Date: 10:17:54 AM, Wednesday, April 04, 2012<br />
Message:<br />
Updated the branch 2.0 with any updates from branch 1.1 or the TRUNK that were not merged into this branch.<br />
----<br />
Modified : /branches/2.0/components/App.cfc<br />
Modified : /branches/2.0/components/proxyWhiteList.xml<br />
Added : /branches/2.0/exported-objects/Multimedia-Single-Chooser-Custom-Element.zip<br />
<br />
Revision: 41<br />
Author: mcarroll<br />
Date: 10:03:44 AM, Wednesday, April 04, 2012<br />
Message:<br />
Added updated code from TRUNK into the branch.<br />
Added parsing to handle various YT embed code URL formats.<br />
----<br />
Modified : /branches/2.0/components/mediaRenderService.cfc<br />
<br />
Revision: 40<br />
Author: mcarroll<br />
Date: 9:59:56 AM, Wednesday, April 04, 2012<br />
Message:<br />
Added updated code from TRUNK into the branch.<br />
Wmode of "transparent" wasn't being applied at all times when producing flash embed code. Updated the cleaner to make sure of it.<br />
----<br />
Modified : /branches/2.0/customcf/flashCleaner.xsl<br />
<br />
Revision: 39<br />
Author: mcarroll<br />
Date: 9:46:48 AM, Wednesday, April 04, 2012<br />
Message:<br />
Updated License code in the comment header.<br />
----<br />
Modified : /branches/2.0/appBeanConfig.cfm<br />
Modified : /branches/2.0/components/App.cfc<br />
<br />
Revision: 38<br />
Author: mcarroll<br />
Date: 9:43:12 AM, Wednesday, April 04, 2012<br />
Message:<br />
Added version variables into the app code.<br />
Fixed typo for the script tag in the media uploader props file.<br />
----<br />
Modified : /branches/2.0/appBeanConfig.cfm<br />
Modified : /branches/2.0/components/App.cfc<br />
Modified : /branches/2.0/customfields/media_uploader_props.cfm<br />
<br />
Revision: 37<br />
Author: gcronkright<br />
Date: 10:16:11 AM, Friday, March 02, 2012<br />
Message:<br />
Updated the logic around the 'Items' getCEData call to make sure the 'Criteria' Array as a length <br />
----<br />
Modified : /branches/2.0<br />
<br />
Revision: 36<br />
Author: gcronkright<br />
Date: 10:12:09 AM, Friday, March 02, 2012<br />
Message:<br />
Updated the logic around the 'Items' getCEData call to make sure the 'Criteria' Array as a length <br />
----<br />
Modified : /branches/2.0/renderhandlers/multimedia_single_embedded_rh.cfm<br />
Modified : /branches/2.0/renderhandlers/multimedia_single_rh.cfm<br />
<br />
Revision: 35<br />
Author: gcronkright<br />
Date: 9:24:21 AM, Thursday, December 15, 2011<br />
Message:<br />
extensions/customcf: Config Admin Custom Script<br />
file: multimedia_config_admin_ds.cfm<br />
update: Added logic to remove the ADD new config option after the element has one record<br />
----<br />
Modified : /branches/2.0/customcf/multimedia_config_admin_ds.cfm<br />
<br />
Revision: 34<br />
Author: gcronkright<br />
Date: 8:49:13 PM, Wednesday, November 09, 2011<br />
Message:<br />
Added an end quote to properly terminate the paramFields string<br />
----<br />
Modified : /branches/2.0/customfields/media_uploader_props.cfm<br />
<br />
Revision: 32<br />
Author: rkahn<br />
Date: 1:50:46 PM, Monday, September 19, 2011<br />
Message:<br />
Fixed app to work on unix systems and removed extra "new and original" files.<br />
----<br />
Modified : /branches/2.0/appBeanConfig.cfm<br />
Modified : /branches/2.0/components/App.cfc<br />
Modified : /branches/2.0/components/mediaRenderService.cfc<br />
Deleted : /branches/2.0/components/mediaRenderServiceNEW.cfc<br />
Deleted : /branches/2.0/components/mediaRenderServiceORIGINAL.cfc<br />
Modified : /branches/2.0/customcf/media_lightbox_player.cfm<br />
Deleted : /branches/2.0/customcf/media_lightbox_player_new.cfm<br />
Deleted : /branches/2.0/lib/ceData_1_0.cfc<br />
Added : /branches/2.0/lib/ceData_1_1.cfc<br />
Modified : /branches/2.0/renderhandlers/multimedia_single_rh.cfm<br />
<br />
Revision: 31<br />
Author: rkahn<br />
Date: 12:37:46 PM, Wednesday, June 29, 2011<br />
Message:<br />
Updating to handle malformed urls from youtube.<br />
----<br />
Modified : /branches/2.0/components/mediaRenderService.cfc<br />
<br />
Revision: 30<br />
Author: rkahn<br />
Date: 8:43:29 AM, Monday, June 27, 2011<br />
Message:<br />
Brining in 2.0 changes.<br />
----<br />
Modified : /branches/2.0/appBeanConfig.cfm<br />
Added : /branches/2.0/components/mediaGC.cfc<br />
Modified : /branches/2.0/components/mediaRenderService.cfc<br />
Added : /branches/2.0/components/mediaRenderServiceNEW.cfc<br />
Added : /branches/2.0/components/mediaRenderServiceORIGINAL.cfc<br />
Modified : /branches/2.0/components/mediaService.cfc<br />
Added : /branches/2.0/components/mediaSingleGC.cfc<br />
Modified : /branches/2.0/components/proxyWhiteList.xml<br />
Modified : /branches/2.0/customcf/handle_media_add.cfm<br />
Modified : /branches/2.0/customcf/manager_layout.cfm<br />
Modified : /branches/2.0/customcf/media_lightbox_player.cfm<br />
Added : /branches/2.0/customcf/media_lightbox_player_new.cfm<br />
Modified : /branches/2.0/customcf/multimedia_config_admin_ds.cfm<br />
Modified : /branches/2.0/customfields/media_host_select_field_render.cfm<br />
Modified : /branches/2.0/customfields/media_uploader_render.cfm<br />
Added : /branches/2.0/player/JW Player Embedding and JavaScript Guide.pdf<br />
Added : /branches/2.0/player/jwplayer.js<br />
Added : /branches/2.0/player/license.txt<br />
Modified : /branches/2.0/player/player.swf<br />
Added : /branches/2.0/player/preview.jpg<br />
Added : /branches/2.0/player/readme.html<br />
Modified : /branches/2.0/player/swfobject.js<br />
Added : /branches/2.0/player/video.mp4<br />
Added : /branches/2.0/player/yt.swf<br />
Modified : /branches/2.0/renderhandlers/multimedia_rh.cfm<br />
Added : /branches/2.0/renderhandlers/multimedia_single_embedded_rh.cfm<br />
Added : /branches/2.0/renderhandlers/multimedia_single_rh.cfm<br />
<br />
Revision: 29<br />
Author: rkahn<br />
Date: 3:00:50 PM, Friday, June 24, 2011<br />
Message:<br />
<br />
----<br />
Added : /branches/2.0 (Copy from path: /trunk, Revision, 28)</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Release_Notes_v2.0&diff=6438PT Multimedia Release Notes v2.02013-03-04T19:32:11Z<p>Dbeckstrom: /* Bug Fixes */</p>
<hr />
<div>=== Enhancements ===<br />
* Updated app for ADF v1.6.<br />
* Added support for entering either a youtube video ID or the entire embed code.<br />
* Dropped support of Yahoo videos after Yahoo stopped providing an API to their videos.<br />
<br />
=== Bug Fixes ===<br />
* Fixed app to work on unix systems and removed extra "new and original" files.<br />
* Updated to handle malformed urls from youtube.<br />
* Added output=false to getAppconfig function to fix issue on Railo.<br />
* Fixed typo for the script tag in the media uploader props file.<br />
* Added logic to remove the ADD new config option after the element has one record.<br />
* Added an end quote to properly terminate the paramFields string.<br />
* Fixed formatting issue due to a missing end DIV tag.<br />
=== SVN Change Log ===<br />
For detailed SVN repository updates for the v2.0, please see the [[PT_Multimedia_Version_2.0_Change_Log|PT Multimedia v2.0 Change Log]].</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Release_Notes_v2.0&diff=6437PT Multimedia Release Notes v2.02013-03-04T19:30:04Z<p>Dbeckstrom: /* Enhancements */</p>
<hr />
<div>=== Enhancements ===<br />
* Updated app for ADF v1.6.<br />
* Added support for entering either a youtube video ID or the entire embed code.<br />
* Dropped support of Yahoo videos after Yahoo stopped providing an API to their videos.<br />
<br />
=== Bug Fixes ===<br />
* Fixed app to work on unix systems and removed extra "new and original" files.<br />
* Updated to handle malformed urls from youtube.<br />
* Added output=false to getAppconfig function to fix issue on Railo.<br />
* Fixed typo for the script tag in the media uploader props file.<br />
* Added logic to remove the ADD new config option after the element has one record.<br />
* Added an end quote to properly terminate the paramFields string.<br />
* Fixed formatting issue due to a missing end DIV tag.</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Release_Notes_v2.0&diff=6436PT Multimedia Release Notes v2.02013-03-04T19:29:32Z<p>Dbeckstrom: /* Bug Fixes */</p>
<hr />
<div>=== Enhancements ===<br />
* Updated app for ADF v1.6.<br />
* Added support for entering either a youtube video ID of the entire embed code.<br />
* Dropped support of Yahoo videos after Yahoo stopped providing an API to their videos.<br />
<br />
=== Bug Fixes ===<br />
* Fixed app to work on unix systems and removed extra "new and original" files.<br />
* Updated to handle malformed urls from youtube.<br />
* Added output=false to getAppconfig function to fix issue on Railo.<br />
* Fixed typo for the script tag in the media uploader props file.<br />
* Added logic to remove the ADD new config option after the element has one record.<br />
* Added an end quote to properly terminate the paramFields string.<br />
* Fixed formatting issue due to a missing end DIV tag.</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Release_Notes_v2.0&diff=6435PT Multimedia Release Notes v2.02013-03-04T19:28:58Z<p>Dbeckstrom: /* Bug Fixes */</p>
<hr />
<div>=== Enhancements ===<br />
* Updated app for ADF v1.6.<br />
* Added support for entering either a youtube video ID of the entire embed code.<br />
* Dropped support of Yahoo videos after Yahoo stopped providing an API to their videos.<br />
<br />
=== Bug Fixes ===<br />
* Fixed app to work on unix systems and removed extra "new and original" files.<br />
* Updated to handle malformed urls from youtube.<br />
* Added output=false to getAppconfig function to fix issue on Railo.<br />
* Fixed typo for the script tag in the media uploader props file.<br />
* Added logic to remove the ADD new config option after the element has one record.<br />
* Added an end quote to properly terminate the paramFields string</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Release_Notes_v2.0&diff=6434PT Multimedia Release Notes v2.02013-03-04T19:28:02Z<p>Dbeckstrom: /* Bug Fixes */</p>
<hr />
<div>=== Enhancements ===<br />
* Updated app for ADF v1.6.<br />
* Added support for entering either a youtube video ID of the entire embed code.<br />
* Dropped support of Yahoo videos after Yahoo stopped providing an API to their videos.<br />
<br />
=== Bug Fixes ===<br />
* Fixed app to work on unix systems and removed extra "new and original" files.<br />
* Updated to handle malformed urls from youtube.<br />
* Fixed typo for the script tag in the media uploader props file.<br />
* Added output=false to getAppconfig function to fix issue on Railo.<br />
* Fixed typo for the script tag in the media uploader props file.<br />
* Added logic to remove the ADD new config option after the element has one record.<br />
* Added an end quote to properly terminate the paramFields string</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Release_Notes_v2.0&diff=6433PT Multimedia Release Notes v2.02013-03-04T19:25:28Z<p>Dbeckstrom: /* Enhancements */</p>
<hr />
<div>=== Enhancements ===<br />
* Updated app for ADF v1.6.<br />
* Added support for entering either a youtube video ID of the entire embed code.<br />
* Dropped support of Yahoo videos after Yahoo stopped providing an API to their videos.<br />
<br />
=== Bug Fixes ===<br />
* Fixed app to work on unix systems and removed extra "new and original" files.<br />
* Updated to handle malformed urls from youtube.<br />
* Fixed typo for the script tag in the media uploader props file.</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Release_Notes_v2.0&diff=6432PT Multimedia Release Notes v2.02013-03-04T19:21:52Z<p>Dbeckstrom: /* Bug Fixes */</p>
<hr />
<div>=== Enhancements ===<br />
* Added <br />
=== Bug Fixes ===<br />
* Fixed app to work on unix systems and removed extra "new and original" files.<br />
* Updated to handle malformed urls from youtube.<br />
* Fixed typo for the script tag in the media uploader props file.</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=PT_Multimedia_Release_Notes_v2.0&diff=6431PT Multimedia Release Notes v2.02013-03-04T19:20:35Z<p>Dbeckstrom: Created page with '=== Bug Fixes === * Fixed app to work on unix systems and removed extra "new and original" files. * Updated to handle malformed urls from youtube. * Fixed typo for the script tag…'</p>
<hr />
<div>=== Bug Fixes ===<br />
* Fixed app to work on unix systems and removed extra "new and original" files.<br />
* Updated to handle malformed urls from youtube.<br />
* Fixed typo for the script tag in the media uploader props file.</div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=CSData_1_0-getCustomMetadata&diff=5538CSData 1 0-getCustomMetadata2012-03-26T23:07:43Z<p>Dbeckstrom: /* Description */</p>
<hr />
<div>__NOTOC__<br />
Attention: Do not change any text in the description, signature, and paramter sections.<br />
<br />
Return to [[CSData_1_0]]<br />
<br />
== Description ==<br />
Given a Page ID returns the custom metadata for the page.<br />
<br />
== Signature == <br />
public struct <strong>getCustomMetadata</strong> ( numeric pageID, numeric categoryID, numeric subsiteID, string inheritedTemplateList )<br />
<br />
== Parameters == <br />
<br />
<table id="lib-params"><br />
<tr class="header"><br />
<td>Required</td><br />
<td>Name</td><br />
<td>Type</td><br />
<td>Description</td><br />
</tr><br />
<br />
<br />
<tr><br />
<br />
<td class="required">required</td><br />
<br />
<td>pageID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td>&nbsp;</td><br />
<br />
<td>categoryID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td>&nbsp;</td><br />
<br />
<td>subsiteID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td class="required">optional</td><br />
<br />
<td>inheritedTemplateList</td><br />
<td>string</td><br />
<td>[Default: ] </td><br />
</tr><br />
<br />
</table><br />
=== Usage: ===<br />
Example 1: Get the blogID from the custom Metadata form bound to the current page:<br />
<source lang="cfm"><br />
<cfscript><br />
pageMeta = application.ADF.CSData.getCustomMetadata(request.page.id);<br />
if ( StructKeyExists(pageMeta.custom, "Blogs2") AND<br />
(StructKeyExists(pageMeta.custom.Blogs2, "blogID")) and <br />
(LEN(pageMeta.custom.Blogs2.blogID))){<br />
<br />
blogID = pageMeta.custom.Blogs2.blogID;<br />
<br />
}<br />
</cfscript><br />
</source></div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=CSData_1_0-getCustomMetadata&diff=5537CSData 1 0-getCustomMetadata2012-03-26T23:06:35Z<p>Dbeckstrom: /* Usage: */</p>
<hr />
<div>__NOTOC__<br />
Attention: Do not change any text in the description, signature, and paramter sections.<br />
<br />
Return to [[CSData_1_0]]<br />
<br />
== Description ==<br />
<br />
== Signature == <br />
public struct <strong>getCustomMetadata</strong> ( numeric pageID, numeric categoryID, numeric subsiteID, string inheritedTemplateList )<br />
<br />
== Parameters == <br />
<br />
<table id="lib-params"><br />
<tr class="header"><br />
<td>Required</td><br />
<td>Name</td><br />
<td>Type</td><br />
<td>Description</td><br />
</tr><br />
<br />
<br />
<tr><br />
<br />
<td class="required">required</td><br />
<br />
<td>pageID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td>&nbsp;</td><br />
<br />
<td>categoryID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td>&nbsp;</td><br />
<br />
<td>subsiteID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td class="required">optional</td><br />
<br />
<td>inheritedTemplateList</td><br />
<td>string</td><br />
<td>[Default: ] </td><br />
</tr><br />
<br />
</table><br />
=== Usage: ===<br />
Example 1: Get the blogID from the custom Metadata form bound to the current page:<br />
<source lang="cfm"><br />
<cfscript><br />
pageMeta = application.ADF.CSData.getCustomMetadata(request.page.id);<br />
if ( StructKeyExists(pageMeta.custom, "Blogs2") AND<br />
(StructKeyExists(pageMeta.custom.Blogs2, "blogID")) and <br />
(LEN(pageMeta.custom.Blogs2.blogID))){<br />
<br />
blogID = pageMeta.custom.Blogs2.blogID;<br />
<br />
}<br />
</cfscript><br />
</source></div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=CSData_1_0-getCustomMetadata&diff=5536CSData 1 0-getCustomMetadata2012-03-26T23:05:42Z<p>Dbeckstrom: /* Usage: */</p>
<hr />
<div>__NOTOC__<br />
Attention: Do not change any text in the description, signature, and paramter sections.<br />
<br />
Return to [[CSData_1_0]]<br />
<br />
== Description ==<br />
<br />
== Signature == <br />
public struct <strong>getCustomMetadata</strong> ( numeric pageID, numeric categoryID, numeric subsiteID, string inheritedTemplateList )<br />
<br />
== Parameters == <br />
<br />
<table id="lib-params"><br />
<tr class="header"><br />
<td>Required</td><br />
<td>Name</td><br />
<td>Type</td><br />
<td>Description</td><br />
</tr><br />
<br />
<br />
<tr><br />
<br />
<td class="required">required</td><br />
<br />
<td>pageID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td>&nbsp;</td><br />
<br />
<td>categoryID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td>&nbsp;</td><br />
<br />
<td>subsiteID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td class="required">optional</td><br />
<br />
<td>inheritedTemplateList</td><br />
<td>string</td><br />
<td>[Default: ] </td><br />
</tr><br />
<br />
</table><br />
=== Usage: ===<br />
Example 1: Get the blogID from the custom Metadata form bound to the current page:<br />
<source lang="cfm"><br />
<cfscript><br />
pageMeta = application.ADF.CSData.getCustomMetadata(request.page.id);<br />
if ( StructKeyExists(pageMeta.custom, "Blogs2") AND<br />
(StructKeyExists(pageMeta.custom.Blogs2, "blogID")) and <br />
(LEN(pageMeta.custom.Blogs2.blogID))){<br />
blogID = pageMeta.custom.Blogs2.blogID;<br />
<br />
}<br />
</cfscript><br />
</source></div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=CSData_1_0-getCustomMetadata&diff=5535CSData 1 0-getCustomMetadata2012-03-26T23:04:43Z<p>Dbeckstrom: /* Parameters */</p>
<hr />
<div>__NOTOC__<br />
Attention: Do not change any text in the description, signature, and paramter sections.<br />
<br />
Return to [[CSData_1_0]]<br />
<br />
== Description ==<br />
<br />
== Signature == <br />
public struct <strong>getCustomMetadata</strong> ( numeric pageID, numeric categoryID, numeric subsiteID, string inheritedTemplateList )<br />
<br />
== Parameters == <br />
<br />
<table id="lib-params"><br />
<tr class="header"><br />
<td>Required</td><br />
<td>Name</td><br />
<td>Type</td><br />
<td>Description</td><br />
</tr><br />
<br />
<br />
<tr><br />
<br />
<td class="required">required</td><br />
<br />
<td>pageID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td>&nbsp;</td><br />
<br />
<td>categoryID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td>&nbsp;</td><br />
<br />
<td>subsiteID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td class="required">optional</td><br />
<br />
<td>inheritedTemplateList</td><br />
<td>string</td><br />
<td>[Default: ] </td><br />
</tr><br />
<br />
</table><br />
=== Usage: ===<br />
Example 1: Get the blogID from the custom Metadata form bound to the current page:<br />
<source lang="cfm"><br />
<cfscript><br />
pageMeta = application.ADF.CSData.getCustomMetadata(request.page.id);<br />
if ( StructKeyExists(pageMeta.custom, "Blogs2") AND (StructKeyExists(pageMeta.custom.Blogs2, "blogID")) and (LEN(pageMeta.custom.Blogs2.blogID))){<br />
blogID = pageMeta.custom.Blogs2.blogID;<br />
<br />
}<br />
</cfscript><br />
</source></div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=CSData_1_0-getStandardMetadata&diff=5534CSData 1 0-getStandardMetadata2012-03-26T22:35:21Z<p>Dbeckstrom: /* Description */</p>
<hr />
<div>__NOTOC__<br />
Attention: Do not change any text in the description, signature, and paramter sections.<br />
<br />
Return to [[CSData_1_0]]<br />
<br />
== Description ==<br />
Given a Page ID returns the standard metadata for the page.<br />
<br />
== Signature == <br />
public struct <strong>getStandardMetadata</strong> ( numeric csPageID )<br />
<br />
== Parameters == <br />
<br />
<table id="lib-params"><br />
<tr class="header"><br />
<td>Required</td><br />
<td>Name</td><br />
<td>Type</td><br />
<td>Description</td><br />
</tr><br />
<br />
<br />
<tr><br />
<br />
<td class="required">required</td><br />
<br />
<td>csPageID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
</table><br />
=== Usage: ===<br />
Example 1: Using the page ID from a field in a custom element, get the page metadata for the page and find the subsite ID for the subsite in which the page is located:<br />
<source lang="cfm"><br />
<cfscript><br />
pageMeta = application.ADF.CSData.getStandardMetadata("items[i].values.mypageID");<br />
if ( StructKeyExists(pageMeta, "subsiteid") AND LEN(pageMeta.subsiteid)){<br />
pagesubsiteid = pageMeta.subsiteid;<br />
}<br />
</cfscript><br />
</source></div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=CSData_1_0-getStandardMetadata&diff=5533CSData 1 0-getStandardMetadata2012-03-26T22:33:06Z<p>Dbeckstrom: /* Usage: */</p>
<hr />
<div>__NOTOC__<br />
Attention: Do not change any text in the description, signature, and paramter sections.<br />
<br />
Return to [[CSData_1_0]]<br />
<br />
== Description ==<br />
<br />
== Signature == <br />
public struct <strong>getStandardMetadata</strong> ( numeric csPageID )<br />
<br />
== Parameters == <br />
<br />
<table id="lib-params"><br />
<tr class="header"><br />
<td>Required</td><br />
<td>Name</td><br />
<td>Type</td><br />
<td>Description</td><br />
</tr><br />
<br />
<br />
<tr><br />
<br />
<td class="required">required</td><br />
<br />
<td>csPageID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
</table><br />
=== Usage: ===<br />
Example 1: Using the page ID from a field in a custom element, get the page metadata for the page and find the subsite ID for the subsite in which the page is located:<br />
<source lang="cfm"><br />
<cfscript><br />
pageMeta = application.ADF.CSData.getStandardMetadata("items[i].values.mypageID");<br />
if ( StructKeyExists(pageMeta, "subsiteid") AND LEN(pageMeta.subsiteid)){<br />
pagesubsiteid = pageMeta.subsiteid;<br />
}<br />
</cfscript><br />
</source></div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=CSData_1_0-getStandardMetadata&diff=5532CSData 1 0-getStandardMetadata2012-03-26T22:31:00Z<p>Dbeckstrom: /* Usage: */</p>
<hr />
<div>__NOTOC__<br />
Attention: Do not change any text in the description, signature, and paramter sections.<br />
<br />
Return to [[CSData_1_0]]<br />
<br />
== Description ==<br />
<br />
== Signature == <br />
public struct <strong>getStandardMetadata</strong> ( numeric csPageID )<br />
<br />
== Parameters == <br />
<br />
<table id="lib-params"><br />
<tr class="header"><br />
<td>Required</td><br />
<td>Name</td><br />
<td>Type</td><br />
<td>Description</td><br />
</tr><br />
<br />
<br />
<tr><br />
<br />
<td class="required">required</td><br />
<br />
<td>csPageID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
</table><br />
=== Usage: ===<br />
Example 1: Using the page ID from a custom element, get the page metadata and find the subsite ID for the subsite in which the page is located:<br />
<source lang="cfm"><br />
<cfscript><br />
pageMeta = application.ADF.CSData.getStandardMetadata("items[i].values.mypageID");<br />
<br />
if ( StructKeyExists(pageMeta, "subsiteid") AND<br />
LEN(pageMeta.subsiteid)){<br />
<br />
pagesubsiteid = pageMeta.subsiteid;<br />
<br />
}<br />
</cfscript><br />
</source></div>Dbeckstromhttp://community.paperthin.com/adf-docs/index.php?title=CSData_1_0-getStandardMetadata&diff=5531CSData 1 0-getStandardMetadata2012-03-26T22:29:21Z<p>Dbeckstrom: /* Parameters */</p>
<hr />
<div>__NOTOC__<br />
Attention: Do not change any text in the description, signature, and paramter sections.<br />
<br />
Return to [[CSData_1_0]]<br />
<br />
== Description ==<br />
<br />
== Signature == <br />
public struct <strong>getStandardMetadata</strong> ( numeric csPageID )<br />
<br />
== Parameters == <br />
<br />
<table id="lib-params"><br />
<tr class="header"><br />
<td>Required</td><br />
<td>Name</td><br />
<td>Type</td><br />
<td>Description</td><br />
</tr><br />
<br />
<br />
<tr><br />
<br />
<td class="required">required</td><br />
<br />
<td>csPageID</td><br />
<td>numeric</td><br />
<td></td><br />
</tr><br />
<br />
</table><br />
=== Usage: ===<br />
Example 1: Using the page ID from a custom element, get the page metadata and find the subsite ID for the subsite in which the page is located:<br />
<cfscript><br />
pageMeta = application.ADF.CSData.getStandardMetadata("items[i].values.mypageID");<br />
<br />
if ( StructKeyExists(pageMeta, "subsiteid") AND<br />
LEN(pageMeta.subsiteid)){<br />
<br />
pagesubsiteid = pageMeta.subsiteid;<br />
<br />
}<br />
</cfscript></div>Dbeckstrom