Clicking "disable developer modules" disables Views UI module

That's the intended behavior. The Views UI should only be needed while building your site. You can alter the default list of toggled modules by implementing a variable override for 'admin_menu_devel_modules'.

The default is

    array('cache_disable', 'coder', 'content_copy', 'debug', 'delete_all', 'demo', 'devel', 'devel_node_access', 'devel_themer', 'macro', 'form_controller', 'imagecache_ui', 'journal', 'trace', 'upgrade_status', 'user_display_ui', 'util', 'views_ui', 'views_theme_wizard');

The variable 'admin_menu_devel_modules' is found in the Administration Menu module (admin_menu) in the file admin_menu.inc - BUT don't hack this file. Rather override the variable in the settings.php file as follows:

$conf = array(

'admin_menu_devel_modules' => array('cache_disable', 'coder', 'content_copy', 'debug', 'delete_all', 'demo', 'devel', 'devel_node_access', 'devel_themer', 'macro', 'form_controller', 'imagecache_ui', 'journal', 'trace', 'upgrade_status', 'user_display_ui', 'util', 'views_theme_wizard'),

);

You will notice that 'views_ui' is removed from the list of module names in the array assigned to the 'admin_menu_devel_modules' variable.

See also #352065: Add setting to select developer modules to keep enabled, which contains a patch that searches for testers.

+1. Devel themer module breaks some themes a bit, so even during development I've forever toggling the developer modules on and off, but I don't want Views UI turned off each time.

Great tip - I thought I was going crazy...

That's the intended behavior....

well, if that's the intended behaviour it's daft!

one module shouldnae be turning off other modules that aren't directly part of itself.

The Views UI should only be needed while building your site...

as should the devel module - there are plenty of legitimate reasons for temporarily disabling the devel module [to get rid of the extra markup it injects into pages for a start] whilst still wanting to adjust a view module 'view'. i fail to see why the developers of the devel module think that disabling the one means i automatically want to disable the other too... ???

Great tip - I thought I was going crazy...

me too!

[BTW - shouldn't this be listed as an issue for the devel module - rather than administration menu]

The "Disable developer modules" menu item is provided by the Admin Menu module as a quick shortcut to disable *all* developer modules. Disabling the "Devel" module itself won't disable Views UI. Using the menu item will. Which is exactly why this is the "intended behavior".

I'm with the others who think that Views UI shouldn't be touched by the "disabling developer modules" menu item.

+1 for not disabling Views UI with this. I couldn't for the life of me figure out how that got disabled until I did it quite a few times. "Developer Modules" I assumed meant the ones listed under "Development" on the "Modules" page.

But while I definitely support not disabling Views UI with this link, I think the attention this is getting is a by-product of this Devel issue:
#753938: Enable/disable theme developer without install/uninstall

We don't really want to turn on and off ALL development modules, we want to turn on and off the Theme developer because it injects extra code, and since that very very useful function has been strangely removed from the devel block, we turn to these links in admin menu. Right?

um, I suggest reading the full issue before following up. See #3, resp., #352065: Add setting to select developer modules to keep enabled - the list of affected modules can be configured already.

Wow what a relief! I also thought there was something horribly wrong with my views module install until i realized the UI was simply disabled and this was indeed why.

#2 worked great for me, thanks.

My vers. 6.x-1.8 and Drupal 6 but what if the code will be changed in an update how do I figure this out and remember to change the code in settings.php, please?

Should be noted, for 7.x head over to /admin/config/administration/admin_menu and in the vertical tabs select "Performance" and select the modules you would like to keep enabled. An essential piece of information for Drupal developers wanting to keep a tight ship. For coders, you can do git versioning of this by setting and overriding the variable admin_menu_devel_modules_skip (see admin_menu.inc file, line: 716)

Today we run into this issue with Drupal 7.32 and admin_menu 7.x-3.0-rc4, for us the following modules were enabled/disabled if using the menu entry "Enable/Disable developer modules":

context_ui, field_ui, l10n_update, rules_admin, stringoverrides, views_ui

.. it was crazy, hope this will be fixed soon.

Thank you.
Matroschker

Would it be possible to have the admin_menu_devel_modules array be able to accept wildcards or RegExs? So, for instance, replace the 'imagecache_ui' and 'views_ui' and similar entries with one /[A-Za-z0-9_]+_ui/ RegEx (for example) to cover all modules, present and future, which have a “…_ui” submodule?

Basically, the list of developer modules keeps increasing as new modules are developed, and it’d be a real pain for y’all to have to keep up with them all. Too bad the Drupal standard module “.info” file format didn’t include a parameter indicating whether a module was intended for runtime, site building (e.g. the various “_ui” submodules), or actual development (coder, devel, etc.), that Administration Menu and similar could key off of to automatically disable and re-enable all developer, and all developer + site-building, modules with a single menu action. Something like:
purpose = site-building ;Can also be 'runtime' (default) or 'devel' or 'cron' or perhaps other options.