CiviCRM Community Forums (archive)

We did an upgrade to 4.3.8 last night that broke editing contact info with profiles, but only for one of our profiles; a rather involved one that has two contact references, custom data fields, and uses CiviRelate, among other things. Trying to edit existing contact info with this profile resulted in a WSOD with the following PHP error:

PHP Fatal error:  Call to undefined method stdClass::build_join() in /home/musicnova/www/www/sites/all/modules/views/plugins/views_plugin_query_default.inc on line 1313


plus the following notice, from the Drupal log:
Notice: Undefined index: relationship in views_plugin_query_default->ensure_table() (line 606 of /home/musicnova/www/www/sites/all/modules/views/plugins/views_plugin_query_default.inc).
I noticed that I could still edit some of the same profile fields of a given contact with a different profile with far fewer fields, so I rebuilt the profile in question, field-by-field, refreshing its edit screen each time to make sure it wasn't WSODing. Once I added in all the fields and pointed CiviRelate at it, it worked fine. I'm really not sure what happened but I can only assume it's an issue with the way Profiles are created in 4.3.8 being somehow different from 4.2.14.

What information can I provide here that might help identify the issue? Is it worth pursuing?

I had a breeze through that JIRA bit and I'm not sure it's related. It looks, on the surface, that there's something about the way profiles were created as data entities in 4.2 that isn't forward-compatible to 4.3. The custom fields all still work fine after the upgrade, so rebuilding the profile is not a huge deal time-wise. I was just thinking that maybe something could be included in the upgrade script that processes the profiles and brings them up to date structurally, but others on this board are way better able to make that call than I.