Thread

After updating to EE 2.6 a number of pages are throwing PHP errors at me. The error is only displayed for me or anyone else with Super Admin level based on the output and debugging settings. But there concerning enough that I’d like to fix whatever the underlying issue is.

The three errors, which are repeated numerous times depending on the page are as follows:

A PHP Error was encountered
Severity: Notice
Message: Undefined offset: 0
Filename: relationship_parser/Tree_builder.php
Line Number: 402

A PHP Error was encountered
Severity: Warning
Message: array_keys() expects parameter 1 to be array, null given
Filename: relationship_parser/Tree_builder.php
Line Number: 402

A PHP Error was encountered
Severity: Warning
Message: Invalid argument supplied for foreach()
Filename: relationship_parser/Tree_builder.php
Line Number: 413

Any help on fixing this would be super helpful.

I’m seeing this too. Has anyone figured out a solution?

Me too! Looks like its the new relationship fieldtype. Looks like it happens when an entry does not have any relationships… in particular I am using {parents id="myrelatedfield"}{/parents}

If there are no parents, then this line works OK:

{if parents:no_results}
Sorry, there are no projects in this programme
{/if}

But in addition to this I get the PHP notices too. As soon as add a relationship, notices go away.

I just upgraded my site to 2.6.1 and confirm that the errors are still present in that version.

Yep! Same problem here!

I’m getting five php errors in any Edit Field page (the Custom Field Type creation page, where you select the fieldtype, enter usage instructions, etc.). If I install the Relationship fieldtype (in addition to the Relationships fieldtype), then I get nine php error messages. Plus the theming of the Edit Field page is wonky. Text too large.

For me, the problem was Denza’s Multi Relationships fieldtype. After I uninstalled it, no more php notices and EE’s relationships fieldtype was usable. Prior to uninstalling Multi Relationships, it was impossible to use EE’s fieldtype; it generated an error and in the error was a mention of Denza’s fieldtype. Luckily, this was a site still in early development, so no data was lost.

EE’s fieldtype isn’t as good as Denza’s so I need to find a replacement. Any problems with Playa?

I have exactly same error after update to EE 2.6.1.

Any solution?

I eventually “solved” this by changing line 476 in expressionengine/libraries/relationship_parset/Tree_builder.php to this:

if ($entry_id == NULL || $field_id == 0)

I have no idea if this is just masking other, deeper problems or if it will have any ill effects, but so far it seems to do the trick.

Awesome - The above worked for me. No more php errors.

Has anyone found a solution to this besides the script rewrite? Also, PHP errors notwithstanding, are the relationship fields otherwise working for you? I’m getting these same errors after upgrading from 1.7.2 to 2.6.1, and the relationship field data is not displaying on the published entry pages.

I haven’t found a solution that works - the above solution doesn’t work for me - but I can confirm that the relationship fields are working for me. Granted, my upgrade wasn’t from 1.7 so I’m not sure what the issue could be for you.

I found that I needed to make some changes to my templates to accommodate the new relationship field type. Specifically, I had some {if} statements that broke with the new relationship field.

Same issue here:

http://ellislab.com/forums/viewthread/238124/

Think it’s a PHP bug…

Definite bug when not adding a “field” parameter to Parents tag and no relationship found.

You could add a field or rewrite 476 as above and add this to line 402

if($leaves){
 $field_ids = array_keys($leaves[$depth]);
}else{     
 $field_ids[0] = 0;
}

Not elegant but works.

I’ve just had this error again on 2.8.1. Turned out that some entries had been deleted, but their relationship entry was still in the exp_relationships table, so it was looping through looking for non-existent entries. Deleted them from the table and all is well.

Different version of EE of course, so might be an unrelated issue, but thought I’d post just in case.

If it helps:

DELETE FROM exp_relationships WHERE parent_id = XX OR parent_id = XX OR ...