After DQX Adminmenu enabled, on the pages:
admin/build/block/list/garland
admin/build/block/list/rubik
admin/build/block/list/... what ever theme enbled
the Region list become unchanged when swithing theme, i.e. always show:
Left sidebar
Right sidebar
Content
Header
Footer

Comments

donquixote’s picture

Thanks for reporting.
I do have some idea why this happens.

There is some stuff I need to get out of hook_init(). That's not so easy, but I will try.
One solution I would like would require a new module dependency.. bad.

donquixote’s picture

Ok, my guess was right.
Removing the "drupal_get_form()" from hook_init() does solve the problem (and might also solve other problems, yet unknown to us).
This drupal_get_form() is part of the mechanic that prevents csrf attackers from doing a "flush cache", or "toggle developer modules".

Solution:
I would like to avoid introducing a new module dependency, but this is really the cleanest solution.
The new module is "pageapi", which is yet to be uploaded on drupal.org.

I might do this tonight, or next week, or..

donquixote’s picture

Status: Active » Needs review

A solution is on git, will be in the next -dev release.
This will have pageapi as a requirement.
Please help testing this, before I make it an official release.

youring’s picture

The dev release works, with or without the pageapi module enabled.
Thanks!

donquixote’s picture

Are you sure? That's impossible.
w/o pageapi there should not be any admin menu showing up.

youring’s picture

yep, pretty sure.
The -dev release has no dependency indicated.

donquixote’s picture

Duh.
The 6.x-3.x branch was not even pushed online. So you were sitting on the 6.x-2.x...
The 6.x-2.x does not have this problem, but it also does not have the CSRF protection for things like "flush cache" or "toggle developer modules".

A snapshot for 6.x-3.x will be available soon.

youring’s picture

Sorry, didn't notice it was 2.x-dev, which was released on Oct. 17, just after your #3 reply
LOL.
ps. I don't use git.

donquixote’s picture

Status: Needs review » Fixed

This should be fixed since a long while in the 6.x-3.x branch.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.