RE: [PHP] Best practice question regarding set_include_path()

-----Original Message----- From: Al [mailto:news@ridersite.org] Sent: Thursday, May 10, 2012 11:44 AM To: php-general@lists.php.net Subject: [PHP] Best practice question regarding set_include_path() For my applications, I've been using includes and other file addressing by using the doc root as the base dir. e.g. require_once $_SERVER['DOCUMENT_ROOT'] . '/miniRegDB/includes/miniRegDBconfig.php'; Recently, I ran into a problem with a new installation on a shared host where the doc root was assigned in an unusual manner. I rather not require setting a custom base dir [instead of $_SERVER['DOCUMENT_ROOT']'] for my applications. So, I was wondering if it would be good practice to use the set_include_path() and add the base dir for my applications. I've used this for dealing with Pear function files on shared servers and had no problems. Need some guidance regarding this subject. Thanks.... -- I use define to set the application path define('BASE_PATH','C:\\inetpub\\vhosts\\yourwebsite.com\\httpdocs\\'); Example: require_once (BASE_PATH. '/miniRegDB/includes/miniRegDBconfig.php'); works great for JQuery paths <script> $(document).ready(function() { $('#dareport').html('<img src="<?php echo BASE_URL;?>images/loading.gif" />'); }); </script> To me it is much better than set_include_path() but works in the same premise