With the issue above I was also having this when moving a paragraph field to translate. Someone created a patch that when a asymmetric paragraph get turned on to translation content will be migrated to it's own translation.
https://www.drupal.org/files/issues/2023-06-07/2992777-paragraphs_asymme... →
Does anyone know if there is a way to fix the issues describe below?
- Entity reference field referencing ECK is set to not allow translations (created through IEF - when creating node)
- Content is created
- Entity Reference Field allow translations is turned on
- Translations are now missing the Entity Reference field that was created in step 2.
Is there an automated way to create those translation that are now missing?
Ok after doing a bit more research it appears at least in my example. Content and translations were created before the field was set to be translatable. Once I went into the field settings and made the field translatable that is when the translation will not display the fields any more.
I think it is because I have an inline entity form reference to an eck inside a paragraph. I will see if I can generate steps to reproduce
Looks like this patch will make previously created translations not have a value.
You have to rebuild permissions after you apply the patch
This appears to be working with 9.2
jksloan2974 → created an issue.
Was there a real fix for this issue? The module created to fix this issue isn't compatible with Drupal 10
jksloan2974 → created an issue.
jksloan2974 → created an issue.
smustgrave → credited jksloan2974 → .
I am running php 8.1.14 and Drupal 9.5.3. I am still unable to add a span with class in the styles plugin.
Here is the error message after trying to add span.test_class|Test Class to the Styles configure textarea
Error message
The Style plugin needs another plugin to create , for it to be able to create the following attributes: . Enable a plugin that supports creating this tag. If none exists, you can configure the Source Editing plugin to support it.