Make WordPress Core

Changes between Initial Version and Version 3 of Ticket #39411


Ignore:
Timestamp:
12/28/2016 06:28:42 AM (8 years ago)
Author:
dd32
Comment:

Hi @vtorres7332 and welcome to Trac,

Trac is for reporting issues with WordPress, and is not available for support requests, for that we have the Support Forums.

In this case though, I'll note that the correct (and only supported) method of transferring WordPress sites is to perform an Export/Import, and not simply transfer databases. You may be able to use other tools that perform a WordPress site transfer too. In the event that you want to use a database transfer though, you'll need to ensure that the MySQL version you're transferring to supports the same database collations as what your current version does - and in this case it does not. In order to perform a SQL export/import you'd need to first convert the database from the utf8mb4_unicode_520_ci format to either utf8mb4_unicode_ci or utf8_general_ci - which depending on the content of your database may not be possible without data loss. How to do that is beyond what support I can offer you here, someone in the forums may be able to assist, or your host may be able to help you import the content.

I'm marking this ticket as invalid, as it's not a bug within WordPress, replies can be left without re-opening.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #39411

    • Property Status changed from new to closed
    • Property Resolution changed from to invalid
    • Property Component changed from General to Import
    • Property Milestone changed from Awaiting Review to
  • Ticket #39411 – Description

    initial v3  
    44
    55SQL query:
    6 
     6{{{
    77--
    88-- Database: `swsproje_prjctdb11`
     
    2626
    2727#1273 - Unknown collation: 'utf8mb4_unicode_520_ci'
    28 
     28}}}
    2929
    3030Could you please tell me how to correct this problem, I really need to move over this website.