Enabling the Views UI module (without ticking the checkbox for Views module) sometimes causes other modules to become disabled. I haven't worked out what causes this to work sometimes but not others, but have reproduced the exact same bug twice. Both times using the latest version of Acquia Dev Desktop with the latest stable version of Views. Modules that became disabled are; Pathauto, Menu, Fields UI, Toolbar, Shortcut, Overlay and possibly other modules that did not have dependencies.

Comments

merlinofchaos’s picture

merlinofchaos commented

That's all core functionality; Views doesn't do anything during enable or disable that I know of. So I don't really see how Views UI itself can be the root cause.

Bevan’s picture

Bevan commented

I agree. Hopefully I or someone else will work out what's going on here though. The fact it happened twice when enabling views UI though and never when enabling other modules is interesting though.

kobever’s picture

kobever commented

I did a test today with 22 students. They had to construct a website and 5 of them complained of the disabling of core modules the moment after they enabled view and view UI.

dawehner’s picture

dawehner
Primary language German
commented

@kobever
Do you have any clue whether it might be possible that you can reproduce this error in a deterministic way?

esmerel’s picture

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

I gave it a shot and wasn't able to replicate; hopefully someone else can.

mustanggb’s picture

mustanggb commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (won't fix)