[support] turn debug on?

[sander-martijn]

Yeah I found a thread on it - it's not comnpatible with certain version 
of zend optimizer, shipped with php 5.  But instead of fixing the module 
so that it doesn't install on those versions or disables the little bit 
of functionality that depends on it, they say it's not their fault and 
you should update zend (not an option for everyone, especially not 
people on shared hosts which is where my dev env is) and closed the 
issue by putting a warning on the main page.  Not a very professional 
approach IMHO, but heck I've only been programming for a decade and a 
half - what do I know?

.s

Metzler, David wrote:
> Yeah I eventually saw that message.  Too bad, cause it's a kickin'
> module.  I have no idea why that would cause your site to be hosed.....
> It is used by darn near every module developer out there, so you might
> consider checking the issue queue for issues like what happened to you. 
> 
> 
> 
> -----Original Message-----
> From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On
> Behalf Of sander-martijn
> Sent: Thursday, September 27, 2007 8:10 AM
> To: support at drupal.org
> Subject: Re: [support] turn debug on?
> 
> see the other messages - the module totally hosed my system.  no way i'm
> 
> trying it again.  Wish it had worked because it would be useful.
> 
> Metzler, David wrote:
>> You might want to get the devel module which has a ton of useful SQL
>> debugging options. 
>>
>> -----Original Message-----
>> From: support-bounces at drupal.org [mailto:support-bounces at drupal.org]
> On
>> Behalf Of dupal1.no
>> Sent: Wednesday, September 26, 2007 5:34 PM
>> To: support at drupal.org
>> Subject: Re: [support] turn debug on?
>>
>> 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
>>>