I created a Feature that includes two blocks from my dev server. When I import the Feature into my staging server and go to the Features page (/admin/build/features), the state of the Feature is marked as "Checking...". I click 'Recreate' and 'Revert Components' but the state still remains as "Checking". I've tried clearing caches, updating DB, optimizing DB but no joy. All of my other features seem to work fine. Any ideas?
Comments
Comment #1
rootdownmedia commentedI should note that I receive the following error when I enable the FE_block module:
user warning: Table 'fe_block_boxes' already exists query: CREATE TABLE fe_block_boxes ( `bid` INT unsigned NOT NULL DEFAULT 0, `machine_name` VARCHAR(32) NOT NULL DEFAULT '', PRIMARY KEY (bid), INDEX machine_name (machine_name) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /Applications/MAMP/vhosts/XXX/wwwroot/includes/database.inc on line 529.
Comment #2
makara commented"Stuck on checking" should have been fixed now. The warning in #1 seems a general error that is caused by installing a module twice.
Comment #4
sk33lz commentedI have been trying to figure out what is going on here and I feel I am having the same issue. I am using a fresh installation of all related modules and Drupal and I am trying to import a feature from another site that is fully updated. Things worked great, but my blocks didn't carry through to my panels, so I enabled this module. I have enabled block settings and now my features do not work properly, and I get stuck on the "Checking..." status. I have a feeling that this is caused by enabling blocks that are not custom blocks and are owned by other modules within the feature. It doesn't seem that Features Extra covers these type of blocks and it could make the whole feature fail. I am going to try and test this and reply here. Everything worked fine before I enabled the block settings export in my feature.
Comment #5
amarcaurele commentedDid not get any errors or warnings but same issue as poster. we tried many ways
block content alone, block content + block settings and block settings alone.
No blocks were installed. And status was stuck on Checking.
any new fixes ? thank you all.
Comment #6
nodiac commentedIf a Feature at admin/build/features is stuck on "Checking..." then enable the console panel in Firebug and take a look at what's going on. Even if you're getting 200 OK HTTP headers, the response will likely include the error you need to debug. In my case, I had a Feature that was depending on a hardcoded path that didn't exist on the local filesystem.