🇺🇸United States @scampbell1

Patch version #2 attached

I haven't done heavy testing (but am no longer getting a WSOD!) but I used the second part of what alshami wrote in their patch to create one for 10.3.6.

There are two versions of the patch: one for the first patch alshami wrote and another for the second. This is the first.

I just tried upgrading to 10.3.6 and am now getting a WSOD. After some googling, I came across this thread (please let me know if it's best if I create a separate issue).

Currently, the error says Twig\Error\RuntimeError: The "Drupal\Core\Template\TwigExtension" extension is not enabled in "core/themes/claro/templates/classy/layout/html.html.twig". in /code/vendor/twig/twig/src/ExtensionSet.php on line 80

However, #6 would not apply for me because my TwigNodeCheckDeprecations.php already written that way.

I, too, am running Twig Extender.

scampbell1 → created an issue.

scampbell1 → created an issue.

Can we get a new release rolled out so people can update their sites accordingly?

I am on a site that has been running the patch and I am trying to move to v2. However, we do use the groupmenu module for our groups and, at every turn, there seems to be an error.

I tried adding the functions in #298 to the groups.install file but I get a WSOD when I do. The error there says TypeError: Drupal\Core\Entity\Sql\DefaultTableMapping::Drupal\Core\Entity\Sql\{closure}(): Argument #1 ($definition) must be of type Drupal\Core\Field\FieldStorageDefinitionInterface, __PHP_Incomplete_Class given in /code/web/core/lib/Drupal/Core/Entity/Sql/DefaultTableMapping.php on line 175 #0 [internal function]: Drupal\Core\Entity\Sql\DefaultTableMapping::Drupal\Core\Entity\Sql\{closure}(Object(__PHP_Incomplete_Class)). But, if I execute the SQL commands directly on my database, I can run the update functions.

Then, I try going to the menus tab on any group and I again get a WSOD. The error that time is Uncaught PHP Exception Error: "Call to a member function toLink() on null" at /code/web/modules/contrib/groupmenu/src/GroupMenuContentListBuilder.php line 61. I have tried adding a simple if statement to the buildRow function so it becomes

  /**
   * {@inheritdoc}
   */
  public function buildRow(EntityInterface $entity) {
    if (empty($entity->getEntity())) {
		return;
    }
    /** @var \Drupal\group\Entity\GroupContentInterface $entity */
    $row['id'] = $entity->id();
    $row['label']['data'] = $entity->getEntity()->toLink(NULL,'edit-form');
    $row = $row + parent::buildRow($entity);
    unset($row['entity_type'], $row['plugin']);
    return $row;
  }

and that will get me into the menu page. But, any related menus are gone. I try to relate a menu or create a new one and, again, I get a WSOD with the error saying Uncaught PHP Exception TypeError: "Drupal\group\Entity\Group::addContent(): Argument #1 ($entity) must be of type Drupal\Core\Entity\ContentEntityInterface, Drupal\system\Entity\Menu given, called in /code/web/modules/contrib/group/group.module on line 660" at /code/web/modules/contrib/group/src/Entity/Group.php line 154

And, before anyone mentions it, I have tried adding the Group Content with String IDs → module and it doesn't do anything.

That is to say nothing about how I have tried to upgrade to v2 after all of this and I have gotten issues with running the update script. Like the folks on https://www.drupal.org/project/group/issues/3322567 🐛 Error on update from 1.5 to 2.0 Active and https://www.drupal.org/project/group/issues/3363130 🐛 Database update errors when upgrading from 1.5 to 2.1 pluginid not found Active I have been having issues when trying to get group_update_9203 to run. I have gotten errors saying: Failed: Drupal\Core\Entity\EntityStorageException: The entity update process failed while processing the entity type group_content, ID: 7185. in Drupal\Core\Entity\Sql\SqlContentEntityStorageSchema->copyData() (line 220 of /code/web/core/lib/Drupal/Core/Entity/Sql/SqlFieldableEntityTypeListenerTrait.php).

Does anyone have a solution on how to uninstall the patch while still having the groupmenu module work?

Fixed in 1.0.4

Patched in 1.0.2

scampbell1 → made their first commit to this issue’s fork.

Thank you for the finds and patches. I added them and have ported to a new version.

scampbell1 → changed the visibility of the branch 3407501-automated-drupal-10 to active.

scampbell1 → changed the visibility of the branch 3407501-automated-drupal-10 to hidden.

@subhashuyadav You were missing a semicolon at the end of line 553. I have an updated version of the patch attached.

scampbell1 → created an issue.

I rewrote the error in a new format (it may need to be cleaned up) as a patch

scampbell1 → created an issue.

So after a lot of trial and error, I figured out a possible solution. I added vendor/google/** -text diff to my root .gitattributes file and also created a patch that creates a standalone id field in the database.

I followed the steps found here to get around the issues with the Google-provided code by manually uploading the files in a binary transfer format but, now, I am getting this database error.

Drupal\Core\Database\IntegrityConstraintViolationException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'conversions:click' for key 'PRIMARY': INSERT INTO "google_analytics_reports_fields" ("type", "ui_name", "description", "gaid", "data_type", "column_group", "calculation") VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6); Array ( [:db_insert_placeholder_0] => METRIC [:db_insert_placeholder_1] => Conversions count for click [:db_insert_placeholder_2] => The count of a specific conversion event. [:db_insert_placeholder_3] => conversions:click [:db_insert_placeholder_4] => string [:db_insert_placeholder_5] => Event [:db_insert_placeholder_6] => ) in Drupal\mysql\Driver\Database\mysql\ExceptionHandler->handleExecutionException() (line 50 of /code/web/core/modules/mysql/src/Driver/Database/mysql/ExceptionHandler.php).

Any ideas on how to handle it? I do not want to sound like a jerk, but as of this writing, GA4 goes live in 28 days so being able to continue to use the module after Universal Analytics is disabled is somewhat time-sensitive.