Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Hello, I just tried fe_block in a clean Drupal installation, created a block, exported, deleted that block and imported the feature. That block is not present, so fe_block does not work. On the features interfaces is on status "ovverriden". Since is a clean installation I am using Bartik theme
Any idea on whats wrong? I also tried the dev version , still no block
Comment | File | Size | Author |
---|---|---|---|
#6 | 1947816-6-features_extra-menu_block_support.patch | 1.48 KB | pfrenssen |
Comments
Comment #1
stilllife00 CreditAttribution: stilllife00 commentedUpdate, deleting the block was the problem (then I needed to change the node machine name on the exported files). So if we suppose to import the node on a different website (with no need to delete anything) shouldn't e any problem. Still, fe_block seems not working with blocks of the module "menu_blocks".
Comment #2
stilllife00 CreditAttribution: stilllife00 commentedIt seems that when exporting "menu_blocks" it doesn't have an option to export also the "boxes" inc file so no block is created on the drupal's blocks interfaces. Is there a way to properly export menu_blocks ? Is this a bug or a missing feature?
Comment #3
pfrenssenNo, Menu Blocks are not yet supported.
Comment #4
sokrplare CreditAttribution: sokrplare commentedLooks like they kinda are, but it takes some strongarming (sorry ;). See #1894280: Exporting Menu Blocks with Features Extra and Strongarm for how to do it.
Comment #5
pfrenssenThanks for linking that issue, DYdave did a great job explaining how to export menu blocks with Features Extra and Strongarm. Reading through this it seems like adding support for Menu Blocks to Features Extra could be done quite easily.
Comment #6
pfrenssenHere is an initial patch. I have just tested a simple export and it seems to work. I will commit this in branch 1947816 and start working on a test.
Comment #7
pfrenssenLet's run the existing tests on it.
Comment #8
pfrenssenThe menu blocks also use numeric block ids, so we need to assign them a machine name to be avoid conflicts. Currently FE Block only supports machine names for the core Block module. The numeric ids are also used in the settings, so we cannot simply export them with Strongarm. The variables should get renamed as well.
I also just discovered #693302: Add API for exportable menu_blocks / Features integration. That issue converts the Menu Block module to use CTools to store and export menu blocks, doing away with the variables completely. That is a nice approach, but it would conflict with this issue if it would get into Menu Block 7.x-2.x.
At least for now this issue is blocked on the numeric IDs. I've created a separate issue to address this: #1994200: Provide machine names for other modules. Will postpone this issue until that gets in.