Notice: Undefined index: select2widgetajax [#2549493]

Hello Everyone,

When creating new content, such as a Discussion Post, I get the following error (three times):

Notice: Undefined index: select2widgetajax in select2widget_entity_process_callback() (line 115 of /var/www/html/profiles/openatrium/modules/contrib/select2widget/select2widget.entityreference.inc).

I have changed the og_group_ref default widget type to Select2Widget Ajax. Doing this removed some other errors, but not the error above... Possibly unrelated, when I use the command "drush fra -y" I get the following warning and errors:

[error]
WD php: FieldUpdateForbiddenException: A list field (field_button_style) with existing data cannot have its keys changes. in list_field_update_forbid() (line 363 of /var/www/html/modules/field/modules/list/list.modules.

[warning]
Cannot modify header information - headers already sent by (output started at /user/share/pear/drush/includes/output.inc:38) bootstrap.inc:1232

[error]
Drush command terminated abnormally due to an recoverable error.

I'm running Open Atrium 7.x-2.43 on Fedora 17. I built this site with one of the first stable release of OA2. However, it has been stuck at 7.x-2.23 due to issues with updating. I mention this in case the error is related to updating from 2.23 to 2.43.

Comments

Comment #1

11 August 2015 at 13:50

OhioEmployee created an issue. See original summary.

Comment #2

mpotter CreditAttribution: mpotter commented 11 August 2015 at 15:21

Sounds like you didn't properly revert the Features after the update (part of the documented upgrade process). The changes to the field for select2widget should be handled by reverting the oa_core Feature I believe. You could do a quick Pantheon install of a clean v2.43 Atrium site for free and compare the settings on the og_group_ref field to see if you set the select2widget correctly if you can't revert the field for some reason.

Comment #3

OhioEmployee CreditAttribution: OhioEmployee commented 11 August 2015 at 17:27

OK, I will give that a try and report back. Thanks.

Comment #4

OhioEmployee CreditAttribution: OhioEmployee commented 18 August 2015 at 13:02

I have a feeling I did not revert features on an earlier update to OA2, which finally caught up to me. However, I love step-by-steps, so if anyone is struggling with a similar issue here is what I did to solve this:

Login as admin
put site into maintenance mode (in OA2)
/admin/config/development/maintenance
new terminal
su root
start nautilus
new terminal
su root
cd /var/www/html
drush cc all
drush fra -y
download latest OA2
extract to /var/www/
copy /var/www/html/sites to /var/www/html/
delete contents of /var/www/html/
*keep hidden files
copy latest OA2 to /var/www/html/
copy sites to /var/www/html/sites
merge folder, apply this action to all files
replace file, apply this action to all files
change default properties:
*create and delete files
*read and write
/var/www/html/sites/
/var/www/html/sites/default
/var/www/html/sites/default/files
/var/www/sites/default/settings.php
start gedit
open /var/www/sites/default/settings.php
change $update_free_access = FALSE to TRUE
drush updb
type y
drush cc all
drush fra -y
service httpd restart
>>do it all again!
drush updb
type y
drush cc all
drush fra -y
service httpd restart
>>do it all again a third time!
drush updb
type y
drush cc all
drush fra -y
service httpd restart
take site out of maintenance mode (in OA2)
/admin/config/development/maintenance
change default home page
/admin/config/system/site-information
set og_group_ref default widget type to Select2widget Ajax
/admin/structure/types/manage/oa-discussion-post/fields/og_group_ref
>>no more warnings!!