description = is not escaped for JS. So, we need to check the box for bad judgement and submit the form, thus auto-enabling the module when the modules page is visited

CommentFileSizeAuthor
#3 you-asked-for-it-971858-3.patch2.37 KBJohnAlbin
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

chx’s picture

Dont forget to submit back the form.

chx’s picture

Oh Dmitri wrote that already. Too baaaaaaad :p

JohnAlbin’s picture

Status: Reviewed & tested by the community » Needs review
FileSize
2.37 KB

Ok. Here's a patch.

carlos8f’s picture

LOL. +1

mbutcher’s picture

Status: Needs review » Reviewed & tested by the community

Tested, and I can verify that this patch was "rolled" like no other.

IceCreamYou2’s picture

Wait, does this mean the module can never be disabled from the UI? What if someone installs a bad idea, realizes it's a bad idea, and then wants to remove it?

...oh, I get it.

dmitrig01’s picture

@JohnAlbin you are amazing

carlos8f’s picture

Can haz?

JohnAlbin’s picture

Version: 7.x-1.0-rc39 » 8.x-1.0
Status: Reviewed & tested by the community » Needs review

Fixed.

Dave Reid’s picture

Status: Needs review » Needs work

The patch is missing critical functionality: it cannot commit itself.

Wim Leers’s picture

This is AWESOME :D

wizonesolutions’s picture

Assigned: dmitrig01 » Unassigned
Issue tags: +SUPER URGENT

Has any body gotten the self comiting paches 2 werk? I ned this for a client. They insissted I use Bad Judgement on there sight.

danillonunes’s picture

If there two modules, like Module A and Module B, where:

Module A depends on Module B
&&
Module B depends on Module A

Then when them both are enabled, they cannot be disabled due to inter-dependency (on the interface, the checkboxes are disabled).

I think that can be used to ensure that a bad decision cannot be rolled back.