Contacting the author
If you have exhausted all other means of solving your problem, and you're thinking of emailing me with a personal plea, please don't! I just don't have enough time to answer PHP questions, and whatever you say will simply go unanswered. Sorry!
That said, if you simply have nowhere else to turn, you're welcome to try and get in touch with me on Twitter:
@twostraws. I can't promise I'll be able to help, but you can try!
Next chapter: Getting qualified >>
Submitting a bug
Writing PHP The design process Analysing the requirements Designing the solution Developing the code Implementing the application Maintenance and support Which IDEs are good Line numbering Syntax highlighting Online help Code insight Interactive debugging Profiling Popular IDEs Laying out your files Directory structuring Group development How to develop code Version control Documenting your project Testing Distributing your code Charging for your work PHP Encoders Cross-platform code 1: Loading extensions Cross-platform code 2: Using extensions Cross-platform code 3: Path and line separators Cross-platform code 4: Coping with php.ini differences Cross-platform code 5 Debugging What is a bug? The most basic debugging technique Making assertions Triggering your own errors Source highlighting Handling MySQL errors Exception handling Backtracing your code Debuggers Custom error handlers Custom exception handlers Using @ to disable errors phpinfo() Debugging practice Coding style Comments and whitespace Variable naming Functions Distinguishing code blocks Output style Options for Tidy Troubleshooting Error types Choosing what types of errors you see Common errors Getting Help The documentation Mailing lists Websites IRC Conferences User groups Submitting a bug Contacting the author Getting qualified Summary Exercises Further reading Next chapter
Table of Contents
Copyright ©2015 Paul Hudson.
Follow me: @twostraws.