Een hart voor de Drupal Community

Sven Decabooter added a comment on drupal.org: Add schema validation + #config_target support

Problem/Motivation

Use OOP hooks, as per https://drupal.org/node/3442349, with LegacyHook support.

Proposed resolution

- Migrate existing hooks to a Hook class + add LegacyHook fallback support.

Remaining tasks

- Create MR

svendecabooter created an issue.

Class logic has been added now.

Sven Decabooter added a comment on drupal.org: block translation

Sven Decabooter added a comment on drupal.org: block translation

MR needs to be reworked on latest 3.0.x branch...

Sven Decabooter added a comment on drupal.org: Call to a member function id() on null

Sven Decabooter added a comment on drupal.org: Call to a member function id() on null

Sven Decabooter added a comment on drupal.org: Fix failing tests

Sven Decabooter added a comment on drupal.org: Fix failing tests

Problem/Motivation

Fix failing tests, as reported by Gitlab CI

svendecabooter created an issue. See original summary.

Problem/Motivation

Fix PHPStan issues, as reported by Gitlab CI.

svendecabooter created an issue.

Sven Decabooter added a comment on drupal.org: Fix PHPCS issues

Problem/Motivation

Fix PHPCS issues reported by GitlabCI.

svendecabooter created an issue. See original summary.

Fons added a comment on drupal.org: Paragraphs / Entity reference revisions fields are not translated

Fons added a comment on drupal.org: Paragraphs / Entity reference revisions fields are not translated

I've setup this module and it works great!

I've setup my website and it has a lot of layout builder blocks, some of them also have a field of the following type:

Entity reference revisions Reference type: Paragraph Paragraph type: [TYPE]

I notice all content from this field type / no paragraphs are translated when using the AI translation.

Is this even possible?

When I manually translate a node everything works great without AI translation which means the translation configuration by itself is correct.

Steps to reproduce

1. Setup a content block with a Entity reference revisions, Reference type: Paragraph, Paragraph type: [TYPE] and fill it with some content
2. Run AI translate

f0ns created an issue. See original summary.

I've setup this module and it works great!

I've setup my website and it has a lot of layout builder blocks, some of them also have a field of the following type:

Entity reference revisions Reference type: Paragraph Paragraph type: [TYPE]

When I manually translate pages everything works great.

When I use Translate AI to translate I notice that the paragraphs on the source node from which is translated disappear.

Steps to reproduce Setup a content block with a Entity reference revisions field of type Reference type: Paragraph Paragraph type: [TYPE] and fill it with some content.

Translate a node manually, you'll notice this works. Translate with AI translate, you'll notice the paragraphs on the source node from which you translate disappeared. They do appear in the translation.

f0ns created an issue.

Problem/Motivation

I've setup this module and it works great!

I have a few content blocks which use the field type double_field (https://www.drupal.org/project/double_field) for example for the FAQ (Question / Answer). I notice all content from the double_field type is not translated when using the AI translation.

Steps to reproduce

Setup a content block with a double_field and fill it with some content Run AI translate

f0ns created an issue.

Latest commits in 2.x have failing PHPCS jobs, so that still needs fixing.

Merge request has been updated, since the blocking issue is now resolved. PHPCS pipeline is passing now.

svendecabooter made their first commit to this issue’s fork.

Sven Decabooter added a comment on drupal.org: Drupal Coding Standarad issues