- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
Re-read this today.
I see where you're coming from. I understand that in very specific scenarios, what you're asking for would help. But in most cases, it would not.
I find that the placeholder appears on the first load after clearing cache, but on subsequent loads the paragraph is already fully rendered.
π This means that this module works fine already. That's literally the behavior described on the project page π
What you're asking for, is a different behavior. You're asking to not prime the page cache even when it could be primed.
And in fact β¦ this is already supported π€
- Eventually, Sessionless BigPipe calls
\Drupal\big_pipe_sessionless\Render\BigPipeSessionless::primePageCache()
with aHtmlResponse
object to prime the Page Cache with. - That calls
\Drupal\page_cache\StackMiddleware\PageCache::storeResponse()
, which contains this logic:
// Allow policy rules to further restrict which responses to cache. if ($this->responsePolicy->check($response, $request) === ResponsePolicyInterface::DENY) { return FALSE; }
- In other words: the Page Cache will not be primed if BigPipe Paragraphs were to define a response policy that detects whether the response contains rendered BigPipe Paragraphs placeholders β¦ which would give you exactly the behavior you're asking for π
- Eventually, Sessionless BigPipe calls
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
Ensured #8 would not go to waste by opening β¨ Allow configuring to *never* store in Page Cache when using Sessionless BigPipe Active . π
Automatically closed - issue fixed for 2 weeks with no activity.