I just updated to beta4 and got the following error message when running database updates:

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /update.php/start?id=78&op=do_nojs&op=do
StatusText: OK
ResponseText: Recoverable fatal error: Argument 1 passed to Drupal\Core\Config\Config::setData() must be of the type array, boolean given, called in /home/turion/manuel/modules/group/modules/gnode/gnode.install on line 75 and defined in Drupal\Core\Config\Config->setData() (line 106 of /home/turion/manuel/core/lib/Drupal/Core/Config/Config.php).

Comments

turion created an issue. See original summary.

kristiaanvandeneynde’s picture

That's weird, it basically checks whether there is a views.view.group_nodes.yml file in your gnode module's config/optional directory, which there is. Can you confirm that file exists?

turion’s picture

In the directory modules/group/config/optional/ there is no such file. I don't have a modules/gnode/config/optional/ directory. (Note: Some time ago there was another alpha update that didn't work either, maybe that's related?)

kristiaanvandeneynde’s picture

I would think your update procedure went wrong. You shouldn't have any missing files when downloading from the project page. Can you delete your entire group module folder and replace it with a fresh copy?

turion’s picture

I removed the directory and downloaded group 8, beta4. Only then did I realise which file you actually meant. (group/modules/gnode/...) Sorry, for a non-dev like me it wasn't obvious that gnode is somehow a submodule in a subdirectory. Anyways, I have that file now. And the error is still:

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /update.php/start?id=83&op=do_nojs&op=do
StatusText: OK
ResponseText: Recoverable fatal error: Argument 1 passed to Drupal\Core\Config\Config::setData() must be of the type array, boolean given, called in /home/turion/manuel/modules/group/modules/gnode/gnode.install on line 75 and defined in Drupal\Core\Config\Config->setData() (line 106 of /home/turion/manuel/core/lib/Drupal/Core/Config/Config.php).

Note that when I do drush updatedb, I get the following error:
Update function gnode_update_8003 not found [error]
Performing gnode_update_8003 [ok]

This is quite confusing. Possibly it's related to that earlier update that went wrong? Should I uninstall the module completely, somehow delete all its tables (no idea how) and reinstall?

kristiaanvandeneynde’s picture

Given that you mention a previous update went wrong and I have no idea whether your set-up is damaged or not, a reinstall might be a good solution. That is, if you don't have any important data yet.

I've not received any similar reports so far, so I am really thinking this may be a one-off by something having gone wrong in the past. Reinstalling should be as simple as uninstalling the module in the UI and then reinstalling it as if you were enabling it for the first time.

turion’s picture

I've uninstalled and installed the module via drush now. Unfortunately, the update is still marked as ToDo somewhere: I do drush updatedb and it will say:

gnode module :
8003 - Make sure the views.view.group_nodes exists and fix broken copies.

And then, it'll again say that this update couldn't be found. How can I tell Drupal to skip this update?

kristiaanvandeneynde’s picture

Uninstalling should really clear that info. I'm starting to think there may be something wrong with your installation.

Did you uninstall all modules related to Group? "gnode", "group", ...? If all else fails, you could run this through Drush, then uninstall everything and reinstall everything: drush ev "drupal_set_installed_schema_version('gnode', 8003)"

turion’s picture

Ok, that did work :) thanks a lot! I bet now we're out of alpha, future updates will be more seamless!

kristiaanvandeneynde’s picture

Status: Active » Fixed

Right, marking this as fixed then. Although it clearly was a one-off and I would advise you to keep a close eye on the state of your database going forward. Cheers for reporting back.

Status: Fixed » Closed (fixed)

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