Difference between revisions of "Application Library Overrides Site Level"
From ADF Docs
m (Reverted edits by Ecaxabu (Talk) to last revision by Renee.mckechnie) |
|||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== ADF Application Library Overrides at the Site Level == | == ADF Application Library Overrides at the Site Level == | ||
See the [[Custom_Application_Site_Level_Configuration#ADF_Application_Site_Library_Overrides|Custom Application Site Level Configuration]] wiki page for more details. | See the [[Custom_Application_Site_Level_Configuration#ADF_Application_Site_Library_Overrides|Custom Application Site Level Configuration]] wiki page for more details. | ||
Latest revision as of 17:35, 24 November 2010
ADF Application Library Overrides at the Site Level
See the Custom Application Site Level Configuration wiki page for more details.
Following are instructions for overriding the library component at the site level:
- Locate the site directory that you want to add the library override component.
- Verify that a directory exists in the _cs_apps directory with the applications name. If no directory exists, create it. (Ex., for the Profile Application, the directory path will be mysite/_cs_apps/pt_profile/.)
- Verify a /components/lib directory exists withing the application name directory. If not, create these directories. (Ex., for the Profile Application, the directory path will be mysite/_cs_apps/pt_profile/components/lib/.)
- Copy the CFC file from the Lib into the /components/lib/ directory.
- For best practices, update the component and extend the original component in the ADF lib directory.
- Update the component as needed.
- Reset the ADF for the server and site.
