Not in core? [#262625]

Why are bug fixes being released as a module? Is this an interim solution? If so, is there a reason the problem can't be directly fixed in core? At least we should perhaps highlight the relevant issue(s) in the project description:

along with a note (pulled from one of those) along the lines of:

"...developers don't need to add any extra validation code to their modules to make up for the bug in core, and once core is fixed this module can be uninstalled."

Also:

"If your module relies on required checkbox fields be sure to make this module a dependency."

Is this wise? Modules would start to depend on this, then the bug will get fixed, and those modules will all need to be updated... seems like a lot of faff for a bug that (IMHO) should get fixed in core?

/2p

Comments

Comment #1

robert castelo commented 25 May 2008 at 22:15

Yes, this is an an interim solution. There's no reason not to fix core, but that will take time, and this is an immediate solution for anyone who needs it NOW.

"Modules would start to depend on this, then the bug will get fixed, and those modules will all need to be updated"

No, other modules don't need to do anything to make this work. If they really need checkboxes to be required they can make it a dependency in their .info file, but that's it.

Once it's fixed in core just uninstall this module, no faff involved.