Hello guys!
I’ve have difficulty running php scripts on my newly installed suse 10.1. I have already done the ff.
-Installed all packages of apache2 using Yast.
-Installed all modules and extensions of php5 using Yast.
-Installed mysql package using Yast.
-Checked and verified php5 included in the apache2 config files using command: httpd2 -D DUMP_MODULES.
But when I tried to open my php script using firefox and konqueror, the “open with” window appeared. Please help me!
Some things that may be obvious, or not.
You have to go through the webserver, you won’t get PHP interpreted if you go to
file:///some/path/file.php
The file suffix should be .php of course, and not upper case.
Did you reload the Apache server? Anytime you add a module you have to do this.
Also I hope you are not using the short tags: <? … ?> by any chance?
You should switch to <?php … ?>.
Thanks for the reply!
I have tried all your suggestions, I checked the runlevel services and apache2 is running. I’ve reinstalled all php5 files from cd and checked apache2 modules php5 is included.
I downloaded live codes from the net and tried to open it with firefox but the “Open with…” message appeared.
I downloaded live codes from the net and tried to open it with firefox but the “Open with…” message appeared.
Two things here.
What do you mean by “downloaded live codes”?
Secondly, you must view the page via Apache not directly from the file system. In other words, open Firefox, and type in http://localhost
You should get the apache welcome page. Next try your php page, which will be http://localhost/some/path/to/your/page.php
Thanks!
I mean, I used a php script that I downloaded and is sure to be running. I tried http://localhost/..path../myfile.php - the output on firefox - error loading the page (something like that.) and when I click the message to check the server …the output is “It works”, nothing else.
I’ll try this again with a simple script and store it on htdocs. I’ll inform you tomorrow. I’m signing out already. Thanks for your time again GransRemedy.
Hello!
I’ve tried to save my scripts on /srv/www/htdocs and open at http://localhost/myscript.php and it ran(Finally!). However when I tried to open by: http://localhost/srv/www/htdocs/myscript.php, “unable to load object!” came out. And also when I tried to run the php2sms.php(I downloaded from m3lin.org), and open at http://localhost/php2sms.php,it did not compile- the source code was displayed instead. Do I have to configure something else?
http://localhost/srv/www/htdocs/myscript.php isn’t going to work because the top of the document directory is /srv/www/htdocs. It would be very dangerous if everything on the computer could be accessed by the web, crackers would ask for http://localhost/etc/passwd. 
http://localhost/myscript.php is the correct way of viewing your pages, but they must be in the directory specified in Apache’s document root.
I’ve not used PHP2SMS before, however if you are seeing php code in your page, then this usually means that the script has not used the open/close tags properly (since your other page worked ok we know PHP itself is working fine).
According to m3rlin.org, PHP2SMS just sends your message to your mobile phone provider’s website (which then puts it onto the phone network) - so you need to make sure that you can send a message using their website first, then try that script.
Good luck
ken yap wrote:
>
> http://localhost/srv/www/htdocs/myscript.php isn’t going to work because
> the top of the document directory is /srv/www/htdocs. It would be very
> dangerous if everything on the computer could be accessed by the web,
> crackers would ask for http://localhost/etc/passwd.
>
>
Wait?!? It doesn’t work like that? I’m going to have to rethink my entire
strategy for world domination! Drat! ncurses! I was requesting
http://localhost/etc/shadow though, I’m not stupid!
{Chuckle}
Loni
–
L R Nix
lornix@lornix.com
Unfortunately /etc/shadow doesn’t even have world read permission, so Apache couldn’t read it. But with /etc/password at least you can reduce the amount of guessing.
Yes I know it’s all in jest. 
It’s just to point out to the OP that there are good reasons why some things are they way they are.