"case" question.

[Otikeu]

Hello,

I'm still new at PHP programming, so bare with me if you can. What I'm tring to do is have the case command ...

case "page.php": $variable = "data for page.php only"; break;

to work on .php pages. In that past, I have been using case commands for such urls as http://www.domain.com/page.php?id=contentpage but wish to use case commands on these types of urls: http://www.domain.com/page.php.

How would I go about setting this up? I basically am using .php pages only (no "page.php?id=contentpage" stuff) and want to use case commands to change certain variable data depending on the .php page they are viewing.

Thank you for your time.

[Rodney_H_]

Have you checked out the manual? http://us2.php.net/switch

[Otikeu]

yes, but am still confused on how to use such things as

case "page.php": $variable = "data for page.php only"; break;

as the ones you mentioned where different, but still helpful in my learning process. So thank you.

However, I still am seeking a solution. Anyone else?

[LoganK]

I think he's trying to accomplish something like: write a PHP script which can determine the difference between if the user is viewing page.php versus page2.php and display the appropriate content.

Unfortunately, this isn't possible. Just put the content into the pages separately to begin with.

[Roger_Ramjet]

You mean, I think, that you want a function to know which page it is being used within. Then you need the Predefined variables

A simple case would be where the function is in a script that has been included into another script that the user requested

eg: user requested http://yourdomain.com/page1.php which has an include for a general purpose menu formatting script that needs to be context sensitive (a duff example I know but it will get the idea across)

$page_link = $_SERVER['REQUEST_URI'];
switch $page_link {
case "page1.php":
   include 'page1_menu.php';
   break;
case "page2.php:
   include 'page2_menu.php';
   break;
}

You should read the manual about the various options and relate them to your own situation, and pay particular attention to the user notes at the bottom.