After running through the database install the following notices appear on the admin user creation page:
Notice: Undefined index: taxonomy_term in field_info_instances() (line 687 of /Users/DanielPHenry/Sites/openchurch.local/modules/field/field.info.inc).
Notice: Undefined index: comment_subject_field_openchurch_image in variable_features_rebuild() (line 137 of /Users/DanielPHenry/Sites/openchurch.local/profiles/openchurch/modules/contrib/strongarm/strongarm.module).
Notice: Trying to get property of non-object in variable_features_rebuild() (line 137 of /Users/DanielPHenry/Sites/openchurch.local/profiles/openchurch/modules/contrib/strongarm/strongarm.module).

http://files.clikbox.com/skitch/Configure_site_%7C_Drupal-20120321-22164...

Comments

drupalninja99’s picture

drupalninja99 commented
Title: Post Instalation Notices » Post Installation Notices
Status: Active » Needs work

You will want to disable notices, several contrib modules still throw notice errors. You can check the stronfarm queue for instance and see if this is a strongarm problem, but I recommend disabling notices bc there will always be some contrib module somewhere throwing an 'undefined index' notice.

danielphenry’s picture

danielphenry commented
Assigned: Unassigned » danielphenry

I've built plenty of sites on Drupal without any notices present. Just saying turn them off is kind of a cop out.

If the notice is a problem with the module used this case should track which problems those are so contributors can repair them. If their are no cases in the offending modules then the problem is with the distro and should be fixed.

I'll try to take a look at these myself when I have some time.

I like what I see in this distro so far but if it's going to be taken seriously these notices need to be taken seriously.

drupalninja99’s picture

drupalninja99 commented

Ya that is understandable, I certainly will fix any OC notices for sure. As for notices coming from strong arm, etc. I just need help identifying where those originate. If its a strong arm issue for instance then we can report it, patch etc. and update the version. I don't have the option to just stop using strong arm. It's difficult supporting my own modules as well as 20-30 contributed modules so any help I can get would be greatly appreciated. Thanks!

danielphenry’s picture

danielphenry commented

Looks like the first one:

Notice: Undefined index: taxonomy_term in field_info_instances() (line 687 of /Users/DanielPHenry/Sites/openchurch.local/modules/field/field.info.inc).

is caused by the field_collection module: #1069318: Notice: Undefined index: field_collection_item in field_info_instances()

drupalninja99’s picture

drupalninja99 commented

Is there a patch? If there is I could add it to the .make unless there's a new release that's ready.

danielphenry’s picture

danielphenry commented
Assigned: danielphenry » Unassigned
Status: Needs work » Needs review

The second two are a problem with one of the features:

modules >> features >> openchurch_image >> openchurch_image.strongarm.inc line 55-60

  $strongarm = new stdClass;
  $strongarm->disabled = FALSE; /* Edit this to true to make a default strongarm disabled initially */
  $strongarm->api_version = 1;
  $strongarm->name = 'comment_subject_field__image';
  $strongarm->value = 1;
  $export['comment_subject_field_openchurch_image'] = $strongarm;

Not sure which name is correct "comment_subject_field__image" or "comment_subject_field_openchurch_image". but the name and the array offset need to be the same.

Code Monkey’s picture

Code Monkey commented

It appears this line, which appears to be line 58, 

$strongarm->name = 'comment_subject_field__image';

needs to have openchurch between the double underscores.

$strongarm->name = 'comment_subject_field_openchurch_image';

I made this change on a local install and the only notice / error remaining on that page was for the "Notice: Undefined index: taxonomy_term ..." error. This error points to the field_info_instances function located in the modules > field > field.info.inc file. This function is listed in the openchurch profile directory 32 times.

Out of those 32 times, it mentions taxonomy 4 times in the file names. That is as far as I can figure out at the moment.

drupalninja99’s picture

drupalninja99 commented

Thanks for the help! I will make these changes is weekend.

drupalninja99’s picture

drupalninja99 commented

I have made the openchurch image fix in dev.

Regarding the other, I haven't been able to trace down where this is coming from:

Notice: Undefined index: taxonomy_term in field_info_instances() (line 687 of /Users/DanielPHenry/Sites/openchurch.local/modules/field/field.info.inc).

Does this only display one time after you finish installation? Or is there another page

drupalninja99’s picture

drupalninja99 commented

We aren't using the field collection module.

drupalninja99’s picture

drupalninja99 commented

I think this is a core issue: http://drupal.org/node/1245332#comment-5705420

Going to try applying this patch: http://drupal.org/files/field_info_instances_fix_returns-1245332-14-7.x_...

drupalninja99’s picture

drupalninja99 commented

Added patch to dev, testing drush make build.

drupalninja99’s picture

drupalninja99 commented

Learning on the fly from http://drupal.org/node/1476014

I had to add a drupal-org-core.make to apply a core patch, also adjusted my build-openchurch.make so that I get the same core patch when I run drush make from head myself. Hopefully this works, might need some help.

drupalninja99’s picture

drupalninja99 commented

I ran build-openchurch.make and it seemed to apply the patch fine.

I see some errors from the dev packaging script as of April 1st, I guess I will see if this is going to keep happening.

http://drupal.org/node/1334928 (see errors)

drupalninja99’s picture

drupalninja99 commented
Status: Needs review » Fixed

Should be fixed in 1x dev

Status: Fixed » Closed (fixed)

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