@J.

Fixed in https://www.drupal.org/project/google_tag/issues/3424623 🐛 "Enforce Privacy Consent Policy" checkbox default value is checked even when it is disabled RTBC

Oops! sorry i didn't mean to overwrite the issue summary.

J. → created an issue.

Looked at this issue (briefly) again today.

It looks like the the "untranslateable field" value can be edited but not actually saved, no matter how many times i tried, which is good! The field is still visible though. I should also note that i was not able to reproduce step 6 from #15 anymore, but i used to be able to. Weird.

I couldn't discern any changes after appling the patch referenced in #20 to entity_reference_revisions. Field is still visible and still unable to save. I might be missing something that it's doing though.

I see this too. I would like to be able to alert the customer of the what they did instead of the page crashing.

Thank you for the tips. I implemented your suggestions and have a working solution. Closing this issue now.

Thanks. patch applied cleanly to 10.1.2

I'm on 10.1.2. Patch removes error. Thanks!

Patch from #6 is really helpful. I though i was loosing my mind because i couldn't find these "new links" after the changes in 10.1 Thank you!

I can confirm #15. I followed the steps and experienced the same results. The hidden field shows up when i go to translate the content.

Thanks TolstoyDotCom. I'm using views_conditional and have been having issues with this ( https://www.drupal.org/project/views_conditional/issues/3347741#comment-... 🐛 D10 "Invalid placeholder (context) with string" error Fixed ), but can confirm that the changes in #15 stop the error messages that were flooding the logs. For the record, the site is using 10.0.9 and views_conditional 1.5.

I test merge request mentioned in #10. Success! Error message no longer flooding the logs!

Am i missing something? i see the issue fork, but no merge request/patch to test.

J. → created an issue.

Would be great if we could theme these via twig!

Yes it was for 8.x-2.x-dev.

Thank you! I had same error. Patch #2 works for me on 10.0.9 using 2.0 branch.

Here's a patch for D10 compatability. I've manually tested in on 9.5 w/php8.1 and was able to send events to GTM. I had no problems manually testing it on D10 either.

Made a patch with the change suggested in #2. Manually testing and not seeing any issue in 9.5 or 10.0.7.

Patch applied cleanly on 9.5/php 8.1 and 10. Seems to be working correctly.

Thanks for the patch! I can confirm it applys cleanly to both 9.5 and 10 on php 8.1. I am seeing the same issue reported on https://www.drupal.org/project/product_taxonomy_filter/issues/3354323 🐛 Error in Drupal 10 - Drupal\Component\Plugin\Exception\PluginException: Plugin (entity:taxonomy_term) instance class "Drupal\taxonomy\Plugin\views\argument_validator\Term" does not exist Needs review , but only on D10.

Patch applied cleanly 9.5/php 8.1 and 10. Functions correctly from manual testing.

I'm hitting this issue too. Just updated to D10 and on Views 1.5.

User warning: Invalid placeholder (context) with string: "" in Drupal\Component\Render\FormattableMarkup::placeholderFormat() (line 245 of core/lib/Drupal/Component/Render/FormattableMarkup.php).

Patch applied cleanly on 9.5/php 8.1. Update status shows no issues. Good to go?

Patch applied cleaning on 9.5, php 8.1

Thanks. I hadn't been able to upgrade because when i would go to edit the translated node, the paragraph content had completely dissapeared. This patch is working on 9.5/php8.1 with dev version of layout_paragraphs. I can now see, edit and save translated layout_paragraph content.

Patch applied cleanly on php8.1 drupal 9.5.7. Error is gone for me too. Thank you!

If i implement a listener for the order assign event and do my own setting of customer/email does it skip implementing commerce's?

#4 works for me on D10 php8.1

Thank you for the patch. I was having issues with forms submitting with email adress just like that and triggering wierd errors on the server side. This fixed it.

I am using drupal 9.7 and php 7.4.

J. → created an issue.

Correct.

Works for me on 10.7, PHP 8.1

I hit this error:

Fatal error: Declaration of Drupal\slack_logger\Logger\SlackLogger::log($level, $message, array $context = []) must be compatible with Drupal\Core\Logger\RfcLoggerTrait::log($level, Stringable|string $message, array $context = []): void in /app/web/modules/contrib/slack_logger/src/Logger/SlackLogger.php on line 40

Modified patch according to suggestions here: https://www.drupal.org/node/3284415 → .

Otherwise, works for me on 10.7 php 8.1. I did not test on 9.

I think i found our problem. We aren't using any allowed patterns. So in our case $allowed_patterns is passing along an empty string, which then triggers the error in _string_to_array. This patch checks if $allowed_patterns has content before proceding.

Works using method described in #18 on D10/PHP 8.1

Patch is apply and no issues on D10.

