Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
batch system
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Jun 2014 at 20:14 UTC
Updated:
25 Feb 2015 at 14:54 UTC
Jump to comment: Most recent
Comments
Comment #1
Crell commentedThe broader issue here is that batch API (and a few other edge cases) need to render totally non-standard pages. Currently they do so by going all the way up to Response, complete with using the rendering services themselves. While that can work, it's obviously sub-optimal and leads to bugs like this.
IMO the correct solution is for such edge cases to return their own HtmlFragmentInterface-implementing objects, and then have view listeners that listen for those objects and convert them to pages their own way rather than the default way. As long as they have a higher priority than the default one it should work fine with the way the system is setup, and be consistent with how we'r eusing the view listeners right now.
Comment #2
dawehnerDidn't batch API just needed a way to render a page without any blocks? Not sure but it feels like this should be doable with the display architecture.
Comment #3
dawehnerIt doesn't do any longer.