Using Drupal 8.0.0-beta6 and the current 8.x-2.x-dev module gives me the following error:

PHP Fatal error: Class Drupal\\google_analytics\\Form\\GoogleAnalyticsAdminSettingsForm contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Drupal\\Core\\Form\\ConfigFormBase::getEditableConfigNames) in /srv/http/drupal.protestan.org/modules/google_analytics/src/Form/GoogleAnalyticsAdminSettingsForm.php on line 928

All Drupal pages (Live site, Administration, etc.) turn up blank. It appears some coding mistake in this module is the culprit. Removing the module (even without "uninstalling" since I can't reach Admin) clears the error and the site functions again.

Comments

alerque’s picture

alerque commented
Issue summary: View changes
hass’s picture

hass commented
Status: Active » Closed (duplicate)
alerque’s picture

alerque commented

@hass What issue is this a duplicate of? Can you please at least add a link to the duplicate in the related issues field so that I know where to track progress and when I can enable the module again?

hass’s picture

hass commented
Related issues: +#2411955: Settings form missing getEditableConfigNames method

Searching the queue is not that difficult before opening a new case.

The module is broken as long as #2391029: Attaching inline JS no longer possible. Help get this back into core! is not fixed.

alerque’s picture

alerque commented

Searching the queue is not that difficult before opening a new case.

I did search the issues open against this module before posting this. In fact I searched again before adding the comment above hoping that knowing it was there would inspire coming up with the right terms. I think you underestimate how much your existing knowledge of the module and Drupal in general plays into what things you understand to be related and what you can search for. To an outsider it is not that easy. I did try.

The module is broken as long as #2391029: Attaching inline JS no longer possible. Help get this back into core! is not fixed.

This should likewise be better documented. Of course a dev branch is expected to have breaking bugs at any time, but it it is really chronically broken and will be until some outside event happens, that should probably be noted and the relevant issue linked in the module description. A note about future D8 support being dependent on a core change on the main module page would also give existing D7 users a chance to rally behind a cause if they hope to continue using the module.