Answers.Body: <p>we were able to update CiviCRM from ver. 4.6.18 to version 5.2.1! I will tell you below how we solved the problem:</p>
  
  <p>a) we realized that we had 3 extensions (CiviVolunteer + Angular + CiviRules) that we did not use. CiviRules, in particular, needed updates (a Yellow Warning said us that it was necessary to update the DB, but the relative link did not work);</p>
  
  <p>b) then we unistalled all the extensions and canceled the relative permissions in Wordpress Access Controll.</p>
  
  <p>c) we cleaned up and verified that no traces were left.</p>
  
  <p>The upgrade was successful.</p>
  
  <p>It must be said that we had installed the three extensions for testing purposes, but if they were in production ... :(</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-15T14:21:55.313Z
Answers.LastActivityDate: 2018-06-15T14:21:55.313Z
Answers.UserDisplayName: Alessandro Letizia
Answers.Body: <p>Without seeing the log files or the error message. My guess is that has to do with exporting the database and importing it. When you export a database mysql adds 'DEFINER=...' to triggers. That definer is the database user in your old database, when you import the database it all goes fine, till the database trigger gets fired. </p>
  
  <p>To fix this do the following:</p>
  
  <ol>
  <li>export the database from your new site</li>
  <li>If your are on on linux run the following command: <code>sed -i 's/DEFINER=[^*]*\*/\*/g' mydump.sql</code> This will remove the definer statements from the dump.</li>
  <li>Import the database again</li>
  </ol>
  
  <p>For step 2 see <a href="https://stackoverflow.com/a/24613430/3733632">https://stackoverflow.com/a/24613430/3733632</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-17T09:01:05.273Z
Answers.LastActivityDate: 2018-05-17T09:01:05.273Z
Answers.UserDisplayName: Jaap Jansma - CiviCooP
Answers.Body: <p>It seems the excellent answer from @Jaap_Jansma will solve the issue with the DB import. The missing field error which occurs is due to a missing field which is part of the multilingual schema.</p>
  
  <p>As the issue is with a missing <code>frontend_title</code> it would appear that your CiviCRM instance is running in "multilingual" mode. Can you run the following command to rebuild the multilingual schema (replacing "en_US","fr_CA" with the values for the enabled languages on your CiviCRM instance. <em>Pick the right command for the CMS you are using.</em></p>
  
  <h1>Drupal 7</h1>
  
  <p><strong>Requires <a href="https://www.drush.org/" rel="nofollow noreferrer">DruSH</a></strong></p>
  
  <p><code>drush php-eval 'civicrm_initialize(); CRM_Core_I18n_Schema::rebuildMultilingualSchema(["en_US","fr_CA"], NULL);'</code></p>
  
  <h1>Drupal 8</h1>
  
  <p><strong>Requires <a href="https://www.drush.org/" rel="nofollow noreferrer">DruSH</a></strong></p>
  
  <p><code>drush php-eval '\Drupal::service('civicrm')-&gt;initialize(); CRM_Core_I18n_Schema::rebuildMultilingualSchema(["en_US","fr_CA"], NULL);'</code></p>
  
  <h1>WordPress</h1>
  
  <p><strong>Requires <a href="http://wp-cli.org/" rel="nofollow noreferrer">WP-CLI</a></strong></p>
  
  <p><code>wp eval 'civicrm_initialize(); CRM_Core_I18n_Schema::rebuildMultilingualSchema(["en_US","fr_CA"], NULL);'</code></p>
  
  <p><em>Source/Discussion/More Info:</em> <a href="https://gist.github.com/mlutfy/647e6325a09079e4f08f273af64900d9" rel="nofollow noreferrer">https://gist.github.com/mlutfy/647e6325a09079e4f08f273af64900d9</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-21T16:20:22.653Z
Answers.Text: Hi, @Homo Techsual, what you say is strange because this CiviCRM did not work in multilingual mode. However we tried and it gives us error:  >> "Sorry, due to an error, we are unable to fulfill your request at the moment. You may want to contact your administrator or service provider with more details about what action you were performing when this occurred. DB Error: unknown error <<   Have you another idea? Thx.
Answers.UserDisplayName: Alessandro Letizia
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-21T19:56:06.690Z
Answers.Text: Can you provide a backtrace from that error?
Answers.UserDisplayName: HomoTechsual
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-18T17:07:23.883Z
Answers.LastActivityDate: 2018-05-18T17:14:08.233Z
Answers.LastEditDate: 2018-05-18T17:14:08.233Z
Answers.UserDisplayName: HomoTechsual
Body: <p>we are trying to upgrade a CiviCRM 4.6.15 on Wordpress that comes from a multisite Drupal installation. This on WordPress is on a different server, but with the same DNS and Admin name. It works correctly but...</p>
  
  <p>...if we try to upgrade to CiviCRM 4.7 (or 5.1) the procedure starts but does not go beyond a "dead screen" with a Retry &amp; Skip button that do not work. </p>
  
  <p>We fear that there were problems with exporting the DB from Drupal multisite. Please, where should we look for the error? </p>
  
  <p>Attached the log file: <a href="https://pastebin.com/65fnAgMG" rel="nofollow noreferrer">https://pastebin.com/65fnAgMG</a></p>
  
  <p>Thanks in advance for those who can help us.</p>
  
  <blockquote>
    <blockquote>
      <p>UPDATE:</p>
    </blockquote>
  </blockquote>
  
  <p>1) as our SysAdmin (user3225453) replied, we've tried to follow Jaap's procedure 
  below, but it's not working. </p>
  
  <p>2) However this activity and the next Jaap' comment helped us to read better the LOGs: </p>
  
  <p>the problem (if does not concern "not imported custom fields" as 
  suspected by Jaap) could also be related to "PROFILE" (aka: "UF_Group", which are also found in the LOG) </p>
  
  <p>Do you have any idea? what about if we delete all profiles from the previous installation and try a new update? </p>
  
  <p>Thx.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-16T14:30:57.967Z
