Uninstall Issue

I have noticed something else about this odd behaviour: I have uninstalled and deleted the module from the system and have found where the issue may be lurking. One of the things I did was to tell the admin theme to ignore the blocks admin paths. However, for some reason, the admin theme was still being applied to the block administration page - but the admin theme appears for ALL themes. But the block changes applied only appear for the admin theme.

Just looking to see where this is coming from... the only way to get around this problem is if I disable the Drupal core admin theme functionality and choose NOT to use an admin theme. It is like this module has done some change to the settings on the admin theme that it is releasing when the module has been un-installed.

Okay, I think I can confirm that the PHP issue is unrelated. But the weird behaviour still remains.

I have finally been able to replicate what I did. If you force the admin theme module to apply its theme to the active blocks (re: active theme) this is where the problem starts. So, when you disable the admin theme module, Drupal still attempts to load the active theme on all block admin pages, regardless if you have been using an admin theme or not.

So, essentially:

1. turn on core admin theme functionality
2. install and activate admin theme module (this module)
3. set admin theme module to activate admin theme on core blocks
4. deactivate admin theme module
5. drupal core still tries to load core theme on all admin pages, strictly for blocks

Does that make more sense or still clear as mud?

Partly correct. The path that the administration theme is activated for is:

http://www.example.com/admin/build/block

Now, the module is disabled, uninstalled, and removed from the server - but this still remains. The cache and been cleared numerous times since this module was removed. I can replicate this issue on other test sites as well (explained in http://drupal.org/node/755920#comment-2869608).

It is a complete mystery to me as there are no php errors, but this problem DOES exist - I am sure that I am not entirely crazy. :P

Actually, another symptom that I have noticed and haven't mentioned (cough, sorry about that) is when the admin theme is applied to the block management page, any blocks you move are changed in the other themes. So, for example:

1. two themes are active on the site, the main theme and the admin theme. but let's add in two other themes as well.
2. let's now edit the blocks of one of those other two themes, just for kicks.
3. we change a few block placements for the other themes
4. go back to the blocks admin page for the core them and we find that any changes we made in the other themes moved blocks in the core theme

This seems to happen if some of the regions are the same (but I haven't confirmed that at the moment). It is like the admin theme (this module) makes the other block pages forget which themes they are truly editing.

Weird I know but an interesting side-effect that I think needs some research.

I haven't tinkered with this module lately (hence my lack of response) but I have been trying to fix this issue today and what I have done so far is re-installed the module on the site giving me grief and forced it NOT to load on "admin/build/block". This seems to have fixed the loading on which theme issue but I will see if it fixes the issue where blocks just seem to fly around on their own between themes (regardless which theme blocks list I am editing).

Is there anything about this module that takes into account regions or changes how they are used? I looked over the code and it doesn't seem to do much except intercept process calls but, anyway, I will test some more and report back what I find. This kind of issue seems elusive but I can replicate it and have on three test installs with all the same results. Once I turn it on to edit the "admin/build/block" - the block system gets all gooey. (Yes, very technical, I know.)

:)