Here's a go at a patch for this.

I replaced the call to commerce's assign method with modification of it that leaves email untouched in the case of anonymous users. I'm not sure if the OrderAssignEvent is needed in this case, but left it since i'm still new to what all this is doing and don't want to break anything. I did remove the optional $save_order parameter from the original function and defaulted to saving the order because i was unsure how to make it optional in this case.

I manually tested it for an anonymous and a user with an account. The checkout link worked correctly and the order went through for both.

Thank you for clarify that the assigning is necessary. I will be happy to work on a patch and i might post this as an issue on the commerce project as well.

J. → created an issue.

I don't understand how all this works, but i'm seeing the patch fail because the .info.yml file i get from composer has changes from the Drupal.org packaging script that the patch doesn't account for.

I am also unable to apply #7 https://www.drupal.org/files/issues/2022-12-12/redirect_after_login-3289... → to 2.7. I'm on D9.5 and php8.1.

Using: 8.x-3.x-dev, 9.5, and php 8.1.

Deprecated function: preg_match_all(): Passing null to parameter #2 ($subject) of type string is deprecated in Drupal\typed_data\PlaceholderResolver->scan() (line 185 of modules/contrib/typed_data/src/PlaceholderResolver.php).
Drupal\typed_data\PlaceholderResolver->scan(NULL) (Line: 53)
Drupal\typed_data\PlaceholderResolver->resolvePlaceholders(NULL, Array, NULL, Array) (Line: 167)
Drupal\typed_data\PlaceholderResolver->replacePlaceHolders(NULL, Array) (Line: 72)
Drupal\rules\Plugin\RulesDataProcessor\TokenProcessor->process(NULL, Object) (Line: 320)
Drupal\rules\Plugin\RulesExpression\ActionExpression->processValue(NULL, Array, Object) (Line: 297)
Drupal\rules\Plugin\RulesExpression\ActionExpression->processData(Object, Object) (Line: 83)

And

Deprecated function: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in Drupal\typed_data\PlaceholderResolver->replacePlaceHolders() (line 172 of modules/contrib/typed_data/src/PlaceholderResolver.php).
Drupal\typed_data\PlaceholderResolver->replacePlaceHolders(NULL, Array) (Line: 72)
Drupal\rules\Plugin\RulesDataProcessor\TokenProcessor->process(NULL, Object) (Line: 320)
Drupal\rules\Plugin\RulesExpression\ActionExpression->processValue(NULL, Array, Object) (Line: 297)
Drupal\rules\Plugin\RulesExpression\ActionExpression->processData(Object, Object) (Line: 83)

I had same deprecation messages for a rule that sent an email after a comment was submitted. The patch works for me clear the errors.

I am getting the error on 2.0.x-dev, 9.5, php 8.1. It happens after i logout/login.

Deprecated function: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in _string_to_array() (line 259 of modules/contrib/protected_forms/protected_forms.module).
_string_to_array(NULL) (Line: 81)
_protected_forms_validate(Array, Object)
call_user_func_array('_protected_forms_validate', Array) (Line: 82)
Drupal\Core\Form\FormValidator->executeValidateHandlers(Array, Object) (Line: 275)
Drupal\Core\Form\FormValidator->doValidateForm(Array, Object, 'user_login_form') (Line: 118)
Drupal\Core\Form\FormValidator->validateForm('user_login_form', Array, Object) (Line: 591)
Drupal\Core\Form\FormBuilder->processForm('user_login_form', Array, Object) (Line: 323)
Drupal\Core\Form\FormBuilder->buildForm(Object, Object) (Line: 73)
Drupal\Core\Controller\FormController->getContentResult(Object, Object)
call_user_func_array(Array, Array) (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 124)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 169)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 81)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 46)
Drupal\redirect_after_login\RedirectMiddleware->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 50)
Drupal\ban\BanMiddleware->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 718)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

J. → created an issue.

This is working for me as well.

Same question.

Apologies for not clarifying. I am on 9.4.10 using layout_paragraphs 2.0.2, not paragraphs. https://www.drupal.org/project/layout_paragraphs/releases/2.0.2 →

In case this helps, I also ran into problems with the table tooltip not showing up in paragraphs while using ckeditor5.

Found a similar problem described here: https://www.drupal.org/project/drupal/issues/3274937#comment-14824232 🐛 Get CKEditor 5 to work in (modal) dialogs Fixed . The css fix mentioned in #69 worked for me. I patched ckeditor5.dialog.fix.css and now table tooltip and linkit are working correctly.

#69 Solved table tooltip issue for me too!

I'm have problems with paragrahs and Linkit w/ckeditor 5 and this patch. I click the link icon and "nothing happens." When i opened the console window to inspect i noticed that the popup for linkit is behind the paragraph overlay.