Dynamicload breaks custom phptemplate regions

You have no idea how much backtracing this took to find!

When creating custom regions as per the handbook They simply DO NOT SHOW UP if dynamicload is active.

This turned out to be because, during the functions dynamicload_menu() -> dynamicload_load()
it attempts to retrieve the list of available regions using system_region_list()
... in order to enumerate the available regions.

That looked like a good idea, but

The problem is threefold.

• The theme has not yet been initialized at this point. Your template.php has not been loaded.
• system_region_list('themename') looks for the themename_regions() function, that is NOT (yet) available, and just returns the default phptemplate_regions. It doesn't try to init it for you.
• system_region_list() caches its result, so that even when the theme gets initialized at its proper time, the list of regions still does not become available!

Meaning no custom regions never!

Pff!

My quick fix is to init the theme properly, although possibly prematurely

function dynamicload_load() {
...
    init_theme() ;
    $regions = system_region_list(variable_get('theme_default', 'garland'));

_{no patch, as I'm working on a very hacked branch of dynamicload.module}

I feel this will interfere with other behaviour (switchtheme?)

The real fix is probably NOT to do this dynamicload_load() function as a side-effect of hook_menu. Is there a better (later) time to be doing this? Like just before render, not during initial URL/Menu-resolution.

Man that hurt!