Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Going to /admin/reports/updates/update page on a freshly installed Panapoly distribution website is giving:
Notice: Undefined index: projects in distro_update_form_update_manager_update_form_alter() (line 374 of distro_update.module).
Only couple extra modules have been activated if that might cause the issue: demo and l10n_update
Comments
Comment #1
eawheeler CreditAttribution: eawheeler commentedI am experiencing this issue as well. In addition to Drupal 7.32 and Panopoly 1.13, I've installed and enabled the following modules.
A few more are installed but not enabled.
Comment #2
lsolesen CreditAttribution: lsolesen commentedCould you both review #2369629: Update distro_update to version 1.0-beta4. Thanks!
Comment #3
dsnopekRelating to: #2369629: Update distro_update to version 1.0-beta4
Comment #4
dsnopekI've been unable to reproduce this with either distro_update 1.0-beta3 or 1.0-beta4. I even tried installing l10n_update both at the current and an older version. The only thing I didn't try was a fresh install... Did the error message go away after a while? Or is still persisting for you on the same site?
Comment #5
hfarrier CreditAttribution: hfarrier commentedI have the same notice plus an additional warning:
Notice: Undefined index: projects in distro_update_form_update_manager_update_form_alter() (line 374 of /srv/bindings/f9af344cbc164f22ba5d584a6ce31bc6/code/profiles/panopoly/modules/contrib/distro_update/distro_update.module).
Warning: Invalid argument supplied for foreach() in distro_update_form_update_manager_update_form_alter() (line 374 of /srv/bindings/f9af344cbc164f22ba5d584a6ce31bc6/code/profiles/panopoly/modules/contrib/distro_update/distro_update.module).
Drupal - 7.32
Panopoly - panopoly-7.x-1.13
Profile is installed on Pantheon platform
Comment #6
caschbre CreditAttribution: caschbre commented@dsnopek: if you want to move this to the distro_update issue, I can try to take a look at this. I'm going to be traveling for the next week or two but can try to tackle it then if you haven't figured it out.
Comment #7
dsnopek@cashbre: Well, let's keep this issue (or a issue) in Panopoly, so that other users who experience the problem can find it. Or we could move this one into distro_update and then make a new one that refers to it? In any case, I think we need something in the Panopoly queue. Definitely let me know if you figure it out!
Comment #8
caschbre CreditAttribution: caschbre commentedYeah, that makes sense. When I'm back from my trip I'll see if I can reproduce it. So far I haven't been able to reproduce it with a fresh panopoly, open atrium, or commerce kickstart site.
Comment #9
eawheeler CreditAttribution: eawheeler commentedUpdated to Panopoly 1.13 again which had the same result as post # 5 above. Attempted to update distro_update to 1.0-beta4 per posts # 2 and 3 which resulted in warning messages relating to manually updating projects within distributions. So, I obviously don't have a grasp of all the necessary details to perform this kind of operation.
I rolled that change back and installed Panopoly dev. Calls to /admin/reports/updates and /admin/reports/updates/update appear normally without warning under dev, so it looks like distro_update 1.0-beta3 resolves the problem (at least for me). At first I believed that beta4 had been applied to Panopoly dev, but the info file labels it as beta3.
Comment #10
eawheeler CreditAttribution: eawheeler commentedFor those still experiencing this issue, I'll issue a final report on my experience. I just upgraded to Panopoly 1.14 which includes distro_update 1.0-beta4. This update resolved my problems with "Notice: Undefined index" and "Warning: Invalid argument" in line 374.
Comment #11
caschbre CreditAttribution: caschbre commentedThanks for the update @eawheeler. Just so I'm clear
distro_update 1.0-beta3 = bad
distro_update 1.0-beta4 = good
Trying to make sure if I need to dig deeper into distro_update 1.0-beta4.
Comment #12
lsolesen CreditAttribution: lsolesen commentedSetting to fixed as #10 suggests that the problem has disappeared with distro_update 1.0-beta4