All,

I have Altsys 0.55 installed on 2.0.16.
I've copied /{trust_path}/libs/altsys.
I've added include XOOPS_TRUST_PATH.'/libs/altsys/include/admin_in_theme.inc.php' ;
I've patched resource.db.php
I've cleared templates_c
I've cleared adminmenu.php

But I'm still not seeing the Altsys. The Admin screen still looks like the normal 2.0.16.

What step have I missed or what else could I look into to resolve this?

Here's an update. It's looking like a problem in my 'config' table of my existing site.

I installed a brand-new site from scratch. Made all the appropriate patches, installs, etc. The admin menu works perfectly with the fresh install.

I exported the system core tables from the existing database/site and imported them one at a time into the new database/site until it crashed my new sites' admin menu. When I imported the config table it caused the admin menu to revert to the original admin menu for 2.0.16 before the Altsys.

Any ideas which entries could be causing this behavior?

*ack: my module numbers are different between the installs; fyi*

Okay. I don't know if it's written anywhere, but if GZip Compression is enabled, it will crash the Altsys. When I turn off GZip Compress in the System Preference, my Adminmenu works correctly. Thanks all. My apologies if this is documented somewhere and I missed it.

Have you set "Theme set for admin" in preferences of altsys?

I can run "bc_admin01" as admin theme with 2.0.16 from xoops.org.

It's set to 'default'.

OK.
I've just read [1.1.1]

It's must be a problem of nesting ob_filters.
I'll check it.