It says the chat logs are written in .html. When I go to look at the logs I
get an internal server message.. Now when I looked to see if it had written
any files it did.. But in .php. I can manually change them to .html to read
them, but that seems to be a PIA.. I know it work for me a few years ago when
I used an older version..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Where it says the chat logs are written in .html? Maybe html language.
The 500 error you get is due to a server restriction to process files within a
777 chmoded directory.
By the time I developed the log mod, this restriction was not in effect, but
php5 server came with it as default.
I'm not sure if I understood correctly and I can't replicate it on my site (as
this restriction is not in effect on my hosting server). Do you mean that
changing the php extension of th log files into .html is not giving the 500
error and allows you to read the files correctly?
If that's true, this might be a solution for a fix/patch in the next versions.
But I need a confirmation first.
PS: Can I have a link and access to the logs? (privatel, of course)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The 500 internal server error happens because your PHP server is running under
CGI with suEXEC support, which is a very good thing - it's the most safe way
to run php scripts on a server.
The problem is that this mode does not require for 777/666 writing permissions
anymore (which is great), but also doesn't allow these permisions to be
written/read from the server.
The current approach to logs in phpMyChat (up to 1.93) is for PHP servers run
as Apache modules.
I will need to rethink this entire approach in order to make it compatible
with the CGI mod. It would be great if I will be able to keep the old way
working too (for compatibility sake).
We'll see.
PS: I am open to any suggestions from other people, either here or by email.
Thanks for raising it up.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just installed Plus 1.93
It says the chat logs are written in .html. When I go to look at the logs I
get an internal server message.. Now when I looked to see if it had written
any files it did.. But in .php. I can manually change them to .html to read
them, but that seems to be a PIA.. I know it work for me a few years ago when
I used an older version..
Hi th,
Where it says the chat logs are written in .html? Maybe html language.
The 500 error you get is due to a server restriction to process files within a
777 chmoded directory.
By the time I developed the log mod, this restriction was not in effect, but
php5 server came with it as default.
I'm not sure if I understood correctly and I can't replicate it on my site (as
this restriction is not in effect on my hosting server). Do you mean that
changing the php extension of th log files into .html is not giving the 500
error and allows you to read the files correctly?
If that's true, this might be a solution for a fix/patch in the next versions.
But I need a confirmation first.
PS: Can I have a link and access to the logs? (privatel, of course)
Ok, I investigated a bit more this issue.
The 500 internal server error happens because your PHP server is running under
CGI with suEXEC support, which is a very good thing - it's the most safe way
to run php scripts on a server.
The problem is that this mode does not require for 777/666 writing permissions
anymore (which is great), but also doesn't allow these permisions to be
written/read from the server.
The current approach to logs in phpMyChat (up to 1.93) is for PHP servers run
as Apache modules.
I will need to rethink this entire approach in order to make it compatible
with the CGI mod. It would be great if I will be able to keep the old way
working too (for compatibility sake).
We'll see.
PS: I am open to any suggestions from other people, either here or by email.
Thanks for raising it up.
One more hint for you: try and CHMOD all foders that are 777 to 755 and files
that are 666 to 644.
This might temporary fix this for you.