[support] turn debug on?

[sander-martijn]

A full restore of the database from backup was the only thing that fixed 
the problem.  now back to square one with a nonworking location module...

.sander

p.s. - your databases are almost definitely NOT being backed up unless 
you set it up.  I know of no hosts that back up your database for you 
(and many shared hosts don't back anything up for you).  google "cron 
mysql backup" to find out how to make sure your db gets backed up, or 
regularly do an export - from PhpMyAdmin if nothing else.  It may well 
save you some day.

sander-martijn wrote:
> Yeah I found that this morning - I've tried the long list of possible 
> solutions - deleting references from the systems and variables tables, 
> deleting the devel tables, empty cache tables, run cron.php.  still not 
> working.
> 
> Honestly the attitude of the maintainers of this module is pretty awful. 
>   They're claiming that a warning on the main page is all that is needed 
> and that they shouldn't have to fix the module since it's a bug in zend. 
>   Well I was under a crunch last night and quickly and wrongly assumed 
> it was a zend related module - knowing that i had installed no such 
> module I went forward.  This module should not allow itself to be 
> installed if the wrong version of zend is present, or as some suggested 
> should disable the buggy functionality.  now my site is hosed and none 
> of the prescribed solutions are helping.
> 
> The only positive thing about this is that I have a dev environment and 
> installed it on there.  I feel really bad for those that are like me 
> only days from launch, install this to debug a problem with a module 
> someone else has stopped maintaining but only have one instance so lose 
> everything.  always run at least two (preferably 3) instances of any 
> site in development.
> 
> damn.
> .s
> 
> Heine Deelstra wrote:
>> sander-martijn wrote:
>>
>>> 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.
>> Execute:
>>
>> DELETE FROM variable WHERE name = 'dev_query';
>> TRUNCATE cache;
>>
>> http://drupal.org/node/126098 might apply to your situation.
>>
>> If it's for debugging, I see no problem editing files. Install xdebug/zend debugger for
>> real debugging.
>>
>> Heine
>>
>>