I have to admit... I am concerned with the lack of discussion on this topic that clearly seems to affect many of us. Specifically, the lack of addressing this known bug/problem by the ez staff. Is anyone watching these threads??
Information on running PHP as CGI can be found at:
http://www.php.net/manual/en/security.cgi-bin.php
Note that this isn't too uncommon; as Tray notes, many of us face this on virtual hosting environments.
To be frank, at the end of the day I couldn't, despite many hours invested, solve this issue. I've installed an alternate CMS to manage my personal site as it was sufficient, in most ways, for the job. I still use ezpub on sites for clients as I can install 3.x on my company's dedicated host.
It is unfortunate that this has not been solved, as I, too, have switched to an alternate CMS, and can not in the foreseeable future see changing to EZ, given the time sink in setting up a website. I was at a pivotal point in my client architecture/changeover system, which would have made a switch to an alternate CMS doable.... That point has passed now - and I, unfortuantely, see EZPublish in the rear view mirror... as I move forward....
It's sad... I was hoping to utilize this system as I had heard such great things about it.
I think it's unfortunate when developers chose to censor a problem rather than fix it.
History has proven that it is not healthy for an web application, or any other application for that matter, to take a position of telling end users to change their systems instead of working for wide scope compatibility.
PHP in CGI mode is actually not all that uncommon that it shouldn't be addressed here. Furthermore, the only link I could find to a patch (your link above) which could provide a starting point for fixing this problem has been removed from the forums.
All in all this is very frustrating.
The past is past and cannot be changed, while the future is shaped by action taken in the present.
You must be logged in to post messages in this topic!
