In D7, placeholders for t() would begin with either @, %, or !. Placeholders beginning @ were passed through check_plain(), placeholders beginning %were wrapped in tags and passed through check_plain(), and placeholders beginning ! were raw HTML to be added unchanged.

In D8, the placeholder prefix ! has been deprecated, as discussed in https://www.drupal.org/node/2506427

So the Devel module code need to update accordingly. Thanks.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jalpesh created an issue. See original summary.

jalpesh’s picture

Assigned: jalpesh » Unassigned
Status: Active » Needs review
FileSize
13.65 KB

I have added a patch for same. Thanks.

lussoluca’s picture

Status: Needs review » Reviewed & tested by the community

There's a lot to work for porting devel_node_access to D8 but this is a good start.

  • salvis committed d4a4c82 on 8.x-1.x
    Issue #2758617 by jalpesh: Need to change !placeholder in t().
    
salvis’s picture

Status: Reviewed & tested by the community » Fixed
+++ b/devel_node_access/src/Plugin/Block/DnaBlock.php
@@ -544,10 +544,10 @@ class DnaBlock extends BlockBase implements ContainerFactoryPluginInterface {
-          '#markup' => t("You have errors in your !na table! You may be able to fix these for now by running !Rebuild_permissions, but this is likely to destroy the evidence and make it impossible to identify the underlying issues. If you don't fix those, the errors will probably come back again. <br /> DON'T do this just yet if you intend to ask for help with this situation.", $variables),
+          '#markup' => t("You have errors in your !na table! You may be able to fix these for now by running @Rebuild_permissions, but this is likely to destroy the evidence and make it impossible to identify the underlying issues. If you don't fix those, the errors will probably come back again. <br /> DON'T do this just yet if you intend to ask for help with this situation.", $variables),

Here's another !na -- I'm fixing that one as well. :-)

Thanks for the patch, jalpesh!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.