Difference between revisions of "Site.php file"

From aMember Pro Documentation
Jump to: navigation, search
(Created page with "We recommend you to use file application/configs/site.php (Rename file application/configs/site-dist.php to site.php if file site.php is not exists) for your customisation. If yo...")
 
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
We recommend you to use file application/configs/site.php (Rename file application/configs/site-dist.php to site.php if file site.php is not exists) for your customisation. If you follow this advice, your customizations won't be lost after upgrade, and it will be easy to track. You can put any custom code here.
+
We recommend using the file at application/configs/site.php for your PHP customizations. (Rename file application/configs/site-dist.php to site.php if the file site.php does not exist.)  
 +
 
 +
Likewise, use the file application/configs/site-dist.js for your JavaScript customizations. (Rename file application/configs/site-dist.js to site.js if the file site.js does not exist.)
 +
 
 +
If you follow this best practice, your customizations won't be lost during an upgrade, and will be easy to track. Put any custom code in either of these two files accordingly.

Latest revision as of 03:25, 26 October 2013

We recommend using the file at application/configs/site.php for your PHP customizations. (Rename file application/configs/site-dist.php to site.php if the file site.php does not exist.)

Likewise, use the file application/configs/site-dist.js for your JavaScript customizations. (Rename file application/configs/site-dist.js to site.js if the file site.js does not exist.)

If you follow this best practice, your customizations won't be lost during an upgrade, and will be easy to track. Put any custom code in either of these two files accordingly.