Since required Core modules aren't shown anymore displaying "Core - optional" is too much and it might be confusing (because where are the required modules then?). The attached patch changes the package from all optional Core modules from "Core - optional" to "Core". The required modules' package stays the same.

Comments

Anonymous’s picture

Maybe it should be package = Drupal instead? Or even package = Drupal core?

xano’s picture

+1 for package = Drupal core.

By the way, should core be capitalised or not?

Anonymous’s picture

Based on other text, no.

xano’s picture

StatusFileSize
new21.33 KB

This patch changes "Core - optional" to "Drupal core" and additionally "Core - required" to "Drupal core (required)". I think using brackets is better for readability than a dash.

Anonymous’s picture

Status: Needs review » Needs work

Looks nice but your system.module change is inserted in this patch file.

xano’s picture

StatusFileSize
new18.54 KB

Aaargh, I did a CVS update before creating the patch? :S

Anonymous’s picture

Status: Needs work » Reviewed & tested by the community

Text change for package variable in info file is good.

catch’s picture

I was going to rtbc this but earnie beat me to it.

dave reid’s picture

StatusFileSize
new19.09 KB

This patch needed to change the string to hide the required group in admin/build/modules. Added the change to system.admin.inc from #6.

Anonymous’s picture

Dave's addition is good. This is still RTBC.

xano’s picture

+1 for Dave's addition.

That package check could be done far better by using drupal_required_modules(), but that's something for another issue.

dave reid’s picture

xano’s picture

Status: Reviewed & tested by the community » Needs review
StatusFileSize
new18.49 KB

We're going to fix the problem Dave mentioned in #9 in #319699: Simplify required module hiding in admin/build/modules.

The attached patch puts all core modules in the same, human readable package.

dave reid’s picture

StatusFileSize
new20.66 KB

Works and put all core modules into the same fieldset. Revised patch fixes the system module tests (fieldset used to enable/disable modules) and passes 100%!

dave reid’s picture

Status: Needs review » Reviewed & tested by the community

Patch in #14 applies cleanly, passes all tests, and is RTBC.

xano’s picture

Title: Change package name: "Core - optional" -> "Core" » Change package name: "Core - optional" -> "Drupal core"
webchick’s picture

Status: Reviewed & tested by the community » Needs work

Shoot. Sorry guys, but we can't use "Drupal core" because of branded distros. http://drupal.org/node/81740#comment-443099 from the original package patch.

I agree that "Core - optional" is exceptionally silly now that Core required aren't shown. "Core" is fine, though. So could we get one that does "Core" and "Core (required)" ?

dave reid’s picture

Title: Change package name: "Core - optional" -> "Drupal core" » Unify all core package names to "Core"
Status: Needs work » Needs review
StatusFileSize
new20.43 KB

Revised patch that changes all core modules package info to "Core." There is no longer a "Core - required" because of the new required module implementation in #319699: Simplify required module hiding in admin/build/modules.

webchick’s picture

Status: Needs review » Needs work

system.test's hunk needs work.

dave reid’s picture

Status: Needs work » Needs review
StatusFileSize
new20.41 KB

Ah crap. Knew I shouldn't have done a grep for '= Drupal core'! System module test passes and confirmed the admin/build/modules screen appears as desired.

webchick’s picture

Status: Needs review » Fixed

Committed! :) Yay!

Now to look at that other eeeenteresting patch...

dave reid’s picture

Yay!

xano’s picture

we can't use "Drupal core" because of branded distros

.

I thought forks etc. weren't supported? On top of that: it is the actual Drupal Core those packages belong to.

dave reid’s picture

I think webchick means branded Drupals such as Acquia Drupal, not forks.

webchick’s picture

Yeah. There are many ways to create a white-label distribution of Drupal that don't constitute "forking." For example, a university creating a distro of Drupal for all departments to create their own branded sub-sites. They would call the distro "Acme University Website Builder" not "Drupal." It's one of the reasons site_name is in a variable_get. We shouldn't hard-code the word "Drupal" in the interface.

xano’s picture

Isn't the name 'Drupal' used in a lot of strings too?

webchick’s picture

Shouldn't be. If they are, they should be replaced with variable_get('site_name'). Separate issue, of course.

Can we let this one die now, so it quits bumping up in my "My issues" queue all the time? :)

lilou’s picture

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

xano’s picture

Assigned: xano » Unassigned