[Nathan]

If you're looking for examples, usage or info on a PHP function simply go to:

http://php.net/functionname

For example:

http://php.net/echo shows info on the echo function.

[elyk]

Wow. I never knew you could do that. Thanks.

[PresFox]

also


error_reporting(E_ALL); is your friend

[Darkneo]

What is error_reporting(E_ALL);

[PresFox]

your friend



it makes PHP show all errors. normally everything below warning level is ignored, with E_ALL on PHP for instance also shows mistyped variables

[Darkneo]

That will be very useful since I am starting to create very big scripts that can't afford even a small error.

[ghilix]

Nathan & PresFox thanks for the helpful informations,I had a hard time finding informations about some functions this help a lot.

[Haseeb Aslam]

Nice tips
I have got alot of information about functions from this
Thanx for Sharing

[Rune-video]

Whoa! That's pretty cool, I'll have to check it out.

[Abdul]

Can we make proxy server site. Bypass useing like kproxy.com .,vtunnel etc. If yes so where we can get its script?

[Nathan]

There are many scripts that do this, but proxies are strictly forbidden on NovaHost.org accounts.

Also, please keep on topic.

[BHUSHAN]

you can also download PHP manual @ http://php.net/download-docs.php

[BHUSHAN]

 some free debugger extensions:
Xdebug - http://www.xdebug.org
DBG - http://dd.cron.ru/dbg
APD - http://pecl.php.net/apd

[Cbeppe]

You might want to be careful with error reporting, though. It's an invaluable resource when creating scripts, but when you have it all working and it's ready to be put online for someone to use, you should remove it. Hackers can use these warnings and notices to figure out how your scripts work, and you do not want that.

I'll see if I can find the original article.

[BHUSHAN]

Some of the default settings in php.ini in earlier PHP versions are pretty dangerous. Modify the original php.ini if you are a server administrator or create custom php.ini in the webroot (directory of the web documents, accessible to the public via web server) to override the unsafe settings or use in-code functions such as ini_set():

• Disable register_globals and don’t rely on it in your code:
  

  register_globals = Off

  
  
  
• Disable magic quotes and don’t rely on it in your code:
  

  magic_quotes_gpc = Off

  
  
  
• Disable error reporting:
  

  display_errors = Off

  This is for production deployment, otherwise achievable runtime by error_reporting(0). For development and debugging, make sure you turn on the full error reporting in your code by error_reporting(E_ALL) so that you get a full grip of what’s going on with your application.
  
  
• Enable error logging and save the log file to a directory below webroot:
  

  log_errors = On
  ignore_repeated_errors = On
  html_errors = Off
  error_log = /path/below/webroot/logs/php_error_log

  Normally the errors will be displayed to the users / crackers when something goes wrong thus disclosing internal information about your application. Now that we have disallowed them to display publicly, enabling error logging helps capture all PHP errors and store them somewhere the users / crackers cannot access yet we can retrieve and analyze when necessary.
  
  
• Store session data below webroot:
  

  session.save_path = /path/below/webroot/sessions

  In most cases, you don’t have to worry about more than just the error logging part because the most up-to-date version of PHP has been well optimized in security by default. For example, register_globals and magic_quotes_gpc are turned off as factory settings, and session data is automatically stored outside of webroot. Other than these, feel free to override things by the ini_set() function when you feel obligated to.