After installing the accessibility module, several errors are thrown on the features creation page.

Notice: Undefined index: name in features_compare_component_name() (line 1374 of {dir}/sites/all/modules/contrib/features/features.admin.inc).
Notice: Undefined index: name in features_compare_component_name() (line 1374 of {dir}/sites/all/modules/contrib/features/features.admin.inc).
Notice: Undefined index: name in features_compare_component_name() (line 1374 of {dir}/sites/all/modules/contrib/features/features.admin.inc).
Notice: Undefined index: name in features_compare_component_name() (line 1374 of {dir}/sites/all/modules/contrib/features/features.admin.inc).
Notice: Undefined index: name in features_compare_component_name() (line 1374 of {dir}/sites/all/modules/contrib/features/features.admin.inc).
Notice: Undefined index: name in features_compare_component_name() (line 1374 of {dir}/sites/all/modules/contrib/features/features.admin.inc).
Warning: uasort() [function.uasort]: Array was modified by the user comparison function in _features_export_build() (line 502 of {dir}/sites/all/modules/contrib/features/features.admin.inc).

This is because the features module is looking for a name property defined in hook_features_api().

Comments

randallknutson’s picture

StatusFileSize
new470 bytes

Patch attached.

pirog’s picture

Status: Active » Needs review
StatusFileSize
new7.04 KB

Here is another patch against the latest dev and also with the t() convention that seems to be commonly used for the "name" attribute of a features component definition.

btopro’s picture

Status: Needs review » Reviewed & tested by the community

Confirming this knocks this out, wow this has been plaguing me for over a year and didn't realize it was this simple a fix :)

pifagor’s picture

  • pifagor committed 15540f0 on 7.x-1.x authored by pirog
    Issue #2221601 by randallknutson, pirog, btopro, pifagor: Throwing...
pifagor’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

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