globexplorer → created an issue.
globexplorer → created an issue. See original summary → .
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
Fixed also with the following patch file.
globexplorer → changed the visibility of the branch 3.0.x to hidden.
globexplorer → changed the visibility of the branch 3490106-pagecache-fix to hidden.
globexplorer → changed the visibility of the branch dev-3490106-pagecache-fix to hidden.
globexplorer → created an issue.
globexplorer → created an issue. See original summary → .
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
Thank you @oleksandr.s! I will remove the comment dependency from the config and once done give you credit for it.
Thanks @oleksandr.s! The problem here is, that the scorm field in that version can only be attached to entities of type node. We have to change some other bits in code and in database table to address this properly. The code change here would be not enough. Furthermore using layout builder with no node in route would that not be the logical next problem. Once we addressed all relying issues I will credit you for that issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
Hi @oleksandr.s!
I think It would be better to remove the route match service at all. The node object can be retrieved from the fromatter ->getEntity() method itself.
see here:
// Read the entity id from url
$node = $items->getEntity();
if ($node instanceof NodeInterface) {
$nid = $node->id();
}
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
This means that you have still meta data for entity in your config but the code has gone.
fixed.
globexplorer → created an issue.
globexplorer → created an issue.
I can confirm this is an issue and I will prepare a patch.
Fixed with Issue #3451617.
This was fixed with the following Issue #3451617.
globexplorer → created an issue.
New feature was added.
Fixed.
globexplorer → created an issue.
globexplorer → created an issue.
Fixed with the following patch for 11.11.x
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.
globexplorer → created an issue.