The controller result claims to be providing relevant cache metadata, but leaked metadata was detected. Please ensure you are not rendering content too early. Returned object class: Drupal\Core\Cache\CacheableJsonResponse.

Created on 12 August 2022, over 2 years ago

Updated 16 March 2023, almost 2 years ago

Problem/Motivation

the decoupled router path (/router/translate-path?path=/) gives errror "The controller result claims to be providing relevant cache metadata, but leaked metadata was detected. Please ensure you are not rendering content too early. Returned object class: Drupal\Core\Cache\CacheableJsonResponse."

🐛 Bug report

Status

Needs work

Version

2.0

Component

Code

Created by

🇮🇳India abhinesh

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment almost 2 years ago →
🇮🇳India abhinesh
Comment almost 2 years ago →
🇮🇳India farhanmae Bengaluru
@abhinesh → I am getting the initial error after applying the patch from #9 🐛 The controller result claims to be providing relevant cache metadata, but leaked metadata was detected. Please ensure you are not rendering content too early. Returned object class: Drupal\Core\Cache\CacheableJsonResponse. Needs work

LogicException: The controller result claims to be providing relevant cache metadata, but leaked metadata was detected. Please ensure you are not rendering content too early. Returned object class: Drupal\Core\Cache\CacheableJsonResponse. in

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024