Fatal Error after transfer to new host

T_Varnell

Greetings all!

My website just migrated to a new hosting service. However when I try to view the temporary site, I get the following error:

Warning: require_once(/home/cdmfun5/public_html/index.php/includes/lib/db.inc.php) [function.require-once]: failed to open stream: Not a directory in /home/cdmfun5/public_html/includes/config.inc.php on line 54

Fatal error: require_once() [function.require]: Failed opening required '/home/cdmfun5/public_html/index.php/includes/lib/db.inc.php' (include_path='.:/home/cdmfun5/public_html/index.php:/home/cdmfun5/public_html/index.php/siteadmin:/usr/lib/php:/usr/local/lib/php') in /home/cdmfun5/public_html/includes/config.inc.php on line 54

I'm lost. I barely write PHP and cannot understand why a straight transfer of code and db causes a fatal error.

The code is below (with sensitive information replaced with XXXXXXXXX)

<?php

//web frontend configuration
$sitedomain = "www.cdmfun.org";

if (!isset($root)) {
	list($root) = explode($_SERVER['PHP_SELF'], $_SERVER['SCRIPT_FILENAME']);
}
$libpath = "$root/includes/lib";

//widget frontend configs
$fileuploadfolder = "/uploadedfiles";
$newsimagedir = $fileuploadfolder;
$articlesimagedir = $fileuploadfolder;
$staffimagedir = $fileuploadfolder;
$fanofmonthimagedir = $fileuploadfolder;
$paypalimagedir = $fileuploadfolder;
$listingsimagedir = $fileuploadfolder;
$vacancyimagedir = $fileuploadfolder;
$cafeeventsimagedir = $fileuploadfolder;
$booksimagedir = $fileuploadfolder;
$navigationimagedir = $fileuploadfolder;
$securefileuploaddir = "$root/../secure-upload";

//form config
$__use_form_message = TRUE;


//database connection Items
#$host= "psqlhost";
#$dbusername= "XXXXXXXXX";
#$dbpassword= "XXXXXXXXXXX";
#$dbname = "webtools_live_cdm";

$host= "localhost";
$dbusername= "XXXXXXXXXXXX";
$dbpassword= "XXXXXXXXXXXX";
$dbname = "XXXXXXXXXXX";

$__query_cache_timeout = 60;

$DBTYPE = 'PG8';
$DBHOST = $host;
$DBUSER = $dbusername;
$DBPASS = $dbpassword;
$DATABASE = $dbname;

require_once("$libpath/db.inc.php");

$PAYMENT_GATEWAY = "Authorize.Net";

// Authorize.Net config
$AUTHNET_LOGIN_ID = "XXXXXXXXXXXX";
$AUTHNET_TRANS_KEY = "XXXXXXXXXXXXX";

//widget Display names
$widgetnamelookup = array(
  "articles" => "Useful Articles",
  "growler"  => "Growler Club",
  "links"    => "Related Links",
  "news"     => "News Events",
  "paypal"   => "Available Products",
  "staff"    => "Our Staff",
  "Vendors"  => "Vendors and Distributors",
  "business-listings" => "Business Listings",
  "events"   => "Events Calendar",
  "vacancies" => "Current Vacancies",
  "pages-navigation" => "Pages",
  "file-upload" => "Files",
);

//Search Configuration
$numberofresultsperpage = 999999;
$searchresultsviewpage = array(
  "articles" => "/test.php",
  "news"     => "/test.php",
  "paypal"   => "/test.php",
  "staff"    => "/test.php",
  "business-listings" => "/test.php",
  "events" => "/test.php",
  "vacancies" => "/test.php",
  "pages-navigation" => "/test.php",
);

//WYSIWYG Configuration
if(strpos($_SERVER['REQUEST_URI'], '/siteadmin/') !== FALSE) {
	require_once("$root/includes/JSON.php");
	$json = new Services_JSON(SERVICES_JSON_LOOSE_TYPE);
	$wysiwyg_options = array(
		'mode'										=>		"textareas",
		'editor_selector'							=>		"mceEditor",
		'theme'										=>		"advanced",
		'plugins'									=>		"imagemanager,spellchecker,advlink",
		'theme_advanced_toolbar_align'		=>		"left",
		'theme_advanced_toolbar_location'	=>		"top",
		'content_css'								=>		"/css/for-admin.css",
		'theme_advance_buttons3_add'			=>		"spellchecker",
		'spellchecker_languages'				=>		"+English=en",
		'relative_urls'							=>		'true',
		'document_base_url'						=>		'',
		'gecko_spellcheck'						=>		'true',
		'apply_source_formatting'				=>		'true',
		'cleanup_on_startup'						=>		'true'
	);

// For table controls in the wysiwyg, uncomment the following lines
$wysiwyg_options['plugins'] .= ',table';
$wysiwyg_options['theme_advanced_buttons3_add'] .= ',tablecontrols';

$wysiwyg_options['theme_advanced_blockformats'] .= 'h3,h4,p,div,blockquote';

$wysiwyg_options['extended_valid_elements'] .= 'form[accept|accept-charset|action|class|dir<ltr?rtl|enctype|id|lang|method<get?post|name|onclick|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|onreset|onsubmit|style|title|target],input[accept|accesskey|align<bottom?left?middle?right?top|alt|checked<checked|class|dir<ltr?rtl|disabled<disabled|id|ismap<ismap|lang|maxlength|name|onblur|onclick|ondblclick|onfocus|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|onselect|readonly<readonly|size|src|style|tabindex|title|type<button?checkbox?file?hidden?image?password?radio?reset?submit?text|usemap|value]';

$wysiwyg_options = $json->encode($wysiwyg_options);
}

?>

bradgrafelman

