Need Help php error

[ddeswal293]

Hi,i am new here i need help
i made a script it works fine for some days but today when i open my site it give me a error

Warning: include() function.include]: open_basedir restriction in effect. File(/usr/local/apache/htdocs/54353.php) is not within the allowed path(s): (/home/:/tmp) in <b>/home/ddeswal2/public_html/index.phpon line 81

Warning: include(/usr/local/apache/htdocs/54353.php) function.include]: failed to open stream: Operation not permitted in /home/ddeswal2/public_html/index.php on line 81

Warning: include() [function.include]: Failed opening '/usr/local/apache/htdocs/54353.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/ddeswal2/public_html/index.php on line 81

i added this code to my index.php
<?php
include $_SERVER['DOCUMENT_ROOT'] . '/54353.php';
?>

[bhupendra2895]

<?php
include $_SERVER['DOCUMENT_ROOT'] . '/54353.php';
?>

Change it to this, if file resides in public_html folder

<?php 
 include '/home/ddeswal2/public_html/54353.php';
 ?>

And you can simply do this too

<?php 
 include '54353.php';
 ?>

[essellar]

And you can simply do this too

<?php 
 include '54353.php';
 ?>

... if and only if the page in question resides in the root directory -- and, let's face it, if you have documents of multiple types (or multiple categories of documents) and they all appear to be in the same directory, your URLs will wind up being far from friendly.

Requiring us to hard-code our public HTML directory is an unfortunate misconfiguration decision IMHO. We were, until recently, able to use $_SERVER["DOCUMENT_ROOT"] to point to the public HTML directory for our accounts, and that is the only sane way to set up a shared server. The PHP you write should require the minimum possible amount of configuration to move from server to server, and with this move we are being forced to hardcode a path to even get to a configuration file. Not very user (or developer) friendly.

[bhupendra2895]

Requiring us to hard-code our public HTML directory is an unfortunate misconfiguration decision IMHO. We were, until recently, able to use $_SERVER["DOCUMENT_ROOT"] to point to the public HTML directory for our accounts, and that is the only sane way to set up a shared server. The PHP you write should require the minimum possible amount of configuration to move from server to server, and with this move we are being forced to hardcode a path to even get to a configuration file. Not very user (or developer) friendly.

I thought that $_SERVER["DOCUMENT_ROOT"] can't be available in shared hosting therefore this weird error (in bold text inside quote)was generated.

Warning: include() [function.include]: Failed opening '/usr/local/apache/htdocs/54353.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/ddeswal2/public_html/index.php on line 81

It is really unfortunate because it will require more amount of configuration.Is this not available because php is not installed here as apache's module?

[leafypiggy]

Fairly certain $_SERVER[]; is enabled.. It looks like the OP was using something like XAMPP to code on his home server and hardcoded the path..

OP:

What server are you on?

[DeadBattery]

@leafypiggy: Starka

@ddeswal293: where is 54353.php in relation to index.php ?

[dlukin]

Fairly certain $_SERVER[]; is enabled.. It looks like the OP was using something like XAMPP to code on his home server and hardcoded the path..

Yes, it is enabled.

And bhupendra2895 is right. When you guys fiddled with the settings,
$_SERVER[ 'DOCUMENT_ROOT' ]is now set to '/usr/local/apache/htdocs'
for everybody. It does not point to '/home/cPanelUsername/public_html' like it did before.

It is the same problem that now requires any mod_rewrite code to use
RewriteBase / in order to function properly.

[leafypiggy]

Yes, it is enabled.

And bhupendra2895 is right. When you guys fiddled with the settings,
$_SERVER[ 'DOCUMENT_ROOT' ]is now set to '/usr/local/apache/htdocs'
for everybody. It does not point to '/home/cPanelUsername/public_html' like it did before.

It is the same problem that now requires any mod_rewrite code to use
RewriteBase / in order to function properly.

You should be defining your rewrite base anyways.

[dlukin]

You should be defining your rewrite base anyways.

Well, when Staff fiddled with the settings they broke a lot of scripts. Which is funny because one of the reasons cited for not upgrading Python/PHP versions has been that it would "break existing scripts".

[leafypiggy]

How do you know, and when did we "fiddle" with scripts?