While working on a development site at some point I noticed that the manage fields links had disappeared in the admin menu. I did a quick research and found out that the field ui module had been disabled. I am the only one working on the site and didn't consciously disable this module. Since the last version that had the ui enabled is a day of work old it is hard to say what action caused the module to be disabled. Things I did include moving the site from one domain to another, enable modules, edit views, some theming and content management. After enabling the module everything seems to work fine.
I'd think that at some point I accidentally disabled the module but it seems I am not the only one with this issue: http://drupal.org/node/818414#comment-6644550

Sorry, this isn't perfect bug report since it is hard to track what happened but I figured someone should start an issue to collect information over time.

Comments

kbrinner’s picture

I just experienced the same issue, where the Manage Fields options disappeared for all of my content types. I am almost 100% positive that I did not disable the Field UI module. This may be unrelated, but I did just update Drupal core from 7.16 to 7.18, and hadn't tried to Manage Field for any content types since the update. Is it possible that somehow the updating process caused the Field UI module to be disabled?

swentel’s picture

Component: field system » field_ui.module

Moving to right component.

nico059’s picture

Same problem for me with Field UI, and context UI and Views UI where disabled too ...

As I have some other problem on this server (random 500 Internal error ...), is their a mecanism in action here (like the old throttle D6 module) which disabled some non essential module in case of performance issue ? ...

s.daniel’s picture

@nico059: I don't think there is such a mechanism.

nico059’s picture

I find the origin of this problem.

I use admin_menu. there is, in the admin menu, under the favicon (where you can flush all cache etc ..), a menu item called "Activate/De-Activate the developer modules". Probably I clicked this menu item.

If you go on your web site on /admin/config/administration/admin_menu you will see a serie of checkbox of the modules that will be de-activated. If you check them, they will stay activated even if this admin menu entry is clicked.

Regards,
Nico.

s.daniel’s picture

Thanks for the update. This might actually be the origin however since in my case i had been working on a dev site there would have been no reason to disable dev modules.

sgdev’s picture

We noticed the same issue in 7.19. I could be wrong, but it seems like the problem occurred after we updated a couple of modules through the user interface (/admin/modules/update). We normally use Drush for our updates, but I think I remember that we had used the interface for a couple of security updates shortly before we saw this problem.

Würden’s picture

I had the same issue using admin_menu and re-activating developer modules fixed the issue completely. So if you are using admin_menu this is probably not a bug (works as designed)..

righteous’s picture

Issue summary: View changes

Hello
I am pretty new in this Drupal world and I recognized similar issue by somebody else, but this post got closed, so let me ask you to help me there.
Display suite - manage display and manage fields options are no longer available in upper tab bar.
It could´ve happened, while Drupal core was updated to version 7.50, where plenty modules were disabled during this process.

A similar was described here:
https://www.drupal.org/node/1853782

I reviewed above recommendations
I have Field UI enabled
disabled devel modules

Still can´t see manage display / fields bar there with any content type. It is only accessible through menu/admin/structure/display suite... but therefore and additionaly, I can not change f.e. view mode for each content type separately.

Version: 7.17 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.