I've had a long-running problem (since v2.0 release) on my localhost where collapsible menu's & modules weren't collapsing. They worked fine on my public webserver, but no matter what debugging trace, DOM view, or any other trick I could think of, I couldn't get it to work on localhost.

Then today, I was adjusting some other settings & my Apache service blew up. So, in debugging that (my access & error logs were 16mb & 14mb respectively), I discovered that eAccellerator had logged a 'You can't do that in this directory' kinda error.

My first thought was "Whaddaya mean I can't do that? I own this machine." Yeah, I took it personal.

Turns out that not all of bitweaver's cached files were being cleared when I manually cleared all caches. The culprit turned out to be an .htaccess file located in a subdirectory of <root>\storage.

My point is that I had been drilling so deeply into php & javascript debugging that I had never considered the possibility of the problem occuring somewhere else altogether. The .htaccess file was overriding my server configuraton & disallowing a 'File>Delete' action.

So, in future, I'll resist the urge to immediately fire up my php debugger, and will instead fire up my brain.