There is a patch for event dev-8.x-1.x version.
The patch refers to files that are not in the event module at the given version.
There seems to be an error in the name or version of the module?
paul_leclerc → created an issue.
paul_leclerc → created an issue.
Patch successfully tested.
I can confirm that the few changes in this patch work.
I have add the necessary changes in the .info.yml to make drupal 10 fully compatible.
previous patch update mistake fixing
Edit for PHP 8.0.x compatible drush command annotation
Proposed patch with the drush command and addition to the readme
paul_leclerc → created an issue.
#17 I'm not able to approved it but it saved my day.
thanks ankithashetty
I've the same issue but in a different context.
After few weeks on other tickets I'm working again on an encrypt mission that was working great.
Checking out the branch about the encrypt ticket, when I'm drush cim it's enabling again all the encrypt modules, every commands respond great but the website always shows me :
Drupal\Component\Plugin\Exception\PluginNotFoundException: The "encryption_profile" entity type does not exist. in Drupal\Core\Entity\EntityTypeManager->getDefinition() (line 139 of core/lib/Drupal/Core/Entity/EntityTypeManager.php).
Drupal\content_translation\ContentTranslationManager->isSupported('encryption_profile') (Line: 94)
Drupal\content_translation\ContentTranslationManager->isEnabled('encryption_profile', 'encryption_profile') (Line: 470)
content_translation_entity_extra_field_info()
call_user_func_array(Object, Array) (Line: 426)
Drupal\Core\Extension\ModuleHandler->Drupal\Core\Extension\{closure}(Object, 'content_translation') (Line: 405)
Drupal\Core\Extension\ModuleHandler->invokeAllWith('entity_extra_field_info', Object) (Line: 433)
Drupal\Core\Extension\ModuleHandler->invokeAll('entity_extra_field_info') (Line: 660)
Drupal\Core\Entity\EntityFieldManager->getExtraFields('site_setting_entity', 'ino_ss_homepage') (Line: 160)If I drush pmu encrypt it's OK but I can't enable it and make the website don't crash on this erreur.
cli-drupal:/app$ drush edel encryption_profile
[success] No matching entities found.It's certainly a tiny thing I forget to manage but I suppose the contrib should not crash all the website because of that.
After using this patch, I believe that it breaks some handlers of the view (/config/install/views.view.profiles.yml)
The patch make some changes on
-base_table: profile
+base_table: profile_field_data
I had to make similar updates on other lines (on sorts and arguments) that still mentionned the previous table.
These lines were sets on fields that also are on the profile table but it was still generate broken handlers.
It fixed the broken handlers.
1 - I would say it's a little different context + I tried all patches without success + the workaround does not works in my case.
"I actually found a temporary workaround for this particular situation by splitting the two cases into separate "Pattern/Hidden" and "Not Pattern/Visible" conditions."
2 - I largely reduced the webform.
as @carolpettirossi I tried some patchs from the given link but it doesn't fix the issue.
drupal core 9.5.10
webform 6.2@beta
paul_leclerc → created an issue.
I had the same issue
#19
🐛
Execute hook_block_view_alter when placing blocks with layout builder
Needs work
is talking about.
This patch fixed it.
#14
🐛
Execute hook_block_view_alter when placing blocks with layout builder
Needs work
I now have the list of blocks of a layout builder page. in hook_block_view_alter and hook_block_view_BASE_BLOCK_ID_alter
Thanks
paul_leclerc → created an issue.
It helps me. Thanks !
The new error append when sending the webform.
Drupal\Core\Entity\EntityStorageException: in Drupal\Core\Entity\Sql\SqlContentEntityStorage->save() (line 815 of core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php).
Drupal\encrypt\EncryptService->encrypt() (Line: 122)
Drupal\webform_encrypt\WebformEncryptSubmissionStorage->encrypt() (Line: 74)I could trace the error until Key.php > loadFromAsciiSafeString > return new Key($key_bytes); (l51)
https://www.drupal.org/project/webform_encrypt/issues/3142997
📌
Webform Encrypt D9 readiness
Fixed
This patch fixes the issue.
But when saving the form I still having another new fatal error.
Hi,
The past could not be applied using :
the version : dev-1.x 40a690c
and the patch : 3284329-catch-exceptions-11.patch
Thanks for your answer.
The alpha 5 was released a few days after the problem appeared and has the same version name that the alpha4 so I get fooled.
Good for me it fixes the issue.
paul_leclerc → created an issue.
paul_leclerc → created an issue.
paul_leclerc → created an issue.
paul_leclerc → created an issue.
paul_leclerc → created an issue.
@jrochate, it appears to me that using the field that targets the taxonomy as a filter only result to a textfield that required the term id.
Its means that selective_better_exposed_filters needs
verf →
module to works properly ?