Re: [PHP] desk top interactive environment
On Tue, Apr 10, 2012 at 9:38 AM, Kirk Bailey wrote: > Php would (IMHO) benefit from an interactive desktop application where you > can test and experiment with code interactively, instead of "edit, dsave, > run, view webpage result, edit... php -a gives you an interactive environment in which you can test code. > Python has this; why not php? Python and PHP are programming languages. That interactive environment your referring (IDLE) to is a tool separate from the programming language that just happens to be distributed with the windows version of the installation package. It's not part of Python. I think that the features in IDLE are probably duplicated by several different PHP IDEs. There are probably several alternatives to IDLE available. There might even be an IDE that does code testing and debugging for both languages better than IDLE does. I'm sorry I can't provide more specific examples. I've found that Vim suits me better in the development environment than any IDE. -- Vince Aggrippino Ghodmode Development http://www.ghodmode.com > -- > end > > Very Truly yours, > - Kirk Bailey, > Largo Florida > > kniht > +-+ > | BOX | > +-+ > think -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Нужны памперсы
I'll be damned! Russian spam. Use Google translate if you want to, then please ban this idiot. -- Vince Aggrippino Ghodmode Development http://www.ghodmode.com 2012/3/5 Deti > Детям требуется Ваша помощь! -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Arrays: Comma at end?
On Wed, Feb 8, 2012 at 4:10 AM, Ashley Sheridan wrote: > On Tue, 2012-02-07 at 11:50 -0800, Micky Hulse wrote: > >> Was there ever a time when having a comma at the end of the last array >> element was not acceptable in PHP? ... > It's fine in PHP, and some coding practices actually encourage it, for > example: ... > > It's easy to add and remove elements without making sure you have to > check the trailing comma. It's also OK in Javascript to use the trailing > comma, as long as you don't mind things not working on IE, which is the > only browser that has issues with it. As far as PHP goes though, it's > fine. I believe this behavior was inherited from Perl. I used Perl before I used PHP and it was considered a feature for exactly the reason Ash gave. I think that problems with Perl may have originally inspired the creation of PHP, at least in part. But they kept the good parts. This is just my perception. To confirm it, I'd have to ask our BDFL :) -- Vince Aggrippino a.k.a. Ghodmode http://www.ghodmode.com > -- > Thanks, > Ash > http://www.ashleysheridan.co.uk > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Continued Problems Accessing *.php.net?
I don't know what all the fuss was about. What's wrong with you people. That document has been there for so many years... you should have memorized it by now! -- Ghodmode http://www.ghodmode.com On Tue, Jan 24, 2012 at 7:22 AM, Daniel Brown wrote: > ALL: > > As you may have noticed, early this morning we got bored and > decided to delete php.net from the Internet. After getting an > estimated sixteen-point-four trillion complaints, we became > overwhelmed and aggravated by your incessant need to RTFM that we > pressed CTRL+Z and brought it back. You're welcome. > > In earnest, a catastrophic failure on one of our systems coincided > with a migration effort being headed by some very talented folks. > This led to a domino effect of issues that resulted in a temporary - > but widespread - impact on the online version of the documentation and > downloads. Things are nearly back to "normal" now across the network > --- or so it seems. If you come across any issues on your favorite > *.php.net mirror, please let us know at https://bugs.php.net/ or via a > reply to this thread and we'll check it out. > > As a result, a list of the top ten reasons PHP had an outage today: > > 10.) We installed an experimental PECL module named "Invisible Ink." > 9.) We learned our indoor solar panels don't work when the > lights get turned off. > 8.) We had our mobile bandwidth slowed to a crawl because we > exceeded 2GB for the month. > 7.) A Groupon swarm for two free downloads for the price of > one killed our network. > 6.) We whited out this time to protest another > Patriots/Giants Superbowl, while the BC Lions never even got a phone > call. > 5.) Our build of mod_expires runs on the Mayan calendar, and > attempting to do a 60-day expire segfaulted. > 4.) The $25.90 check we wrote to cover the server's AOL > dial-up bounced. > 3.) It's Chinese New Year, but it was too cold to set off the > fireworks outside today, so sorry. > 2.) As it turned out, all our base truly were belong to them. > 1.) We needed 7,500,001 signatures on the petition against SOPA/PIPA. > > Thanks to all for your patience and such. And, of course, apologies to > all. > > -- > > Network Infrastructure Manager > http://www.php.net/ > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] which server variables from this list can be spoofed?
On Fri, Jan 20, 2012 at 10:07 AM, Haluk Karamete wrote: > I marked those I already know as "can", > > $_SERVER['REMOTE_ADDR'] CAN > $_SERVER['HTTP_REFERER'] CAN > $_SERVER['HTTP_USER_AGENT'] CAN > $_SERVER['REQUEST_URI'] CAN ( cause it contains the query string > part and user/hacker can easily change that ) > > Those I'm not too sure are as follows; > > $_SERVER['SERVER_NAME'] > $_SERVER['DOCUMENT_ROOT'] > $_SERVER['SCRIPT_NAME'] > $_SERVER['PHP_SELF'] All of 'em. However, SERVER_NAME, DOCUMENT_ROOT, and SCRIPT_NAME come from the server, so it would have to be whoever controls the server doing the spoofing. PHP_SELF could probably be faked in the code if done creatively. Naturally, no one would try to do this intentionally, but I wonder if something mischievous could be done with this if code was included from an external source. -- Ghodmode http://www.ghodmode.com/blog -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Intentionally generate an "Internal Server Error"
On Mon, Aug 8, 2011 at 11:35 AM, Kirk Bailey wrote: > Access a non existant file. Woops! > That's a 404, not a 500.
Re: [PHP] Intentionally generate an "Internal Server Error"
On Sun, Aug 7, 2011 at 12:38 PM, shiplu wrote: > By the way, You can also try sending proper html page and http header that > will copy the Internal Server Error. > That is completely possible in php. > Just use the header() function. > Actually, I learned from reading a previous message on this list (Subject: "php causes HTTP 500, but results in blank page in apache"), that using header() would require me to provide the content of the error page. That probably should still put a message in the error log, but it wouldn't be enough to convince the stupid tech support people at GoDaddy that it was an error. I want them to see their own error page and then fix the problem with the logging. -- > Shiplu Mokadd.im > My talks, http://talk.cmyweb.net > > Follow me, http://twitter.com/shiplu > Innovation distinguishes between follower and leader > -- Ghodmode http://www.ghodmode.com/blog
Re: [PHP] Intentionally generate an "Internal Server Error"
On Sun, Aug 7, 2011 at 12:05 PM, shiplu wrote: > One way would be, write a php extension and perform segfaults there. > Unfortunately, I don't know how to write an extension or intentionally perform a segmentation fault. If I did know how to intentionally perform a segmentation fault, wouldn't that be enough to generate a 500 error in a single php file without needing to be in an extension? -- > Shiplu Mokadd.im > Follow me, http://twitter.com/shiplu > Innovation distinguishes between follower and leader > Thank you. -- Ghodmode http://www.ghodmode.com/blog
[PHP] Intentionally generate an "Internal Server Error"
I'd like to use PHP to intentionally generate an "Error 500 Internal
Server Error".
Here's the problem. My site has this error intermittently and I'd
like to monitor the error log to figure out the problem.
Unfortunately, I don't get to see the actual Apache error log and my
hosting provider's error reporting system isn't working. Customer
support just sends me canned responses stating that everything's fine
and they can't reproduce the error, so I'd like to create a
reproducible internal server error so that they can see that it's not
showing up in the error log.
I know that I can mess up something in the .htaccess file, but that
would break the whole site. I don't want to do that.
I know I could use header("HTTP/1.1 500 Internal Server Error"), but
that means I would also have to provide the content of the Error 500
page. I want to kick off they're internal server error page. They
don't give me to option to create one of my own.
I'm using GoDaddy.
Can someone suggest some invalid PHP code that should generate an
internal server error?
Thank you.
--
Ghodmode
http://www.ghodmode.com/blog
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] PHP live chat
I've played around with CraftySyntax LiveHelp, but I haven't deployed it in a production environment. It definitely looks like it's worth a try, though. http://www.craftysyntax.com/ On 14/12/09 21:14, Angelo Zanetti wrote: Hi all, I know there are a lot of scripts that one can pay for, for "live chat" - website support. Are there are any free open source ones that work well? I found: www.phplivechat.com But still waiting to evaluate it. Please send you comments, good or bad and what you would recommend or not recommend and why Thanks in advance. Angelo http://www.wapit.co.za http://www.elemental.co.za -- *Vince Aggrippino* a.k.a. Ghodmode www.ghodmode.com <http://www.ghodmode.com>