Comments.Text: Can you check CiviCRM log file if there are any errors?
Comments.UserDisplayName: Pradeep Nayak
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-16T19:18:28.610Z
Comments.Text: Yes, logs under ConfigAndLog folder.
Comments.UserDisplayName: Pradeep Nayak
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-17T10:12:18.150Z
Comments.Text: Did you run a perl script to sort out the triggers when you imported the sql dump?
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-17T17:15:23.220Z
Comments.Text: i've tried to follow Jaap's procedure, but it's not working. I've tried to search the log when i do upgrade and get this. https://pastebin.com/65fnAgMG Any help will be appreciated.
Comments.UserDisplayName: user3225453
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-17T19:31:09.290Z
Comments.Text: Please see the answer below. "user3225453" is our SysAdmin
Comments.UserDisplayName: Alessandro Letizia
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-18T06:30:17.110Z
Comments.Text: Thanks for posting the log. What I see is that a database query is failing because it is expecting the frontend_title field. The frontend_title field is not a CiviCRM field in the database. I dont know much about wordpress but could it be that you had (custom)fields in your previous wordpress/civicrm which weren't exported.
Comments.UserDisplayName: Jaap Jansma - CiviCooP
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-18T07:52:55.453Z
Comments.Text: Hi Petednz, we will check it, in addition to the last idea proposed by Jaap Jansma
Comments.UserDisplayName: Alessandro Letizia
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-18T07:56:30.810Z
Comments.Text: We will try to understand what's this field. 
  We keep you updated, Thanks a lot..
