Bootstrap 7.x-3.8 breaks dpm() Krumo and string output

This isn't a devel issue.

I have not found a solution to this issue. Appears to still be a problem.

***EDIT*** SEE THE PARENT ISSUE FOR THE AWESOME PATCH TO devel ***EDIT***

***EDIT*** THANKS to @mustanggb and @markcarver ***EDIT***
oh, found solution.

looks like this is a reasonable solution.

https://www.drupal.org/node/2824575#comment-11908224

looks like this is a reasonable solution.

No, it's not. Read the comment below the comment you mentioned above (which I have now unpublished) https://www.drupal.org/node/2824575#comment-11908246.

actually, the forget comment #4 , the real solution is this patch to the devel module.

#2855666: Make Krumo compatible with XSS injection protection to drupal_set_message()

see parent issue for the patch that works flawlessly.

mytheme is a subteme of bootstrap.. I don't know how good is that approach but i simply override the bootstrap_status_messages function and replaced it with the core function in my theme

<?php

function subtheme_status_messages($variables){
  $display = $variables['display'];
  $output = '';

  $status_heading = array(
    'status' => t('Status message'),
    'error' => t('Error message'),
    'warning' => t('Warning message'),
  );
  foreach (drupal_get_messages($display) as $type => $messages) {
    $output .= "<div class=\"messages $type\">\n";
    if (!empty($status_heading[$type])) {
      $output .= '<h2 class="element-invisible">' . $status_heading[$type] . "</h2>\n";
    }
    if (count($messages) > 1) {
      $output .= " <ul>\n";
      foreach ($messages as $message) {
        $output .= '  <li>' . $message . "</li>\n";
      }
      $output .= " </ul>\n";
    }
    else {
      $output .= reset($messages);
    }
    $output .= "</div>\n";
  }
  return $output;
}

?>

#9 worked perfectly... been wrestling with trying to develop with the messed up display for a while. Thanks for posting rmajed

Additionally:

change "subtheme" to the machine name of your active theme. You can get this by going to the settings page of your subtheme, and look at the url. i.e. /admin/appearance/settings/[theme machinename]. The first line will be:
function [theme machinename]_status_messages($variables)

Unfortunately #6 is not a real solution, but #9 works.

@szt , #6 is the correct solution. There was a security issue in bootstrap that was resolved , unfortunately the solution meant that the current devel module will not work with bootstrap. The solution is to replace the devel module with the latest dev release of devel and then to patch the devel module with this patch.

This is why this issue is closed as a duplicate.

Please do not recommend a hacker solution to others. The correct solution is to patch the devel module and it would be best if the maintainer of the devel module gets busy and publishes a new release of devel with the solution.

I had this issue too. The easiest way out is in Devel settings at /admin/config/development/devel

set "Krumo backtrace above the rendered page"

and voilá, no more dependency on themes.

Ré: #13 Nice workaround

#9 works for me
#13 does not on drupal commerce carts

#6 worked
#13 did not