It seems that it is not being processed or rendered in the correct format.
{% autoescape false %}: This disables autoescape for all content within the block. Any variable or text placed inside this block will not be escaped.
But you don't need to add this code and you can use the |raw filter to apply it specifically to a single variable or expression.
So to make sure that the specific formatting is applied the |check_markup filter is added.
davidcr → made their first commit to this issue’s fork.
In the EntityUnifiedFieldsDiffLayout file there is also the same code. So the same proposed code was added to the file.
Hi @Rajan Kumar@2026 sorry for my English :)
It works with that change, but there are codes from block_diff_ui module. This does not alter anything because for some reason it is not taking the custom forms. If you change the route if it takes those custom forms.
I only have one doubt, if later for some reason or some changes in the Group module starts to work with the custom forms, maybe there we can have problems.
In the dev branch there is a possible solution. Another solution is to go to the following path "admin/group/types/manage/GROUP_TYPE" and in the Creator settings section deactivate the option "Group creator must complete their membership".
Hello @AndreaR25, you can use version 1.1.x and later, as it is not available for versions 1.0.x.
Sorry for my English, I was testing the module on a Drupal 9 installation, and I'm seeing the same error you reported @Cangurin cleanups. After quickly reviewing the error, I've realized that the 'l()' function is being used, which is deprecated. Perhaps the following code could be an idea to resolve the error.
NodeController.php::120 file.
use Drupal\Core\Link;
if ($vid != $html_page->getRevisionId()) {
$link = Link::fromTextAndUrl($date, new Url('entity.html_page.revision', [
'html_page' => $html_page->id(),
'html_page_revision' => $vid,
]))->toString();
}
else {
$link = $html_page->toLink($date)->toString();
}
The solution is in DEV until the next release.
Another alternative solution is to go to "admin/structure/types/manage/TYPE_NAME/form-display", edit the field configurations, and save.