Ok, sorry for the blatant cross posting of this problem. But I am beginning to think that this is the more appropriate place for it (mods if you feel the need to, delete the thread in the modules troubleshooting forum).

"I just did a completely fresh install of XOOPS 2.0.10 and now I am trying to install some modules that aren't included with XOOPS (wf-section in particular, but this problem is not limited to this module). When I go to the module admin page they simply don't show up. There are no errors, nothing is "wrong". It's as if it doesn't even exist. The modules are in the correct directory and they have the correct permissions. I've done this before and it's all worked fine. I can't understand why all of the sudden XOOPS just doesn't see any third party module I put in the modules directory. I even checked to make sure that the definition for the XOOPS root path was correct in mainfile.php. Does anyone have any clue as to what might be causing this behaviour?"

I have been trying to figure this out all day and have come up with no answer. I even went as far as restarting the apache2 server (which itself presented a host of problems completely unrelated to any of this). I have tested more third party modules and they all do not show up. Ownership and privleges are all still set to the proper settings, the same as they were when things were working. This is as clean an install as possible. I am stumped.

No errors with PHP debug enabled?

Is PHP debug a compile time option? Or is it something i can set in the php.ini file?

So it turns out that the problem was actually in the wfsection module. Inside the loadinfo function the php code was puking somewhere. I dunno why exactly, there's way too much code to debug. I'm thinkin' I'll just settle for an older version that works for sure.