Difference between revisions of "Site.php file"

From aMember Pro Documentation
Jump to: navigation, search
 
Line 1: Line 1:
 
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.)  
 
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.
 
 
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 08:51, 23 March 2018

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.)

If you follow this best practice, your customizations won't be lost during an upgrade, and will be easy to track.