Answers.Body: <p>This error is displayed when some Names for a relationship type do not match the Labels.</p>
  
  <p>For example in civicrm_relationship_type table you may have something like</p>
  
  <p>name_a_b = Mayor
  name_b_a = Mayor
  label_a_b = Mayor of
  label_b_a = Mayor is</p>
  
  <p>You can correct these either in SQL or via the UI</p>
  
  <hr>
  
  <p>UPDATE</p>
  
  <p>To identify the rows causing the issue </p>
  
  <pre><code>select name_a_b, label_a_b, name_b_a, label_b_a from civicrm_relationship_type where name_a_b &lt;&gt; label_a_b;
  select name_b_a, label_b_a from civicrm_relationship_type where name_b_a &lt;&gt; label_b_a;
  </code></pre>
  
  <p><strong>To fix we want to set the name = to the label</strong></p>
  
  <p>Make a temporary backup - this will be dropped when you log out of mysql.</p>
  
  <pre><code>create temporary table temp_civicrm_relationship_type as select * from civicrm_relationship_type;
  update civicrm_relationship_type set name_b_a = label_b_a where name_b_a &lt;&gt; label_b_a;
  update civicrm_relationship_type set name_a_b = label_a_b where name_a_b &lt;&gt; label_a_b;
  </code></pre>
  
  <p>Confirm that the number of rows updated matches result of the query.</p>
  
  <p>(nb I just grabbed this from a ticket in our own system but hope it is helpful in your case)</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-27T10:42:01.617Z
Answers.Text: A tiny addendum: it seems SQL is the only place for edits, since it looks different via CiviCRM GUI (at civicrm/admin/reltype?reset=1) and in, say, phpmyadmin.
Answers.UserDisplayName: yurg
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-27T10:47:24.230Z
Answers.Text: Just wondering what do we change to stay safe: name or label? One of this might be used/hard-coded somewhere (across templates for example)  so we may break things. I'd say it is labels, but not really sure. Besides, making labels the same as names might not always have a semantic sense.
Answers.UserDisplayName: yurg
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-23T22:28:19.457Z
Answers.LastActivityDate: 2018-07-28T00:33:32.850Z
Answers.LastEditDate: 2018-07-28T00:33:32.850Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>Subject says it all. Just wondering if anyone has seen something like this before?   </p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-07-23T21:33:09.297Z
Comments.Text: I've seen it but haven't yet dug into what is generating it.
Comments.UserDisplayName: Seamus Lee
Tags: <upgrade>
Title: CiviCRM upgrade from 4.6 to 5.3 > [warning] Both parameters should have an equal number of elements Relationship.php:2222
ThreadText: # CiviCRM upgrade from 4.6 to 5.3 > [warning] Both parameters should have an equal number of elements Relationship.php:2222
  
  (Asked by: username_0 on 2018-07-23)
  
  Subject says it all. Just wondering if anyone has seen something like this before?
  
  **Tags:** upgrade
  
  > **Comments:**
  > **username_1**: I've seen it but haven't yet dug into what is generating it.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2018-07-23. Score: 1 | Accepted answer
  
  This error is displayed when some Names for a relationship type do not match the Labels.
  
  For example in civicrm\_relationship\_type table you may have something like
  
  name\_a\_b = Mayor
  name\_b\_a = Mayor
  label\_a\_b = Mayor of
  label\_b\_a = Mayor is
  
  You can correct these either in SQL or via the UI
  
  ---
  
  UPDATE
  
  To identify the rows causing the issue
  
  ```
  select name_a_b, label_a_b, name_b_a, label_b_a from civicrm_relationship_type where name_a_b <> label_a_b;
  select name_b_a, label_b_a from civicrm_relationship_type where name_b_a <> label_b_a;
  
  ```
  
  **To fix we want to set the name = to the label**
  
  Make a temporary backup - this will be dropped when you log out of mysql.
  
  ```
  create temporary table temp_civicrm_relationship_type as select * from civicrm_relationship_type;
  update civicrm_relationship_type set name_b_a = label_b_a where name_b_a <> label_b_a;
  update civicrm_relationship_type set name_a_b = label_a_b where name_a_b <> label_a_b;
  
  ```
  
  Confirm that the number of rows updated matches result of the query.
  
  (nb I just grabbed this from a ticket in our own system but hope it is helpful in your case)
  
  > **Comments:**
  > **username_0**: A tiny addendum: it seems SQL is the only place for edits, since it looks different via CiviCRM GUI (at civicrm/admin/reltype?reset=1) and in, say, phpmyadmin.  
  > **username_0**: Just wondering what do we change to stay safe: name or label? One of this might be used/hard-coded somewhere (across templates for example)  so we may break things. I'd say it is labels, but not really sure. Besides, making labels the same as names might not always have a semantic sense.  
  
  ---
  
  