Welcome to PHPBuilder! When posting PHP code, please use the board's [noparse]

..

[/noparse] bbcode tags as they make your code much easier to read and analyze.

As for your issue... have you defined $root elsewhere before the code above is executed? In other words, while this:

if (!isset($root)) { 
    list($root) = explode($_SERVER['PHP_SELF'], $_SERVER['SCRIPT_FILENAME']); 
}

seems like an error-prone kludge (IMHO) to find the root directory, the paths in your error messages above don't seem to suggest that it would cause any problems... assuming, of course, that if() statement was true and the above code was being executed at all (hence why I asked about $root).

T_Varnell

Hi!

Sorry about not including the tag. I'll be sure to do it in future.

Having slogged through the .inc files I can find, I do not see $root defined anywhere. (I didn't write this. I just took it over.) I'm just really baffled that it worked on the old server but moving it to a new host caused this.

This is probably a stupid question, but is there a reason $root can't just be a set value for whatever my root directory is? The way it's done now seems unnecessarily complicated to me, but I'm a big fan of "the simpler the better." Especially if I end up having to maintain it.

bradgrafelman

T_Varnell;10996277 wrote:
Having slogged through the .inc files I can find, I do not see $root defined anywhere.

You could be sure of this by adding something like:

echo 'DEBUG: isset($root) == ';
var_dump(isset($root));
exit;

just above that if() statement.

T_Varnell;10996277 wrote:
(I didn't write this. I just took it over.) I'm just really baffled that it worked on the old server but moving it to a new host caused this.

While I certainly would have went about doing it a different way, it does seem like the code in the if() statement should work.

To be sure, though could you echo out $SERVER['PHP_SELF'] and $SERVER['SCRIPT_FILENAME'] in that code and show us the output?

T_Varnell;10996277 wrote:
This is probably a stupid question, but is there a reason $root can't just be a set value for whatever my root directory is? The way it's done now seems unnecessarily complicated to me, but I'm a big fan of "the simpler the better." Especially if I end up having to maintain it.

The code is in your hands; you could certainly get rid of that entire if() statement and just assign some constant string value to $root instead, or perhaps change the way that the code detects what the "root directory" path should be.

As an example, I would think using [man]dirname/man followed by [man]realpath/man like so:

$root = realpath(dirname($_SERVER['SCRIPT_FILENAME']));

would be a much more robust way of detecting the absolute path to the directory where the script is located.

T_Varnell

I've made progress, of sorts, thanks to your help. The code

echo 'DEBUG: isset($root) == '; 
var_dump(isset($root));
echo "<br />";
echo $_SERVER['PHP_SELF']; 
echo "<br />";
echo $_SERVER['SCRIPT_FILENAME'];


exit;

returns

DEBUG: isset($root) == bool(true)
/~cdmfun5/index.php
/home/cdmfun5/public_html/index.php

So at least now I know where the stray .index.php are coming from.

One little tiny baby step at a time... (and thanks for helping my first tentative steps)

Ashley_Sheridan

You mentioned that you have to look through a bunch of .inc files. .inc is not an extension which is usually used by PHP, and any new server setup will not have this extension associated with the PHP parser. Check to make sure that this has been done. It could be in one of several places:
in an .htaccess file
in a site-specific .conf file for Apache
* in a global .conf file for Apache

The last two are usually kept somewhere in /etc/httpd or /etc/apache (depending on the distro of Linux that is running on the server)

bradgrafelman

Ashley Sheridan;10996378 wrote:
You mentioned that you have to look through a bunch of .inc files. .inc is not an extension which is usually used by PHP

I have to disagree. ".inc" is a very common file extension (I myself have used it a couple of times in new projects).

And technically, there aren't any file extensions which are "used by PHP" since PHP doesn't care about file extensions at all. If you tell it to parse a file and execute it as PHP, that's what it'll do.

Ashley Sheridan;10996378 wrote:
and any new server setup will not have this extension associated with the PHP parser. Check to make sure that this has been done. It could be in one of several places:
in an .htaccess file
in a site-specific .conf file for Apache
* in a global .conf file for Apache

The last two are usually kept somewhere in /etc/httpd or /etc/apache (depending on the distro of Linux that is running on the server)

I'm guessing none of this is applicable, since the ".inc" files aren't meant to be executed directly but are instead meant to be included by other PHP files.

Ashley_Sheridan

I've seen .inc used a fair bit, but it's not part of any default installation, and is the biggest area where things break when moving to a new server that I've seen, so that's why I mentioned it.

I know any file can be parsed as if it were PHP, and I've seen a lot of people parse .html files just so they can insert PHP into their .html files. Thing is, as it's not part of any default PHP isntallation to process anything other than .php (and sometimes things like .php4, .php5) files, if a config option gets left out, any code in those .inc files is treated as output for the browser, including any sensitive code that you wouldn't want seen.

bradgrafelman

Ashley Sheridan;10996394 wrote:
I've seen .inc used a fair bit, but it's not part of any default installation

It isn't part of mine either, mostly because it doesn't need to be (and, in fact, probably shouldn't be).

Ashley Sheridan;10996394 wrote:
Thing is, as it's not part of any default PHP isntallation to process anything other than .php (and sometimes things like .php4, .php5) files, if a config option gets left out, any code in those .inc files is treated as output for the browser, including any sensitive code that you wouldn't want seen.

But you're still assuming that these ".inc" files were meant to be used directly. I clearly stated that the ".inc" as I know it is quite the opposite; they're only meant to be included by other PHP applications, thus it wouldn't be appropriate to modify your configuration to add the ".inc" file extension.

Furthermore, you're also assuming that these ".inc" files are in a location that is even accessible from the web. In many cases (such as any time I personally have ever used them in a project), this assumption is false.