Hello,

I'm evaluating the new Workspaces module.

I'm cheking the behavior with custom blocks, but I have the following error just after updating the block on the Custom block library page (admin/structure/block/block-content):
Drupal\Core\Entity\Exception\UndefinedLinkTemplateException: No link template 'revision' found for the 'block_content' entity type in Drupal\Core\Entity\Entity->toUrl() (line 224 of /var/www/docroot/core/lib/Drupal/Core/Entity/Entity.php).

On the front website however, the block renders well in the right version, when switching workspaces.

How to reproduce:

  1. Switch to a workspace (in my case, this is not the Live one)
  2. Go to admin/structure/block/block-content and update a custom block (custom type)
  3. After saving the block, you get the error
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dolu created an issue. See original summary.

Ludo.R’s picture

Issue summary: View changes
amateescu’s picture

Title: No link template 'revision' found for the 'block_content' entity type » StringFormatter should check whether an entity type has a 'revision' link template
Version: 8.6.2 » 8.6.x-dev
Component: workspaces.module » field system
Status: Active » Needs review
Issue tags: +Workflow Initiative
FileSize
2.3 KB
3.52 KB

The problem here is actually in \Drupal\Core\Field\Plugin\Field\FieldFormatter\StringFormatter, not related to Workspaces at all :)

Here's a fix for it.

The last submitted patch, 3: 3013029-test-only.patch, failed testing. View results

Ludo.R’s picture

I confirm that this patch solves the problem mentionned above.

Now I see that there may be another issue - related to Workspace this time - but I4ll create a new ticket.

Thanks! :)

amateescu’s picture

Happy to help :) If you also looked at the code in the patch and you agree with it, you can set the status of the issue to RTBC, especially since you already tested it manually.

driverok’s picture

Status: Needs review » Reviewed & tested by the community

I was able to reproduce the issue locally on 8.6.x branch with steps to reproduce provided and I confirm that patch #3 fixed the issue.

alexpott’s picture

Status: Reviewed & tested by the community » Fixed

Crediting @dolu for reporting the issue.

Committed and pushed 58cffff60d to 8.7.x and 7feaa9647a to 8.6.x. Thanks!

  • alexpott committed 58cffff on 8.7.x
    Issue #3013029 by amateescu, dolu: StringFormatter should check whether...

  • alexpott committed 7feaa96 on 8.6.x
    Issue #3013029 by amateescu, dolu: StringFormatter should check whether...

Status: Fixed » Closed (fixed)

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