Upon running update.php and attempting to update to the dev April 24 version of fc, I received these bad WSOD errors during the update process:

  • Notice: Undefined index: fc handler class in /.../sites/all/modules/fc/fc.inc on line 12
  • Exception: fc handler class <em class="placeholder"></em> not found or not suitable in fcComplete::build() (line 17 of /.../sites/all/modules/fc/fc.inc).

Comments

rlmumford’s picture

rlmumford
Primary language English
Location Manchester
commented

Does this still happen with the latest dev?

deanflory’s picture

deanflory commented

7.x-1.x-dev 2014-Apr-24 was the one I mentioned, the latest dev (unless a new one hasn't shown up yet on the project page).

rlmumford’s picture

rlmumford
Primary language English
Location Manchester
commented

What entity type were you experiencing the problem with?

The issue is stemming from the fact that an entity type on your site does to have the 'fc handler class' set in its entity info, this key should be being set on all entity types that are fieldable by default - see fc_entity_info_alter in fc.module.

Either you have an entity that that isn't fieldable that is attempting to have its completeness calculated. OR fieldComplete is trying to work out completeness before the entity info cache has been cleared, try running entity_info_clear_cache() from somewhere (drush or devel/php).

deanflory’s picture

deanflory commented

I'll have to review all entities to see if I happened to check enabling fc, as I really haven't even gotten around to setting it up yet.

It's also odd this happened on the update.php page, where there are no nodes or field completedness. I'll reply later when I have more info but am hesitant to update to the version that produced the WSOD error, will see later.

deanflory’s picture

deanflory commented

Doh! Ran into this when updating again. Grrr

deanflory’s picture

deanflory commented

And did it again. 3rd time it's on me. Waiting for a huge backup to download just to re-up the old fc, just to disable it. Not going to forget to get rid of this module this time.

  • Notice: Undefined index: fc handler class in /.../sites/all/modules/fc/fc.inc on line 12
  • Exception: fc handler class <em class="placeholder"></em> not found or not suitable in fcComplete::build() (line 17 of /.../sites/all/modules/fc/fc.inc).

These two module errors break the site.

Since I really haven't set up fc on any entities/nodes/fields, I'm not sure why this would be happening on my home page which is a ctools page manager page that has lots of views. Plus, since I'm not using a "<em class="placeholder"></em>" anywhere that I know of, I'm not sure where that's coming from.

Done with this, no more time for this. Maybe I'll check back in 6 months to see if it's matured.

deanflory’s picture

deanflory commented
Issue summary: View changes
deanflory’s picture

deanflory commented

I think the issues stem from this submodule since disabling it makes the errors go away (in limited testing):
Field Complete Field Groups
7.x-1.0-rc2+11-dev

I had definitely not yet set up Field Complete on any of my Groups fields.

deanflory’s picture

deanflory commented
Status: Active » Needs work
adaddinsane’s picture

adaddinsane
him/he/his
commented

I'm thinking that if this is happening during update.php we have to disable the whole completeness process during an update. Which is not unreasonable - it should never be needed at that stage.

So the question then is what indication is there that update.php is running and where would we need to put the checks. (Certainly any of the field hooks, and probably all the entity hooks.)

Actually there's a justification for not having it "switched off" during any drush command (I think).

Any other thoughts?