Welcome to my hell... day in... day out... mediating a world of user and programmers...
If you want people to use the program, when you write the directions you have to remember that what seems really obvious to a programmer or someone involved in the day to day of running things may or may not be obvious to those who want to use the program.
If the average 6th grader can't figure out what to do from your documentation, your documentation needs work... btw it actually much easier to get a 6th grader to try something unfamiliar and read the directions than it is an adult...
None of the issues I encountered were very complicated, I realize that "PHP magic_quotes_gpc" seems self explanatory to a developer, but it is not self explanatory to the average user.
In the long run you save yourself a whole of work and frustration with good documentation. With good documentation you never hear from people like me, I'd rather not be bothered with forums, too much work and too much crap in the chitchat to find what I'm looking for.
If the programmers can't disassociate themselves enough to see the program from the user's point of view find a tech writer. I assume you don't do this for your health and you want people using the product?