PHP Idea: Useful or Not?

[sparkele]

When using some webservers that you aren't 100% sure that you will be using in the future, how about inserting a print code for each link, directory, and image and including addresses in a .inc file.
Example:

<?php 
###############
#addresses.inc#
###############
$logo = "http://www.yosite.com/images/logo.gif";
?>

And if you change domains or directories..

<?php
######################
#a few weeks later...#
######################
$logo ="http://www.mysite.com/new/site4/img/logo.gif";
?>

Then you would put that into an HTML file like so:

<IMG SRC="<?php print($logo); ?>

This would prevent long and tedious re-coding, and since my sites arent all dynamic yet, this seems like a good idea. Give me your opinion.

[someonewhois]

Better:

<?php
$IMAGE_PATH = "http://mydomain.com/images/";
$URL_PATH = "http://mydomain.com/";

Then call it:

<IMG SRC="<?=$IMAGE_PATH?>logo.gif">

[Zoef]

eh... why not just use relative url's?

[philm]

Because that would be too easy for the coding geeks

What would they have to fiddle with then?

[tfountain]

Yup:

<img src="/images/logo.gif">

Easy .

[Technosailor]

easy but not always the best way. config.php files with all the variables are some of the best ideas around. Also, if you're creating a dstributable app, this is useful. Most bulletin board software uses a similar technique.

Aaron

[sparkele]

The only problem was that my whole point was to make it easy to change an image's or other document's location if I ever had to move, changed web addresses, or changed file directory structure. In response to someonewhois, I would have to change every single page if I changed even one file or directory. That would totally elminate the purpose.