We're setting up a webserver w. RHEL 4.1 and PHP 4.3. I'm sure there
is a setting somewhere that's been confounding me. When I create a
file "test.php" and insert:
phpinfo();
?>
It displays as expected in the browser but when the file is reopened
from the server to be edited, the file contains the output from the
phpinfo() call rather then the three lines of code above. Anyone have
ideas as to why this is happening?
On Aug 8, 11:13 am, swiftfal...@gmail.com wrote:
> We're setting up a webserver w. RHEL 4.1 and PHP 4.3. I'm sure there
> is a setting somewhere that's been confounding me. When I create a
> file "test.php" and insert:
>
> phpinfo();
> ?>
> It displays as expected in the browser but when the file is reopened
> from the server to be edited, the file contains the output from the
> phpinfo() call rather then the three lines of code above. Anyone have
> ideas as to why this is happening?
What do you mean by "reopened from the server" ? How are you opening
the file?
On Aug 8, 12:14 pm, ZeldorBlat
> On Aug 8, 11:13 am, swiftfal...@gmail.com wrote:
>
> > We're setting up a webserver w. RHEL 4.1 and PHP 4.3. I'm sure there
> > is a setting somewhere that's been confounding me. When I create a
> > file "test.php" and insert:
> >
> > phpinfo();
> > ?>
> > It displays as expected in the browser but when the file is reopened
> > from the server to be edited, the file contains the output from the
> > phpinfo() call rather then the three lines of code above. Anyone have
> > ideas as to why this is happening?
>
> What do you mean by "reopened from the server" ? How are you opening
> the file?
I'm opening it with Notebook++, a simple source code editor
On Aug 8, 10:13 am, swiftfal...@gmail.com wrote:
> We're setting up a webserver w. RHEL 4.1 and PHP 4.3. I'm sure there
> is a setting somewhere that's been confounding me. When I create a
> file "test.php" and insert:
>
> phpinfo();
> ?>
> It displays as expected in the browser but when the file is reopened
> from the server to be edited, the file contains the output from the
> phpinfo() call rather then the three lines of code above. Anyone have
> ideas as to why this is happening?
if you use 'php test.php' to "re-open" the file, it will output the
content generated by the php script, but if you edit test.php with 'vi
test.php' or something of the sort, you should see the code you
entered previously instead of the generated info.
On Aug 8, 1:20 pm, dkruger
> On Aug 8, 10:13 am, swiftfal...@gmail.com wrote:
>
> > We're setting up a webserver w. RHEL 4.1 and PHP 4.3. I'm sure there
> > is a setting somewhere that's been confounding me. When I create a
> > file "test.php" and insert:
> >
> > phpinfo();
> > ?>
> > It displays as expected in the browser but when the file is reopened
> > from the server to be edited, the file contains the output from the
> > phpinfo() call rather then the three lines of code above. Anyone have
> > ideas as to why this is happening?
>
> if you use 'php test.php' to "re-open" the file, it will output the
> content generated by the php script, but if you edit test.php with 'vi
> test.php' or something of the sort, you should see the code you
> entered previously instead of the generated info.
You're corrent that through vi I do see the code. I'm starting to
think this may be a WebDAV issue.
On Aug 8, 12:43 pm, swiftfal...@gmail.com wrote:
> On Aug 8, 1:20 pm, dkruger
>
>
>
>
>
> > On Aug 8, 10:13 am, swiftfal...@gmail.com wrote:
>
> > > We're setting up a webserver w. RHEL 4.1 and PHP 4.3. I'm sure there
> > > is a setting somewhere that's been confounding me. When I create a
> > > file "test.php" and insert:
> > >
> > > phpinfo();
> > > ?>
> > > It displays as expected in the browser but when the file is reopened
> > > from the server to be edited, the file contains the output from the
> > > phpinfo() call rather then the three lines of code above. Anyone have
> > > ideas as to why this is happening?
>
> > if you use 'php test.php' to "re-open" the file, it will output the
> > content generated by the php script, but if you edit test.php with 'vi
> > test.php' or something of the sort, you should see the code you
> > entered previously instead of the generated info.
>
> You're corrent that through vi I do see the code. I'm starting to
> think this may be a WebDAV issue.- Hide quoted text -
>
> - Show quoted text -
It could be the notepad++ program, I am personally not familiar with
that, however, if you are accessing the file through windows (i
assume) for viewing/editing, likely using the URL for the file to open
it, then the server is executing the script as though a web browser
requested it and is sending the output of the script...just my guess.
If you run some sort of editing program on your server, to make the
changes, probably the issue would not occur.
On Aug 8, 2:24 pm, dkruger
> On Aug 8, 12:43 pm, swiftfal...@gmail.com wrote:
>
>
>
> > On Aug 8, 1:20 pm, dkruger
>
> > > On Aug 8, 10:13 am, swiftfal...@gmail.com wrote:
>
> > > > We're setting up a webserver w. RHEL 4.1 and PHP 4.3. I'm sure there
> > > > is a setting somewhere that's been confounding me. When I create a
> > > > file "test.php" and insert:
> > > >
> > > > phpinfo();
> > > > ?>
> > > > It displays as expected in the browser but when the file is reopened
> > > > from the server to be edited, the file contains the output from the
> > > > phpinfo() call rather then the three lines of code above. Anyone have
> > > > ideas as to why this is happening?
>
> > > if you use 'php test.php' to "re-open" the file, it will output the
> > > content generated by the php script, but if you edit test.php with 'vi
> > > test.php' or something of the sort, you should see the code you
> > > entered previously instead of the generated info.
>
> > You're corrent that through vi I do see the code. I'm starting to
> > think this may be a WebDAV issue.- Hide quoted text -
>
> > - Show quoted text -
>
> It could be the notepad++ program, I am personally not familiar with
> that, however, if you are accessing the file through windows (i
> assume) for viewing/editing, likely using the URL for the file to open
> it, then the server is executing the script as though a web browser
> requested it and is sending the output of the script...just my guess.
> If you run some sort of editing program on your server, to make the
> changes, probably the issue would not occur.
Thanks for the advice but what it ended up is that the line "ForceType
text/plain" was missing from our conf file. So the code was being
preprocessed.
On Aug 8, 5:04 pm, swiftfal...@gmail.com wrote:
> On Aug 8, 2:24 pm, dkruger
>
>
>
> > On Aug 8, 12:43 pm, swiftfal...@gmail.com wrote:
>
> > > On Aug 8, 1:20 pm, dkruger
>
> > > > On Aug 8, 10:13 am, swiftfal...@gmail.com wrote:
>
> > > > > We're setting up a webserver w. RHEL 4.1 and PHP 4.3. I'm sure there
> > > > > is a setting somewhere that's been confounding me. When I create a
> > > > > file "test.php" and insert:
> > > > >
> > > > > phpinfo();
> > > > > ?>
> > > > > It displays as expected in the browser but when the file is reopened
> > > > > from the server to be edited, the file contains the output from the
> > > > > phpinfo() call rather then the three lines of code above. Anyone have
> > > > > ideas as to why this is happening?
>
> > > > if you use 'php test.php' to "re-open" the file, it will output the
> > > > content generated by the php script, but if you edit test.php with 'vi
> > > > test.php' or something of the sort, you should see the code you
> > > > entered previously instead of the generated info.
>
> > > You're corrent that through vi I do see the code. I'm starting to
> > > think this may be a WebDAV issue.- Hide quoted text -
>
> > > - Show quoted text -
>
> > It could be the notepad++ program, I am personally not familiar with
> > that, however, if you are accessing the file through windows (i
> > assume) for viewing/editing, likely using the URL for the file to open
> > it, then the server is executing the script as though a web browser
> > requested it and is sending the output of the script...just my guess.
> > If you run some sort of editing program on your server, to make the
> > changes, probably the issue would not occur.
>
Thanks for the advice but what it ended up is that the line "ForceType
text/plain" was missing from our conf file. So the code was being
preprocessed.
So basically it was an issue with WebDAV missing that one line
directive.