[support] turn debug on?

[sander-martijn]

thanks,

I actually went directly into the system table on the database and 
changed the status and bootstrap columns from 1 to 0 which should 
disable it.  I also deleted the folder from the modules dir.  Still, my 
site is down with a 500 internal server error.  Is there anything else 
this module modifies on install or am I pretty much SOL and having to 
reinstall?  It's not a disaster bc i did this on my dev instance - so I 
can download from the primary box and reinstall from there - but I'll 
lose a couple hours to it (mostly in ftp wait time) so it's not ideal.

.s

Michael Prasuhn wrote:
> Also fixable from settings.php. At least the disabling the module part....
> 
> -Mike 
> 
> 
> __________________
> Michael Prasuhn
> mike at mikeyp.net
> mikeyp.phone at gmail.com phone
> 714.356.0168 cell
> 949.200.7670 fax
> 
> -----Original Message-----
> From: sander-martijn <lists at severeddreams.com>
> 
> Date: Wed, 26 Sep 2007 21:39:20 
> To:support at drupal.org
> Subject: Re: [support] turn debug on?
> 
> 
> ok, that was cute.  The devel module seems to have brought my entire 
> site down.  Even after deleting it from the modules dir.  oh well - 
> looks like i'm done for the night!
> 
> dupal1.no wrote:
>> OK. This is not my strongest side :-D
>> But I will try this idea ; Can this module help you?
>> http://drupal.org/project/devel
>>
>> sander-martijn skrev:
>>> Thanks - I know those.  In this case I'm not looking to see error 
>>> messages on the screen - I've already eliminated errors.  And web 
>>> developer and firebug are client side tools.  What I want is to trace 
>>> what's happening on the app when there are no errors but things are 
>>> still not happening as expected.  It's clear that drupal already has it 
>>> built in - I'm just looking to find out how to turn it on.
>>>
>>> dupal1.no wrote:
>>>   
>>>> Hi
>>>> If  you only want to se your error-messages on screen you can put this 
>>>> line in you htaccess-file:
>>>>
>>>> php_flag display_errors on  (remember to take it away when you are finis.
>>>>
>>>> But Firefox hav some fine tools:
>>>> *Web Developer* and *Firebug*.  I use them all the time.
>>>>
>>>>
>>>>
>>>> sander-martijn skrev:
>>>>     
>>>>> Hi,
>>>>>
>>>>> I'm trying to debug an issue with the queries that the location module 
>>>>> is performing.  Basically it works flawlessly when logged in but not 
>>>>> when you're not.  I erred earlier thinking it was working fine, but I 
>>>>> guess it's not.  The module doesn't seem to be actively maintained so 
>>>>> I'm stuck debugging it myself.  If anyone has any ideas as to why that 
>>>>> may happen or what to look for I would greatly appreciate it (i've 
>>>>> already patched the module with a patch someone offered on the support 
>>>>> page as well as edited some sql to eliminate an ambiguity issue - I got 
>>>>> rid of the errors but not get "Displaying results 1 - 0 of 11 for search 
>>>>> on 05401" for a search that has 11 results if you're logged in).
>>>>>
>>>>> That said I have a more general question that has nothing to do with the 
>>>>> module.  I want to find out what the queries are that are getting 
>>>>> executed on the database so that I can
>>>>> a. compare them to the code (i discovered while debugging the first 
>>>>> issue that the queries executed are not always the same as t
>>>>> b. run them directly on the db and see what I get
>>>>>
>>>>> I found in database.mysql.inc the following:
>>>>>  if ($debug)...
>>>>> which is a variable that gets passed to the function and defaults to 0.
>>>>>
>>>>> How do I turn debug on without editing the mysql file?
>>>>>
>>>>> thanks,
>>>>> .sander
>>>>>   
>>>>>