Block management in controllers other than in PageBundle

Description

Background

Block management must be possible on pages outside the PageBundle also, to decorate other pages with blocks.

Requirements

  • When the controller uses a theme view there must be an Edit button on that page also (for example the item action in the ArticleController)

  • You must be able to add blocks, the same as on PageController pages

  • Blocks will be saved based on controller action and channel. If the controller has parameters the same blocks will be used for each parameter (for example every news article will have the same blocks)

  • I think the view the controller uses for its output (in this example the article) will be fixed (because it is not a block area), but preferably this can be moved

Currently, the base view of the theme will be used, it might be a future feature to choose the template that will be used (maybe with )

Technical tasks

None

Deployment actions

put content block around base template grid
{% block content %}
{{ integrated_grid('main') }}
{% endblock %}

integrated block and menu edit variables become request variables

integrated_block_edit|default -> app.request.attributes.get('integrated_block_edit')

integrated_menu_edit|default -> app.request.attributes.get('integrated_menu_edit')

Activity

Show:
Maartje Wessels-Wouda
June 6, 2017, 6:31 AM

Deze zou jij toch oppakken? Ik heb het issue op je naam gezet!

API
June 7, 2017, 12:54 PM

.Notificatie preview gestuurd naar Integrated Marijn (marijn@e-active.nl)

Marijn Otte
June 8, 2017, 2:47 PM

All blocks in columns seem to disappear after editing

Ger Jan van den Bosch
June 9, 2017, 11:13 AM

bug wordt opgelost in

API
June 9, 2017, 2:04 PM

.Notificatie oplevering gestuurd naar Integrated Marijn (marijn@e-active.nl)

Assignee

Unassigned

Client

Integrated Marijn

Epic Link

Sprint

None

Fix versions

Configure