This forum is in READ-ONLY mode.
You can look around, but if you want to ask a new question, please use the new forum.
Home » development » Documentation » Problem solving tutorial or thingsToCheckBeforeAsking list
Problem solving tutorial or thingsToCheckBeforeAsking list [message #94836] Fri, 05 March 2010 01:52 Go to next message
janismucenieks  is currently offline janismucenieks
Messages: 31
Registered: March 2010
Location: Latvia
Member
Hello!

1st Thank You very much for Symfony and Jobeet tutorial!

Concerning programming languages I'm fluent only in AS2.0 Smile, but I do have some usable understanding of PHP, google is my best friend and I even once did tutorial on RoR. So I manage getting through Jobeet tutorial.

The thing that really bugs me is that I'm totally useless reading error messages, logs and using debug tools.

Could please someone direct me in the right direction where I could start to pick up on these things?
Are there some kind of error solving tutorials out there?

I wonder if it would be possible to make Jobeet like tutorial when everything in project is ok except one (per lesson) particular thing that gives out particular error message so there could be step by step guide on how to track down problem source and fix it.

Thank You!
JM
Re: Problem solving tutorial or thingsToCheckBeforeAsking list [message #94858 is a reply to message #94836 ] Fri, 05 March 2010 13:16 Go to previous message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
I think that's a really good question, I wish people would ask it more often Smile

Firstly I would say, depending on the system and language, get used to where log files are. So in symfony they span between Apache (or other server) logs, symfony's own logs, and sometimes PHP has its own logging too. If there's a problem then something is usually logged in one or more of these places.

Then, my strategy with errors is to take the text (e.g. "Trying to get property of non-object") and add the language to it, so as to get something to put in a search engine ("php Trying to get property of non-object"). For system-specific stuff I often try adding in the name of the library to improve search results ("symfony", "Propel 1.2", etc).

A set of lessons of PHP debugging problems, ordered by level of difficulty, is a really excellent idea. However I have never seen one online, though perhaps one is out there. Do a search? Very Happy


Remember Palestine
Previous Topic:Problem with documentation generation (phpDocumentor)
Next Topic:Trying to understand the framework structure/inheritance
Goto Forum:
  

powered by FUDforum - copyright ©2001-2004 FUD Forum Bulletin Board Software