Unresolved dependency for fe_block

... same here

Hi guys,

Thank you very much for your interest for the Block Class module and for posting this issue. It's greatly appreciated and I certainly apologize for the delay of this reply.

Unfortunately, I'm not going to be able to help much on this issue as I have never personally encountered this problem before and I don't really have the time to specifically test this.
However, doing a quick search yielded a lot of results. It doesn't seem like this problem would be specifically related with Block Class, since many other modules have encountered the exact same issue and some solutions have been proposed:

• Just download the module that's requested:
  Unresolved dependency error when updating
  #1871008: Unresolved dependency context (Missing)
  #2509346: Colorbox stopping update.php
  (and maybe uninstall it after the update, if it's unnessary/not required anymore)
• #1095460: "unresolved dependency"
• #2452825: Upon update: Unresolved dependency elements (missing)
• Webform: #2196491: Cannot update to Drupal 7.26 because I get the error webform has Unresolved dependency
• #1566356: Unresolved Dependency Updating from 7.12 to 7.14
• Administration menu: #1405212: Requirements problem (Unresolved dependency, System Version >=7.12 required)
• Multiple unresolved dependencies after update
• #2347267: Unresolved dependency to update
• and many more...

I guess it was just a matter of time before this issue would hit Block Class and be reported in our tracker :D.

In many of these tickets it is actually suggested that the users perhaps didn't perform the update fully/correctly (just updating some/certain modules)... you might want to make sure this isn't your case.

if FE_block is a required module should we be updating the list of required modules on the main page?

fe_block is not a required by block_class. It is required by block_class_fe_block_test which is a module only used for automated testing.
Now it certainly comes as a mystery to me as to why a module that's only needed for SimpleTests/hidden would actually trigger this kind of Unresolved dependency error.
However, strictly speaking: YES it works as designed, block_class_fe_block_test is a module, yes it has a dependency to Features Extra's fe_block, so yes, indeed, it should trigger an error if the required dependencies were not met.

Lastly, I know this may sound a little crafty, but since the unresolved dependency error is only triggered because of block_class_fe_block_test, which is a hidden module only used for Automated testing (it's not a functional module), then another solution that could work fine would be to either remove the test folder from your block_class' folder, or comment the problematic dependencies in the file block_class_fe_block_test.info, for example.
Whether you restore the files or not doesn't really matter, unless you plan on running SimpleTests for the module, which would greatly surprise me.

I hope I was able to answer your questions on this Unresolved dependency error and that I didn't misunderstand your initial requests.

Since I believe you should have at your disposal a few acceptable solutions, I allowed myself to mark this issue as Fixed for now, but feel free to re-open it, or post a new ticket, at any time if you have any further objections with the solution suggested in this ticket (we would surely be happy to hear your feedback).

In any case, please let us know if you would have any more questions, comments, feedback, issues, objections, suggestions or concerns on any aspects of this comment or the module in general, I would be glad to provide more information or explain in more details.

Thanks again very much for reporting this issue and in advance to everyone for your help, reviews, testing, feedback and participation in this module's issue tracker.
Cheers!