By asb on

Hi,

since a few days, in several of my D5 installations fieldsets in the administration section can't be expanded anymore; some CCK fieldgroups show a similar behaviour, but not all - some are still working as before. This is extremely annoying since lots of configuration option became inaccessible (e.g. Imagecache presets).

There are several things I tried, without any luck so far:

* raising the PHP memory limit
* disabling Jquery_update module
* switching to a default theme (Garland)
* switching to another Web-browser (Opera, Firewox, both Windows and Ubuntu)
* restarting the webserver daemon (Lighttpd)
* restarting the whole (dedicated) server

The protocols (/admin/logs/status, /admin/logs/watchdog) do no indicate any problems or errors.

Caching mode is "normal"; CSS compression is enabled.

System information: Drupal 5.15, LightTPD 1.4.13, PHP 5.2.0-8+etch13, MySQL 5.0.32, running on Debian GNU/Linux "Etch" (stable)

Any ideas what I can check to get my fieldgroups back??

Thank you! -asb

⋅ Categories: Drupal 5.x

Comments

jim0203’s picture

jim0203 commented

I had a similar problem; it was due to a module conflict. Off the top of my head I think it was either admin_menu.module or devel.module. Do you have either of these installed? If so, try disabling them and see if that fixes the problem.

prairiehippo’s picture

prairiehippo commented

I had the exact same issue. It was the Devel module (http://drupal.org/project/devel) that was causing it.

If I disabled the javascript portion of the module, I could expand collapsible fieldsets again.

jim0203’s picture

jim0203 commented

I think it might be fixed in the latest release - or perhaps the latest dev release.

asb’s picture

asb commented

Very strange problem, indeed. Yes, I have admin_menu enabled and already tried to disable it, without the result of getting my fieldgroups back.

However, mostly by "accident" I discovered a solution that worked for me on several sites:

"CCK Fieldgroup Tabs" depend on "Fieldgroup" (from CCK) and Tabs (from "Javascript tools"); enable "CCK Fieldgroup Tabs", "Javascript tools", and "Tabs", and the issue is gone. This is pretty braindead since I neither need "CCK Fieldgroup Tabs" nor "Javascript tools", but what the heck, it's a pragmatic workaround ;-) At least there's one drawback: the fieldsets do expand, but don't collapse.

Still I'd love to understand what is broken here, if I remember correctly, fieldsets a a core functionality of Drupal...

Greetings, asb

--
Drupal playgrounds: www.kefk.org | www.cinedat.org | www.fotonexus.org | www.encycan.de | www.encymus.de

asb’s picture

asb commented

After upgrading to Drupal 5.16 yesterday, the problem reappeared: On all upgraded sites, all fieldgroups are dead again. The "Devel" module isn't installed, and the workaround from above doesn't work anymore. This is getting really annoying :-(

Any ideas or suggestions?

Thanks & greetings, -asb

asb’s picture

asb commented

Grr... this time I forgot to overwrite the contents of the ./misc folder with those provided by jQuery Update.

To others running into similar problems: The information provided at /admin/logs/status is misleading; if it reads jQuery Update: Installed correctly that does not necessarily mean that the "jQuery Update" module really is installed correctly. It simply does not check the "misc" folder.

Greetings, -asb

gggdrpl’s picture

gggdrpl commented

Hello everyone!

I've spent a while reading several threads like this where everybody is posting their theories and possible solutions about this strange behaviour and started feeling frustrated because none of the tips and suggestions could help to solve the problem in my own Drupal installations.

But after jim0203's comment gave me the clue about the admin_menu module (which I've found indispensable), I thought about doin' a little experiment and to my own surprise, it worked out!

So, to help others which are experiencing the same problem, here's the brief description of what I did:

First of all, I haven't noticed ever this problem with any Drupal 5.x version, until I decided to dedicate this week to the task of upgrading several sites I've built, most of them with D5. I wanted all these sites to be upgraded to 5.16, which is the latest version so far. From the moment I had the first site upgraded to 5.16, I noticed the problem with the collapsible fieldsets in several sections of the site, plus the node/add/* pages.

This is my work environment: browser is FF3, which has been reported by many to present this problem.
Drupal version is 5.16, Administration menu 2.8 and jQuery Update 2.0 (and yes, it is correctly installed!)

Well, I came to this point and the collapsible fieldsets weren't working. So I did the following:

In Administration menu settings:

Apply margin-top to page body: unchecked

Use fixed instead of absolute positioning: checked (I've never used this before, maybe that's the key!)

Collapse menus in menu administration: unchecked

Collapse fieldsets on modules page: checked

Move page tabs into administration menu: unchecked

And all the fieldsets got back it's functionality! I can confirm that this is working in two different installations.

I also noticed something interesting: if I only disable Administration menu as suggested by jim0203, collapsed fieldsets would be openned but I couldn't close them again.

Anyway, this worked very well for me and I hope it will be helpful to someone else!

yakker’s picture

yakker commented

Similar issues here:

Drupal 6.10
Admin Menu
Devel

To get your fieldsets back
1. go to "/admin/by-module"
2. go to Admin menu settings.
3. Make sure that "collapse fieldsets on modules page" is UNchecked.

Save. Now you can get the module list.

To (hopefully) get rid of the issue:
1. Go to the modules list
2. UNcheck the Theme Developer option under "development."

--> Obviously, if you're using Devel to theme, this isn't workable. I'm just using it to log performance, so it's doable.

becca08’s picture

becca08 commented

@gggdrpl

thanks for posting . . . no idea why but changing up the admin menu settings worked for me too!! Yay! Thankyou . . . I have been thread surfing for hours tryng to figure this out.

Cheers

MakeOnlineShop’s picture

MakeOnlineShop commented

You are lucky, it didn't work for me and i don't know what to do ?

Thanks for help.