Account created on 12 March 2008, over 16 years ago
#

Recent comments

🇨🇦Canada megan_m

I was able to make this error go away by uninstalling DateTime hide Seconds module. But I also wasn't able to replicate it using the Smart Date starter kit + DateTime hide Seconds on a clean install. SO it might have to do with that module + some other configuration ?

🇨🇦Canada megan_m

The instructions from the link don't work either. What you want is a credentials file in json format with a file name like your-property-name-[string of numbers].json.

When I set this up in developers.google I followed the instructions in the Readme and it did generate a service account. From API/service details, look for Service Accounts. Then edit that, and use the Keys tab to create a new key. This will let you generate the json file.

That will let you download a json file. That's what you need to upload in the module settings.

Then, as marco mentioned in #3, you need to add that email address as a user in GA4. From GA4, go to Admin then look for Account access management.

🇨🇦Canada megan_m

Oops, didn't get the permission file in there. Here's a new patch

🇨🇦Canada megan_m

Applying the patch for issue #3364109 linked in the previous comment resolves this error for me.

🇨🇦Canada megan_m

I copied the contents of the composer.libraries.json file into my composer.json file and that worked.

🇨🇦Canada megan_m

If I'm understanding you correctly, this is actually because of this issue:

https://www.drupal.org/project/disqus/issues/3359581 🐛 Uncaught TypeError: $(...).once is not a function RTBC

The same thing happened to me after upgrading to Drupal 10. So if you install that patch there you should be good.

🇨🇦Canada megan_m

Thank you for working on this pyrello! My client is waiting for this. Unfortunately I don't know anything about writing ckeditor plugins either :)

🇨🇦Canada megan_m

Is that why I'm getting this error:

Drupal\Component\Plugin\Exception\InvalidDeriverException: Plugin (views_entity_embed_drupalentity) deriver "Drupal\entity_embed\Plugin\CKEditor5Plugin\DrupalEntityDeriver" does not exist. in Drupal\Component\Plugin\Discovery\DerivativeDiscoveryDecorator->getDeriverClass() (line 218 of core/lib/Drupal/Component/Plugin/Discovery/DerivativeDiscoveryDecorator.php).

?

🇨🇦Canada megan_m

This doesn't seem to work with the 2.x version of Google Tag.

BUT, it's not necessary to use a separate module for this. Domain Config module can handle this. I am currently having trouble getting that to work with the 2.x version of Google Tag. It works in the 8.x-1.6 , but I might have been setting it up wrong. The UX for that module works better for this use case in the 8.x version. Setting up multiple containers works differently in the 2.x version.

🇨🇦Canada megan_m

The ""%AutoEntityLabel%" block" text is appearing for me only in Layout builder. It's not displayed on the front-end.

🇨🇦Canada megan_m

I'm finding the same as #8. And also, if I have "Make filter options collapsible" checked, then the collapsible box still appears.

🇨🇦Canada megan_m

Thanks for the fast response. I have used a custom module in the past to do this, but I don't really like any of those solutions for doing this :|

If I'm using this module to adjust the help text on a per-field basis, it might be nice to be able to set the defaults on the config form. And also pre-fill the form on the field widget settings with that default text :) Or even pre-fill the form on the widget settings with the default help text, that would be good.

🇨🇦Canada megan_m

Sorry, thought I found an issue but it was a configuration problem on my part.

🇨🇦Canada megan_m

I can confirm that this patch applies, gets rid of the ajax error, and makes the modal display. However, the correct form mode is not loading. It's using the default form mode not the one I have configured the modal to use. I'm not sure if that's a separate issue or not.

🇨🇦Canada megan_m

I had this problem on a site without Layout Builder Asymmetric Translation so this doesn't belong with this module. I will move this to core/layout builder

I'm not sure what's needed to reproduce this. I think it could have happened if editors closed a layout tab without saving or discarding the changes? I don't understand how tempstore works so that's just a guess.

Based on this Stack Overflow post, I was able to go in to the key_value_expire table and delete the rows where collection was tempstore.shared.layout_builder.section_storage.overrides. All the nodes we were having trouble with were in there (22 rows).

Sql query:

delete from key_value_expire where collection like 'tempstore.shared.layout_builder.section_storage.overrides'

Production build 0.69.0 2024