I have used an Admin theme which is located, like 'minnelli' in a sub-folder of garland, importing the garland CSS file, as minelli does.

Utilising this Admin theme as the 'Admin Theme' {admin/settings/admin} produces a conflict with the admin/build/blocks interface, which I have noticed and traced to the introduction to my site of the OG content type admin module.

Here's what's happening:

The 'administer blocks' interface (page) normally "takes on" the theme for which the block selection is being made. I.e it shows the whole page in Bluemarine when the Bluemarine tab is selected within admin/build/blocks.

However, when an admin theme is selected AND OG Content type admin module is utilised / "on", the admin theme takes over all the tabs for the other themes. Not only does the relevant theme NOT take over the admin/build/blocks interface (page), but the actual block selections for those themes is absent: only the block selection for the Admin theme is shown.

  • If Admin theme set to Bluemarine or Minelli the issue remains: those themes take over all the tabs on the admin/build/blocks interface.
  • If Admin theme is set to Garland, or System default the issue resolves.
  • If the OG C/T/Admin module is switched off the issue resolves.

I have repeated this issue with more than one website, though using the same code base (i.e. multisite)

Any ideas on why the OG C/T/Admin module should have this effect?
Any other ideas about this behaviour?

(I realise it can be argued that this is a side effect of the way I have developed an admin theme in a sub-folder of 'garland', but bear in mind the issue also happens with Minnelli and is resolved by turning off this OG C/T/Admin module.)

Thanks. Looking forward to any input you can offer. Meanwhile, I think I will switch off the OG CTAdmin module while I set up my sidebar blocks!

Comments

rconstantine’s picture

rconstantine commented

I realize you tried to be verbose and complete in your description of the problem. Perhaps I'm distracted and not paying attention, but you lost me. What do you mean by 'takes over all the tabs'? Also, is it only on the admin/build/blocks page?

My guess at what you mean is that the theme displayed on that page should change when you select the theme name for which you would like to admin blocks, but all selections are stuck on one theme. Is that what you mean? If so, I was not able to duplicate this problem. Here's what I tried:

  1. Go to 'Administration theme'
  2. Set the theme to anything other than the site theme - I chose Garland first, then Minnelli on a second test
  3. Go to the blocks config page
  4. Click on each theme name and see what happens

The result was that the theme properly changed every time - and I have 15 themes installed.

So I'm afraid you're going to have to poke around some more to figure this one out. If you built your admin theme yourself, then perhaps that's your problem.

jbc’s picture

jbc commented

Thanks for your input. You did interpret my verbosity correctly!

Presuming you had og c/t/admin installed, this is reassuring. This is a peculiar glitch; since uninstalling og c/t/admin module, I find sometimes admin pages will appear after a configuration change themed as 'garland' rather than my admin theme, though it reverts after a refresh.

My admin theme is basically a clone of garland, as minelli is, simply without the width restrictions which minelli introduces. The glitch also occurs when I use bluemarine for 'admin theme', so I don't think its a theme issue.

One question you might help me with: where do you locate your non-standard themes: in sites/*/themes or within themes/*?

Thanks again. I'll post here if I work out what's happening.

rconstantine’s picture

rconstantine commented

Minnelli, of course, came with Drupal, so it's in themes/*. My custom themes are usually in sites/*/themes, but I believe that those derived from Garland are supposed to be put inside the Garland folder, so I suppose you'd have to do that.

One thing that hopefully doesn't make any difference is that on the site I was testing, I only have one theme activated for users to see. The admin theme was then changed as I mentioned and both times was different from that one user theme. I don't know whether behavior would be different if more than one user-visible theme were activated. So play with that. Hopefully, that's not the issue. - And yes, I did have this module installed on my test server.

rconstantine’s picture

rconstantine commented
Status: Active » Postponed (maintainer needs more info)

I haven't heard back in a couple of weeks from the poster. If I don't hear back soon, I'll assume there's no longer any interest/no problem and close the issue.

Anonymous’s picture

Anonymous (not verified) commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

@Ryan

Closing the issue.