Answers.Body: <p>Part of the process that CiviCRM Entity uses to integrate is to read metadata on the civicrm API entities, and also for fields with options lists, it fetches those with an API call...
  This API call :</p>
  
  <pre><code>$result = civicrm_api3('Relationship', 'getoptions', [
    'field' =&gt; "relationship_type_id",
  ]);
  </code></pre>
  
  <p>Is what is producing the warning...</p>
  
  <p>I'm calling this a CiviCRM Core bug/issue..</p>
  
  <p>there is an issue here, I'll update it:
  <a href="https://lab.civicrm.org/dev/core/issues/268" rel="nofollow noreferrer">https://lab.civicrm.org/dev/core/issues/268</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-04T19:54:03.020Z
Answers.Text: i can work around this issue in CiviCRM Entity, I'll work up a patch for that
Answers.UserDisplayName: jackrabbithanna
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-29T13:51:49.193Z
Answers.Text: Has this issue ever been resolved, from either end? I'm still seeing this error filling my Drupal logs.
Answers.UserDisplayName: somnolentsurfer
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-30T00:50:01.940Z
Answers.Text: I don't believe so. I ended up manually updating relationship types, to make sure not exact same names used for 'a' and 'b' in one relationship type. Updating name_a_b or name_b_a didn't seem to have adverse affects .. only if customs look for relationship types specifically by those names.
Answers.UserDisplayName: jackrabbithanna
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-04T18:19:17.813Z
Answers.LastActivityDate: 2019-01-04T18:19:17.813Z
Answers.UserDisplayName: jackrabbithanna
Body: <blockquote>
    <p>Blockquote
    Warning: array_combine(): Both parameters should have an equal number of elements in CRM_Contact_BAO_Relationship::buildRelationshipTypeOptions() (line 2250 of /home/i571020/membership.irishjudoassociation.ie/sites/all/modules/civicrm/CRM/Contact/BAO/Relationship.php).</p>
  </blockquote>
  
  <p>I've started getting this error after enabling the module. I can see all the options in views, rules etc. but the warning is visible in the back-end. Is this something in my relationships that's not right or else?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-01-04T16:13:53.673Z
Comments.Text: I see this notice all the time as well....hasn't seemed to cause any problems...I've seen this issue about it too: https://lab.civicrm.org/dev/core/issues/268
Comments.UserDisplayName: jackrabbithanna
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-01-04T16:19:37.103Z
Comments.Text: this didn't start appearing until sometime in the 5.x series of CiviCRM as well...
Comments.UserDisplayName: jackrabbithanna
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-05-28T17:10:54.377Z
Comments.Text: I've the same issue. Any solution?
Comments.UserDisplayName: bass
Tags: <civicrm-entity>
Title: Error after installing Civi Entity module
ThreadText: # Error after installing Civi Entity module
  
  (Asked by: username_0 on 2019-01-04)
  
  > Blockquote
  > Warning: array\_combine(): Both parameters should have an equal number of elements in CRM\_Contact\_BAO\_Relationship::buildRelationshipTypeOptions() (line 2250 of /home/i571020/membership.irishjudoassociation.ie/sites/all/modules/civicrm/CRM/Contact/BAO/Relationship.php).
  
  I've started getting this error after enabling the module. I can see all the options in views, rules etc. but the warning is visible in the back-end. Is this something in my relationships that's not right or else?
  
  **Tags:** civicrm-entity
  
  > **Comments:**
  > **username_1**: I see this notice all the time as well....hasn't seemed to cause any problems...I've seen this issue about it too: https://lab.civicrm.org/dev/core/issues/268  
  > **username_1**: this didn't start appearing until sometime in the 5.x series of CiviCRM as well...  
  > **username_2**: I've the same issue. Any solution?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-01-04. Score: 3
  
  Part of the process that CiviCRM Entity uses to integrate is to read metadata on the civicrm API entities, and also for fields with options lists, it fetches those with an API call...
  This API call :
  
  ```
  $result = civicrm_api3('Relationship', 'getoptions', [
    'field' => "relationship_type_id",
  ]);
  
  ```
  
  Is what is producing the warning...
  
  I'm calling this a CiviCRM Core bug/issue..
  
  there is an issue here, I'll update it:
  <https://lab.civicrm.org/dev/core/issues/268>
  
  > **Comments:**
  > **username_1**: i can work around this issue in CiviCRM Entity, I'll work up a patch for that  
  > **username_3**: Has this issue ever been resolved, from either end? I'm still seeing this error filling my Drupal logs.  
  > **username_1**: I don't believe so. I ended up manually updating relationship types, to make sure not exact same names used for 'a' and 'b' in one relationship type. Updating name_a_b or name_b_a didn't seem to have adverse affects .. only if customs look for relationship types specifically by those names.  
  
  ---
  
  