GTM setting for tracking only anonymous users.
Google tag > Conditions > User Role > Select `anon`
#24 works for me.
This was causing below the update `8102 ` did not ran correctly and the version of the latest db updates as set to `8103 ` without changes correctly applied by `8102`. I did the following to fix this.
After investigation it looks like the issue was with "viewsreference" module used in paragraph. some how update for `8102` did not went through.
So in order to re-run the db updates I reset the version from 8103 to 8102.
drush ev "\Drupal::service('update.update_hook_registry')->setInstalledVersion('viewsreference', 8102)". After running this I ran the drush updb again and the issue went away as the database changes were now in sync with codebase.
I verified to see if the version is correctly set or not using drush ev "echo \Drupal::service('update.update_hook_registry')->getInstalledVersion('viewsreference')"
hitesh.koli → created an issue.
I had a similar issue. The message appearing "Mismatched entity and/or field definitions (Paragraph)" in status report.
After investigation it looks like the issue was with "viewsreference" module used in paragraph. some how update for `8102` did not went through.
So in order to re-run the db updates I reset the version from 8103 to 8102.
drush ev "\Drupal::service('update.update_hook_registry')->setInstalledVersion('viewsreference', 8102)". After running this I ran the drush updb again and the issue went away as the database changes were now in sync with codebase.
I verified to see if the version is correctly set or not using drush ev "echo \Drupal::service('update.update_hook_registry')->getInstalledVersion('viewsreference')"
froboy → credited hitesh.koli → .
This issue still exist when items are wrapped in the fieldset.
The only way to fix this was use `template_preprocess_fieldset()` in the custom theme and set `description_display` value (before/after).
I am having the same issue using Claro as base theme for the administration with a custom theme.
#4 fixes the problem on Drupal core 9.4.12 . This patch need to go in next release