Comments.UserDisplayName: Alessandro Letizia
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-22T08:02:20.490Z
Comments.Text: I dont know what to do next and your own suggestion makes sense to me and I would try that out.
Comments.UserDisplayName: Jaap Jansma - CiviCooP
Tags: <upgrade><4.7><4.6>
Title: ISSUE upgrading CiviCRM 4.6 to 4.7 (or 5.1) in Wordpress (comes from a Drupal multisite)
ThreadText: # ISSUE upgrading CiviCRM 4.6 to 4.7 (or 5.1) in Wordpress (comes from a Drupal multisite)
  
  (Asked by: username_0 on 2018-05-16)
  
  we are trying to upgrade a CiviCRM 4.6.15 on Wordpress that comes from a multisite Drupal installation. This on WordPress is on a different server, but with the same DNS and Admin name. It works correctly but...
  
  ...if we try to upgrade to CiviCRM 4.7 (or 5.1) the procedure starts but does not go beyond a "dead screen" with a Retry & Skip button that do not work.
  
  We fear that there were problems with exporting the DB from Drupal multisite. Please, where should we look for the error?
  
  Attached the log file: <https://pastebin.com/65fnAgMG>
  
  Thanks in advance for those who can help us.
  
  > > UPDATE:
  
  1) as our SysAdmin (username_3) replied, we've tried to follow username_4's procedure
  below, but it's not working.
  
  2) However this activity and the next username_4' comment helped us to read better the LOGs:
  
  the problem (if does not concern "not imported custom fields" as
  suspected by username_4) could also be related to "PROFILE" (aka: "UF\_Group", which are also found in the LOG)
  
  Do you have any idea? what about if we delete all profiles from the previous installation and try a new update?
  
  Thx.
  
  **Tags:** upgrade, 4.7, 4.6
  
  > **Comments:**
  > **username_1**: Can you check CiviCRM log file if there are any errors?  
  > **username_1**: Yes, logs under ConfigAndLog folder.  
  > **username_2**: Did you run a perl script to sort out the triggers when you imported the sql dump?  
  > **username_3**: i've tried to follow username_4's procedure, but it's not working. I've tried to search the log when i do upgrade and get this. https://pastebin.com/65fnAgMG Any help will be appreciated.  
  > **username_0**: Please see the answer below. "username_3" is our SysAdmin  
  > **username_4**: Thanks for posting the log. What I see is that a database query is failing because it is expecting the frontend_title field. The frontend_title field is not a CiviCRM field in the database. I dont know much about wordpress but could it be that you had (custom)fields in your previous wordpress/civicrm which weren't exported.  
  > **username_0**: Hi username_2, we will check it, in addition to the last idea proposed by username_4 Jansma  
  > **username_0**: We will try to understand what's this field.  We keep you updated, Thanks a lot..  
  > **username_4**: I dont know what to do next and your own suggestion makes sense to me and I would try that out.  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_0 on 2018-06-15. Score: 2 | Accepted answer
  
  we were able to update CiviCRM from ver. 4.6.18 to version 5.2.1! I will tell you below how we solved the problem:
  
  a) we realized that we had 3 extensions (CiviVolunteer + Angular + CiviRules) that we did not use. CiviRules, in particular, needed updates (a Yellow Warning said us that it was necessary to update the DB, but the relative link did not work);
  
  b) then we unistalled all the extensions and canceled the relative permissions in Wordpress Access Controll.
  
  c) we cleaned up and verified that no traces were left.
  
  The upgrade was successful.
  
  It must be said that we had installed the three extensions for testing purposes, but if they were in production ... :(
  
  
  ---
  
  ### Answer by username_4 on 2018-05-17. Score: 1
  
  Without seeing the log files or the error message. My guess is that has to do with exporting the database and importing it. When you export a database mysql adds 'DEFINER=...' to triggers. That definer is the database user in your old database, when you import the database it all goes fine, till the database trigger gets fired.
  
  To fix this do the following:
  
  1. export the database from your new site
  2. If your are on on linux run the following command: `sed -i 's/DEFINER=[^*]*\*/\*/g' mydump.sql` This will remove the definer statements from the dump.
  3. Import the database again
  
  For step 2 see <https://stackoverflow.com/a/24613430/3733632>
  
  
  ---
  
  ### Answer by username_5 on 2018-05-18. Score: 0
  
  It seems the excellent answer from @username_4\_Jansma will solve the issue with the DB import. The missing field error which occurs is due to a missing field which is part of the multilingual schema.
  
  As the issue is with a missing `frontend_title` it would appear that your CiviCRM instance is running in "multilingual" mode. Can you run the following command to rebuild the multilingual schema (replacing "en\_US","fr\_CA" with the values for the enabled languages on your CiviCRM instance. *Pick the right command for the CMS you are using.*
  
  # Drupal 7
  
  **Requires [DruSH](https://www.drush.org/)**
  
  `drush php-eval 'civicrm_initialize(); CRM_Core_I18n_Schema::rebuildMultilingualSchema(["en_US","fr_CA"], NULL);'`
  
  # Drupal 8
  
  **Requires [DruSH](https://www.drush.org/)**
  
  `drush php-eval '\Drupal::service('civicrm')->initialize(); CRM_Core_I18n_Schema::rebuildMultilingualSchema(["en_US","fr_CA"], NULL);'`
  
  # WordPress
  
  **Requires [WP-CLI](http://wp-cli.org/)**
  
  `wp eval 'civicrm_initialize(); CRM_Core_I18n_Schema::rebuildMultilingualSchema(["en_US","fr_CA"], NULL);'`
  
  *Source/Discussion/More Info:* <https://gist.github.com/mlutfy/647e6325a09079e4f08f273af64900d9>
  
  > **Comments:**
  > **username_0**: Hi, @Homo Techsual, what you say is strange because this CiviCRM did not work in multilingual mode. However we tried and it gives us error:  >> "Sorry, due to an error, we are unable to fulfill your request at the moment. You may want to contact your administrator or service provider with more details about what action you were performing when this occurred. DB Error: unknown error <<   Have you another idea? Thx.  
  > **username_5**: Can you provide a backtrace from that error?  
  
  ---
  
  