| Project: | Features |
| Version: | 7.x-1.0 |
| Component: | Block |
| Category: | bug report |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I am using Homebox 7.x.2.beta6 and have created homebox pages for each role in my site, along with a page
Since I am not sure if this is a problem with homebox or features for each users profile. so far so good.
Each page has blocks assigned - some are view displays, some are php/html blocks. no problems with either type of block locally.
In order to integrate these homebox pages with work done by others on my team I have created a feature using the features module. Features captures the homebox pages, blocks, and settings for the blocks (including all homebox region and title setting), along with all the other settings and permissions one might expect. However when importing the feature to the Dev environment from my local workstation to integrate the work product and reverting the feature in the new environment, all settings for the php/html blocks fail to revert. the settings for views block displays revert as expected.
The upshot is that each time I move the feature from Local to Dev to Staging I must re work the layout for each homebox page and flush the settings. I need to resolve this issue before releasing the feature to production. I'm sure that the users will not be happy to have their settings flushed when new blocks are added in future releases.
Further review indicates that there is a problem in the processing of custom blocks and the processing of serialized data using the bid field in the blocks_custom table without joining to the FE_boxes table and using the machine name field.
Local env = Quickstart Ubuntu
Dev Env = Windows 7 enterprise with uniserver
Staging Env = Windows 7 enterprise with uniserver
Drupal 7.16 in all environments