Hello,

Ok, so I posted in the beginner's corner with the first part of this problem, but it has since exploded into a more annoying and drawnout problem.

So here it goes. I am trying to get debugging to work so that I can see why my page is broken (see here) and I found reference to the recovery.php.

Since I am using XOOPS 2.2.2, I assumed that to get my debug to work (since I cannot log in, cannot access user.php, cannot access admin.php), I could use recovery.php. This didnt work.

The first time I had the page loaded, I had the following error:

Quote:

I cant find a single place on the forums that answers the problem of this error (though I found this error in a couple of places).

As soon as I tried to turn on the debugging, this error disappeared, and no matter what I set the debug value to, it always went to "OFF" no matter what. So I cant turn on the debugging to fix my initial problem.

I am sinking further into this death trap and I cant see a way out. Does anyone have any insight into this problem?

[EDIT] I have also already tried editting common.php, but that doesnt display anything either. [/EDIT]

In looking at the code for recovery.php I have outputted some different aspects of it to try to debug the problem. I outputted the config values that recovery.php generated and the list contained two different parts labeled "debug_mode".

The values for the two versions of debug_mode are:

conf_name debug_mode
conf_title _MD_AM_DEBUGMODE
conf_formtype select_multi

conf_name debug_mode
conf_title _MI_DEBUG_MODE
conf_formtype yesno

I dont know why it is drawing on two different versions of debug_mode, but it is preventing me from changing my debug options through recovery.php.

Anyone know anything that can help me fix this problem so that I can get back to the original problem?

Just want to bump this for the poor guy so that it doesn't get buried in the forum. Hope someone can help.

lol, you got my hopes up... here I was thinking someone was going to help me solve this problem. But I appreciate the bump, means I dont have to do it...

But, here is another update.

So I found where that _MI_DEBUG_MODE mode was coming from. When looking for config options, recovery.php looks for anything with the following key:



The problem is, debug_mode is defined for conf_modid 1 (system), but it is also defined for conf_modid 10 (private messaging). I dont know enough about this code to add into the Criteria() to check for only conf_modid 1, so instead I did a really ugly work around by renaming the debug_mode defined for private messaging to debug_mode1 for now. I know it is an ugly fix, but once I get my site working, I will go back and change it back.

Perhaps someone with some more skill than me can go through and figure out a way to set it up so that recovery.php will only get config options for system stuff and ignore other mods?

And... now back to my original problem (see here) where you will find an update on the problem that lead me into this downward spiral of despair and hatred of all things php.