🇩🇪Germany @uniquename

Sorry, ignore the last comment. something went wrong with the reroll... Here is the correct one.

Here is a reroll against 2.0-beta17

Ran into the same issue and google brought me here. #56 from the other issue did the trick for me

drupal 10.3
geocoder 8.x-4.25

https://www.drupal.org/project/geocoder/issues/3153678#comment-14822390 🐛 How to add Gecoder 3.x providers Needs review

We had the same issue and we've found that it's problematic to have the bundle name at the end of hook_preprocess_node. Instead we do it like here

https://stackoverflow.com/a/43780621

I've update the 1.0.x branch and comited the changes.

Added the missing schema.

uniquename → created an issue.

Look good to me!

uniquename → created an issue.

uniquename → created an issue.

uniquename → created an issue.

Here is a follow up ticket. https://www.drupal.org/project/migrate_tools/issues/3432321 🐛 Using --sync results in: [warning] array_flip(): Can only flip string and integer values! EntityStorageBase.php:278 Active

uniquename → changed the visibility of the branch 6.0.x to hidden.

uniquename → created an issue.

It seems that the changes got removed in https://www.drupal.org/project/migrate_tools/issues/3397550 🐛 --sync does not remove rows without a destination Fixed

Find a patch attached that applies to 6.0.4

Oh sorry, forgot to mention, I'm on gin.

With 19 it is in the middle, see screenshot, with 20 it's on the right there.

I have created a sandbox over here → that show a concept of integrating with moderation_sidebar.

It leverages a custom form display mode to get the scheduler fields in the moderation sidebar but leaving all the logic for scheduler.

uniquename → created an issue.

Seems you're right, but this one needs less configuration and attempts to fix the schema.yml.

uniquename → created an issue.

uniquename → created an issue.

The patch from #48 seems to create a corrupted revision, when saving the layout form without any changes.

Steps to reproduce:

1. Get a fresh installed d10.1.5 with layout builder enabled and the patch applied.
2. Have a content type that has the full view enabled for layout builder.
3. Create a node of that content type.
4. This will create the first revision on /node/1/revisions.
5. Goto /node/1/layout and press save layout without changing anything.
6. No new revision will show up on /node/1/revisions.
7. Goto /node/1/layout, move a block an press save layout.
8. A new revision will show up on /node/1/revisions, but hast the vid 3.

I've also found that in the DB in node_field_revision are three entries, so 5. created data, but this row has the revision_translation_affected field emtpy. That's why it's not showing up on /node/1/revisions.

Find a patch attached.

uniquename → created an issue.

I think this patch produced an unused $langcode variable in generateTokenValues().

This leads to non translated metatags when using something like

$tags = $this->metatagManager->tagsFromEntityWithDefaults($entity);
$metatags = $this->metatagManager->generateTokenValues($tags, $entity);

I could fix that with adding $langcode to this line in the same method.

$processed_value = $this->processTagValue($tag, $value, $token_replacements, TRUE, $langcode);

I'm not sure if this is the right place to put a patch for it.

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

Find a patch attached.

uniquename → created an issue.

uniquename → created an issue.

Ups, forgot something... next try.

Find a patch attached, that applies against 4.1.6

uniquename → created an issue.

Works fine for me and is a minor change, so could be commited.

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

Thanks, commited.

Thanks, commited.

Thanks, slightly modified and commited.

FormBase and ControllerBase already have StringTranslationTrait, so no need to have a use statement again.

Because the module is still pretty much work in progress I will not yet apply this patch. But thanks anyway.

Thanks. Patch is applied.

Here is a patch against current 2.0.x

Here is a patch for that.

fixed typo

Tested on a fresh d10 installation and worked for me.

#10 worked for me.