Managing blocks [#2125089]

I want to manage my content (blocks as a minimum) between sites and I was wondering if this is the module for it. I'm using it to manage things like content authoring and metatags to progress from dev, test and production. I can't find any documentation for blocks.

Apologies if this is the wrong module. I'd appreciate any suggestions for alternatives.

Comments

Comment #1

PedroKTFC CreditAttribution: PedroKTFC commented 1 November 2013 at 13:47

Title:

Managin blocks

» Managing blocks

Comment #2

dagmar

Spanish

Argentina

CreditAttribution: dagmar commented 2 November 2013 at 20:54

This module is intended to manage configuration, not content. If you want to export block definitions, take a look to the Bean module first.

Comment #3

PedroKTFC CreditAttribution: PedroKTFC commented 5 November 2013 at 22:25

Thanks, I'll look at that as an option. As an alternative, could blocks be managed as configuration with the boxes module?

Comment #4

dagmar

Spanish

Argentina

CreditAttribution: dagmar commented 17 November 2013 at 16:24

Yes, I think that is another valid option.

In fact I think that should work out of the box with Configuration Management since boxes uses CTools as export system.

Comment #5

joshmiller

he/him

English

Indianapolis, Indiana, USA

CreditAttribution: joshmiller commented 20 June 2014 at 19:19

Version:	7.x-2.0-alpha3	» 7.x-2.x-dev
Component:	Miscellaneous	» Documentation
Category:	Feature request	» Task

Confirmed that the boxes modules works with Configuration Management and that the Beans module (while cool) can easily export bundles of blocks it cannot export content even with the included Bean UUID module.

So I'm marking this a documentation issue and urge the maintainer to note this in the readme.txt and on the module page that the "best practice" for managing blocks is the boxes module. This would have saved me about an hours worth of testing and I'm sure I'm not the only one.

Josh