When updating to commons 3.3 I get this error:

    Notice: Undefined index: title in commons_origins_preprocess_form_content() (line 735 of /mnt/www/html/commonsint/docroot/profiles/commons/themes/contrib/commons_origins/template.php).
    Notice: Undefined index: title in commons_origins_preprocess_form_content() (line 735 of /mnt/www/html/commonsint/docroot/profiles/commons/themes/contrib/commons_origins/template.php).

This persists through the site. And yes, commons_origins was updated to newest version ;-)

CommentFileSizeAuthor
#1 Screenshot_6_12_13_11_13_PM.png187.13 KBjaperry
Screenshot_6_12_13_11_06_PM.png224.68 KBjaperry
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

japerry’s picture

japerry
Location KVUO
CreditAttribution: japerry commented
FileSize
Screenshot_6_12_13_11_13_PM.png187.13 KB

It looks like the partial forms for documents and polls are not working correctly, showing odd things like this:

Daniel_Rempe’s picture

Daniel_Rempe CreditAttribution: Daniel_Rempe commented

It seems that $variables['form']['title'] does not exist on every form. In my case "commons_bw_partial_node_form__document" and "commons_bw_partial_node_form__poll".
My temporary workaround is to check if the title is set. Or is it necessary to set a title instead? Any comments on that?

Changes in template.php line 756:

if(!empty($variables['form']['title'])){
    $variables['form']['title']['#markup'] = str_replace('<h3>', '<h3 class="partial-node-form-title">', $variables['form']['title']['#markup']);
  }
ezra-g’s picture

ezra-g CreditAttribution: ezra-g commented
Status: Active » Postponed (maintainer needs more info)

Can you confirm that you followed all of the upgrade steps listed at https://docs.acquia.com/commons/upgrade, specifically:

- Running updatedb
- Reverting all features?

commons_bw_update_7302() should update the title fields on all of your content types.

japerry’s picture

japerry
Location KVUO
CreditAttribution: japerry commented
Issue tags: +Commons 7.x-3.3 radar

tagging 3.3 to watch before we release.

dstol’s picture

dstol
Primary language English
CreditAttribution: dstol commented

This seems to be the result of not running features-revert all after the upgrade process.

ezra-g’s picture

ezra-g CreditAttribution: ezra-g commented
Status: Postponed (maintainer needs more info) » Fixed

Marking as fixed per #3/5 but please re-open if you can reproduce with the latest dev snapshot of Commons.

japerry’s picture

japerry
Location KVUO
CreditAttribution: japerry commented

confirmed steps to reproduce and #5 fixes the issue.

Updb on its own does not however. You must run drush fra or go in and manually feature revert every enabled commons feature when upgrading.

Status: Fixed » Closed (fixed)

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

goofken’s picture

goofken CreditAttribution: goofken commented

This extra if check worked for my setup. Did all updates but warning was still there

amittarkar’s picture

amittarkar CreditAttribution: amittarkar commented

I downloaded the latest dev of commons and warning still persists.

bryanhidalgo’s picture

bryanhidalgo CreditAttribution: bryanhidalgo commented

I had the same problem and I solved after applying: drush features-revert-all

bryanhidalgo’s picture

bryanhidalgo CreditAttribution: bryanhidalgo commented
Issue summary: View changes

make image show up correctly

markbannister’s picture

markbannister CreditAttribution: markbannister commented
Issue summary: View changes

FYI is you have added custom types to the bw (say via browsing widget ui) make sure after reverting that there is a field selected to display in the browsing widget in admin/structure/types/manage/post/fields/ or you will keep getting this error.