Executing scripts in just <? 1

[csteinhilber]

I have a lot of legacy scripts that were originally coded in what I suppose could be termed "shorthand"... like:

<?
   // phpscript here
?>

or

<?= $outputSomeVar ?>

rather than the more succinct

<?PHP
   // phpscript here
?>

and

<?PHP echo($outputSomeVar) ?>

They worked just fine on our Apache/PHP installs for years.

I've since switched development machines, and used WAMP (for the first time) to install my dev servers, rather than doing it all manually. Which was terrific... except now none of the shorthand code works anymore. Script blocks only work if they're in <?PHP.

First, how do I reconfig my dev server to interpret blocks with just the <? shabang.

And second, is there a reason why WAMP wouldn't already be configured to do this? I mean... beyond it being best practice to always use the PHP nomenclature. Any security issues or anything else that would make it worth the effort to convert all our existing scripts to abide by these practices?


-Carl

 

[jpadie]

open php.ini
add this line if it is not there:

short_open_tag = On

if it is there then make sure that it is uncommented and set to "On"

save and close the file

if you are using php as a sapi module, you will need to restart your web server.

if you are using php as a cgi in a hosted and shared environment, you may be able to load just a local php.ini into the folder in which your script resides

 

[csteinhilber]

Thank you, jpadie! That worked like a charm.

Trying to find it on my own was driving me a little nuts (you try to Google "<?" )

Anyway... is there any reason why one would need/want to keep short_open_tag = Off? Is it best practice to enforce the use of... well... long_open_tags? Or is the option there simply to help make sure PHP doesn't step on scripts in other languages, etc?

Thanks again!



-Carl

 

[jpadie]

i believe it's the latter. in particular the combination of xml and php would create a hiccup with short open tags. consider running

<? xml version...

through a php parser...

there may be other languages that create a conflict too.