Recently I found myself in a catch-22 with a Drupal site I have running locally as a sandbox for development. A module I had enabled (SecurePages) was working great. Later, though, when I went to start up the web server after I had taken it down, I couldn't establish a connection to the SSL that the module requires. The server wouldn't start because of this. I first tried turning off the the "Secure (SSL/TLS) Connections" includes call in httpd.conf. The server was then able to start up ok, but I kept getting "Error Code -12263" when attempting to go into the Admin to disable the module.
So, I had to disable it manually. It may not be the "proper" way to do it, but I like that I can dive in and tweak something like this as a quick fix if necessary. I used phpMyAdmin to do this, but here's the SQL that ran for anyone who could use this information (including myself for if and when I get into a similar situation).
The important part of this is the `status` field. It had been '1' and what I did was change it to '0' to disable the module. From there I was able to get to the site and work with it without any further trouble.
Post new comment