The Drupal Module That Will Not Disable

The Drupal Module That Will Not Disable

The Easiest Way to Manage Drupal Module Disable

All of Your Drupal Module Disable Data In One Place

Have you ever built a Drupal site, you realize the excitement of attempting new modules. Drush makes module sampling precariously easy — a fast drush dl and drush en , plus you've got your snazzy new feature. We all know we ought to choose modules sensibly , and test changes on the copy . But we have a tendency to believe that, contrary goes completely wrong, we are able to just disable the module and become normal again.

Sadly, reality could be a lot more harsh. Within this Drupal ghost story, you'll tremble in the Undead Module That Will Not Disable — and also the hrs it required to uncover how you can kill it.

Media, Media Gallery, and also the Unstable 2.x Branch Previously, I'd a website that used both Media (a large module), and Media Gallery , a little module that gives a great "gallery" of pictures of the media files. (Yes, I possibly could used Sights with this, but Media Gallery had some good features — including the opportunity to reorder the pictures by dragging them around.)

At this time around, Media had come forth with a couple.by branch, with awesome additional features, but Media Gallery had lagged, and just labored using the 1.x branch of Media.
Now, the press folks were sensible, plus they had not made the two.by branch the default. 2.x was too unstable. Should you used drush dl media , you'll still got the stable 1.x branch. These were while using major version system for Drupal modules well.
Even when I'd unwisely up-to-date all of the modules at the same time, this update would have known as Media 1.x, so Media Gallery would have labored and my website wouldn't have damaged. If 2.x eventually grew to become the default version for Media, while Media Gallery still depended on 1.x, then this is an issue.
However, I handled to produce a completely novel disaster. Trouble Starts (Because It Always Does) With Fine-tuning

I needed to have the ability to personalize the thumbnail that made an appearance within my art galleries, instead of accepting the random crop. This rapidly converted into an average Drupal rabbit hole, and at the time of my searches, I discover the File Entity module. I made the decision I'd check it out, and went drush dl file_entity .
Large mistake. Nothing broke immediately. But after a number of other changes, I discovered which i could no more save my art galleries . Whenever I attempted to edit and save them, I acquired some warning about file types.
File Entity Needs the Unstable 2.x Eventually, I monitored this lower to file for Entity, and really visited its project page . Ah. It needed Media 2.x.
I can not remember basically really attempted improving to Media 2.x, or maybe I handled to check on Media Gallery first and find out this wasn't a choice.

In either case, I determined which i needed to choose from File Entity and Media 2.x, or Media Gallery and Media 1.x. Media Gallery won, and so i made the decision to disable File Entity.
The Module That Will Not Die Except, I could not. After I attempted drush dis file_entity , it cautioned me which i could not disable File Entity without also needing to disable Media .
What? I'd downloaded this extra module! After I'd already installed and enabled Media! How been with them possibly be a dependency of Media? Media had been running before I even considered to download this crazy glue!
It had been like my roommate's new girlfriend had began responding to his mobile phone for him. After 2 days. Something was very wrong.

All of Your Drupal Module Disable Data In One Place

File Entity Had Been There The answer, it switched out, was still being with that File Entity project page , in bold:

This module isn't suitable for Media 1.x. You have to make use of the File entity module that's incorporated with Media 1.x and never this separate project. This really is just for use with Media 2.x.

File Entity was not an optional module. Should you went Media, you possessed File Entity.

On Television 1.x, this code have been incorporated with Media . Whenever you did drush dl media , this incorporated the code for File Entity. Many "modules" are just like this. We give them a call modules, however they really include multiple modules which may be enabled and disabled individually.

Easy Drupal Module Disable Management

For domain names hosted with us it’s very easy and quick to check your WHOIS data by just logging in to your web hosting account.

Privacy and Security

We offer privacy protection as an addon with all domains so you can rest assured that your private information is protected the right way.

Keeping Your Drupal Module Disable Safe

For Media 2.x, the designers had made the decision to split up File Entity out into its very own project on Drupal.org. Should you went drush dl file_entity , you can get this separate File Entity that only labored with Media 2.x .
Meanwhile, should you went drush dl media , you can get the fir.by form of Media.
In a nutshell, using drush would enable you to get mutually incompatible modules.
The Problem With Overrides Whenever you recognized this error, crippling your 2.x File Entity wasn't enough. As lengthy as that 2.x code was there, in sites/all/modules/file_entity/ , Drupal would keep trying for doing things, rather than the fir.by version incorporated with Media 1.x in sites/all/modules/media/file_entity/ .
The only real solution ended up being to: disable File Entity (2.x) and Media (1.x)

completely un-install and take away the code for that separate File Entity (2.x)
after which re-enable Media (1.x) which may now likewise incorporate File Entity 1.x code, that was a part of Media 1.x.
That solved it. I possibly could edit and save art galleries again. Moral from the Story: Plan Your Modules and browse Carefully
Granted, this story is exactly what we call an "edge situation". It does not happen very frequently that designers separate a module out into its very own project, which makes it readily available for drush , as the primary project continues to be set for an earlier major version.
However, it will happen. More frequently than you'd think. So that as we had, the Drupal override system, usually so splendid, made the incorrect (although logical) call here and used the more recent, incompatible form of File Entity.

All part may be the edge situation. What's not an "edge situation" is installing and seeking new modules without really understanding what you are doing. If I'd checked the File Entity project page itself, rather than being quite happy with various blogs and articles concerning the Media system, I'd have experienced that bold warning and saved hrs of debugging.
Also, I had not taken time to know the press module fully enough. I did not understand that File Entity would be a non-negotiable a part of Media. Since it was like another module, and since I'd never looked carefully enough at Media 1.x to note a directory known as file_entity , I figured File Entity was optional. This mental confusion managed to get more difficult that i can realise why I could not appear to disable the module I'd downloaded.
Why did not I make time to research this correctly? Since I was focusing on a little site, for any friend. It had been a relief to simply download and check out some modules, without needing to do all of the usual research.
However I ended up walking right into a tar pit. Works out, regardless of how small the website, you could find yourself in trouble. It's really no fun needing to understand modules, their major versions, and just how they interrelate. But it is a smaller amount fun investing hrs on the damaged site, and needing to learn everything stuff anyway.
Browse the project pages before you decide to download. Remember — just installing File Entity 2.x, even when I did not enable it, was enough to interrupt my Media 1.x site. The weekend it will save you might be your personal.